Skip to main content

How To Work At SocialServe.com

Here are my instructions to anyone else who may want to work at SocialServe.com:
  1. Have a strong enough interest and passion for development to start a contracting business without any formal training. Support yourself for about a year and a half working for one client and the next.
  2. Move to an area populated enough to start a user group for your favorite development language, tool, or concept. (Mine was Python)
  3. Be suggested to send in a resume to the company of one of the first members.
  4. Sweat your way through the first real interview for the kind of job you've wanted your whole life.
  5. Cross your fingers not to screw it up.
So, that's my story. I had my interview last Tuesday, called Thursday, and started Friday. I've enjoyed it a lot. Learning my way around the codebase has been going pretty well and I've already got my first couple of commits in, as well as two small projects. I like to think I'm moving along nicely.

One of the things I need to get used to is that all of our development boxes are Macs. I have a company issued Macbook Pro (2.33ghz dual intel, 2GB RAM, 17") and I'm really enjoying the Mac life. The UNIX background is great and the interface is just slick. Installing applications is just fun. I've got the entire KDE suite installed, so I've got a lot of my favorite tools and toys right there.

The time away from the house, while somewhat nice, is probably the biggest downside. Caelan misses me a lot while I'm at work and I miss him and his mother quite a bit. After all this time at home, and all of his life so far with me there every hour, it is tough. It may be harder for me than him.

Finalizing the whole picture is my commute. 30 minutes or less to work and an hour to and hour and a half to get home. What's up with that? I need to see about leaving early or I might just leave an hour late. I'd still get home at the same time, so I might as well spend it in a comfortable chair instead of my ugly car.

Comments

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…