Skip to main content

I’m Gonna Hit The Ground Running

I already wrote about leaving Caktus to start a new job at Red Hat and that first day was today. I’ve never really had this kind of new-hire orientation before, having spent all my previous software career as a freelancer and just transitioning from a contractor to employee at my last company. I didn’t know what to expect.

I’ve been thinking a lot about what this transition means for me as a developer, obviously. I’m making than a transition in companies here. I’m moving back to full-time Python work from years as one of those Full-stack web developers. While software always has many moving parts I’m transitioning from an environment with multiple diverse client projects to working on more focused, coherent works to deep dive into. Moving from Ubuntu to Red Hat Enterprise Linux, MacOS to GNOME, thirty coworkers to over 10,000.

So it was time for a change and clearly I decided to just take them all at once. Software development is inherently change and new: by virtue of being built everything you make is new, even if similar to the things that came before it. You always learn something new, even as you grow in the experience you can bring to every new project. I have to ask myself two really important questions about how this is going to work:
  • How can I make all the twelve years of experience I have make me as successful as possible applying it to such a new environment and such new kinds of projects?
  • How can I absorb as much of the new experiences I’m going to have in the next few years and avoid being either overwhelmed or leaving too much on the cutting room floor when adapting that experience into my developer-mind?
There might be good answers to those questions, but I don’t quite have them yet. This is something I’m going to get wrong, but not totally wrong. I’m going to make some mistakes and learn to make some adjustments and I’m not going to be phased when that happens. If I can expect course corrections later, then the best thing I can do now isn’t to decide exactly how I’m going to do great, but to decide how I’m going to keep doing better.

I love software because I love solving problems. Knocking a new job out of the park is just one more problem.
Labels:

Comments

Post a Comment

Popular posts from this blog

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 operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...
Post a Comment
Read more