Tag: systems analysis

Animated Navigation Bar: 50 Projects in 50 Days

Carl Setzer2 Comments
person encoding in laptop

Today we created an animated navigation bar with (mostly) CSS. I easily see a use case for this one, which makes it that much more fun.

You click on the “x” or the double line (depending on the view you’re in) to change the animation.

Besides growing my developer skills, I’m considering what work I should/could do in the near term. It’s going to be a bit before I feel ready to do coding interviews, much feel ready to jump into a production environment. But that’s not the only thing I can do with all that I’ve learned over the past few years.

My studies have covered a pretty broad swath of technology. Besides the keys to web development (HTML, CSS, and JavaScript), we also looked at JQuery and PHP. Stretching beyond the rudiments, we went pretty deep into databases (theory as well as design), system analysis and design, and project management (amongst other things). Also, I added some courses in Cisco Networking (the internet is a network, right?), desktop support (one more class then I will have a certificate in desktop support), and system architecture. Combining this with my pre-ATA career, I think this sets me up to be a great system analyst. I understand the technical side of things, and what business leaders want/need. I will do an excellent job bridging the gap between “business” and IT. Thus, I’m leaning that way in my job search.

What do you think? Any guidance you have to offer me as I transition? I’d love to hear your thoughts.

Documenting Everything

Carl Setzer
code-as-documentation

Currently, I’m taking the second quarter in a two-quarter series on Systems Analysis. One of the lists my text presented is “7 Design Habits”. (side note: I appreciate the reference/nod to Steven Covey’s 7 Habits Of Highly Successful People). I like the list, so I wrote it out on a post-it and have it on the wall next to my desk.

  1. Understand the business
  2. Maximize graphical effectiveness
  3. Think like a user
  4. Use models and prototypes
  5. Focus on usability
  6. Invite feedback
  7. Document everything

I value each of these. While maximizing graphical effectiveness has been an area of interest for quite some time (it’s the roots of my interest in design), what really speaks to me right now is “document everything”.

I’ve lived by this mantra for years. I try to drop everything into Evernote*, for instance. Articles I’ve read, people I’ve met, things told to me. This collection of notes is but one element of documenting everything. Knowing where I got ideas is pretty important. But this notion means more. To me, it implies a certain thoughtfulness to the documentation. Sure, it’s great to have dozens of pages of random notes. But “documentation” is organized. Not just links to articles, or pages of feedback, but also analysis, explanations of the “why” within choices. Being able to reference, at some random point in the future, how we got to a certain decision can be crucial when evaluating a problem and determining a response. Also, in a more negative vein, it can show due diligence in a lawsuit.

So, yeah, my propensity for collecting information has saved me plenty of anguish over the years (“you never told me that!” “well, here’s the email I sent to you with your reply”). It’s also been helpful to friends and colleagues (“hey Carl, who was that guy from Facebook we met with last year”. Yeah, it’ll be in my notes). I appreciate the reinforcement that this is a best practice that’s valued at least by textbook writers.

*this link to Evernote is an affiliate link. If you subscribe to the service, I will get rewarded with a free year of the service.