Solving work

[prog]

It's been a little over a year since I signed my first truly independent work contract. I continue to feel like I've solved "work". I don't think I'll ever need to go job-hunting again. Unlike every other job I've had since graduating college, I'm not bored after a year of it, and I don't foresee that ever changing.

(Of course, in a real sense I am in fact looking for work all the time, now. But there ends up being a world of difference between attracting customers and seeking employers, as far as their respective outcomes go. It has everything to do with who controls you.)

Part of me just wants to embrace this evolved sense of work completely, invest some spare cycles into the next potential leap forward (Project X), and just let go of everything else for now. But I don't wanna, so instead I just procrastinate, by putting more time into Appleseed or X. Well, that could be a lot worse.

And X is going fine, thanks for asking. I am a little bummed that both my career and my biggest sub-project both deal with computer programming right now; though the projects are quite different the overall context is kind of monotonous. X is finite, though; the software itself has well-defined goals, and then it will go through a pass/fail submission process, which I hope to hit in around ten more weeks. If it fails, it fails, and if it passes, everything will change. But let's deal with that when we come to it.

Comments

[metahacker.livejournal.com]

Man, this is good to hear. While I'm not sure I can deal with the level of uncertainty that consulting requires, it's always been a moderately attractive career path...

[prog.livejournal.com]

Knowing what the pitfalls are helps a lot. I suffered last fall when I hit one, but I've been more proactive about avoiding them since then. For me this meant reading a short book about operating a business in MA, and then connecting with a decent lawyer, just for advisory matters. I don't expect to fall down quite so badly again.