Not Dead Head

Side A

Monthly Archives: December 2010

Know your Kung-Fu

My comments on this interesting article …

http://www.thebitsource.com/infrastructure-operations/the-social-network-bust-what-i-learned-from-my-job-interview-with-facebook/

… I was a Sr. Systems Engineer with 10 years of experience that was picky about where I wanted to work, and I was in no rush in finding a job that I would not enjoy.  I wanted a career, not a job.

This is a very good article not just about getting through a job interview.  The possibility to get a position after an interview is not always as good or bad as you may think after it.  There are too many factors that come into play.  You may be very good on the facts and expertise required for the position, but if you aren’t the type of person they’re looking for, you’re out.

Sometimes it is also the other way around.  You come into an interview with great expectations and very exited, very well prepared, you know is “The Company”! and afterwards you take back your application. Disappointed because it wasn’t was you where expecting.

To get/find a good job is hard and a matter of luck.  So if you’ve got a good one, work on it so that it stays that way.  Because looking for a good job isn’t easy.

To truly master scalability, performance, and availability – you have to know the fundamentals.

A very important piece of information is to stay aware. If you get too cosy on your “perfect” job, you will end up loosing all your hardly achieved skills.  Computer Scientists are no “assembly line” personnel, we’re also more than scientists, we’re also artists.  We use technology to build beautiful great things, so don’t forget that feed your brain well. I thought it’s really sad, that he started looking for information about new technologies and current practices only because he had to do the interview.  A least he is doing it right now.  Stay passioned!

Code has the possibility of being poetry, laced with verses of logic.

I like that he mentioned some good books, Web Operations is a good one.  I’ll have to check some of the other ones.

 

Know your Kung Fu.

Advertisements

on continuous delivery

This comes very familiar to me. Some extra comments:

  • Releasing frequently, well frequently  is very relative. Releases should consist of  small change set in order to keep the impact of the changes “predictable”. A way of achieving this is using agile methods like scrum.
  • Everyone can self-service deployment is a tricky thing. You can do this if you architecture is not too complex, so that everyone understands what happens during a/any deployment.  If the architecture is complex, then people will be only deploying their application.    This requires a very good communication culture and channels.  You may say …”no no, all you need is to automate”,  if you are so far, please let me know.
  • Puppet, well that is just a tool. The point is to automate your deployment process to the max. Infrastructure as code will be the answer.
  • Metrics is a very important point. Without them you a driving blind and no automation will be possible.
  • I love the “How log will it take your organization to deploy a change the involves just one line of code?“. … how agile are you?
  • If it hurst, do it more often …” kind of masochistic but very effective.
  • make your build self-healing” … I wonder what that will look like.

I got the mindmap from http://code-dojo.blogspot.com/2010/11/mind-map-continuous-delivery-notes.html

%d bloggers like this: