The Hacker Lifecycle
An anonymous reader writes "Hacker Benjamin Smith deconstructs the cycle of education, production, and rest that will be familiar to many software and hardware engineers. He breaks it down into four steps: 1) Focused effort toward a goal, 2) structured self-education, 3) side-projects to sharpen skills, and 4) burnout and rest. He writes, 'As my motivation waxes at the beginning of a cycle, I find myself with a craving to take steps towards that goal. I do so by starting a project which focuses on one thing only: building a new income stream. As a result of this single-mindedness, the content or subject of the project is often less interesting than it otherwise might have been. ... [Later], I almost always decide to teach myself a new technical skill or pick up some new technology. ... This is usually the most satisfying period of my cycle. I am learning a new skill or technology which I know will enhance my employability, allow me to build things I previously could only have daydreamed about, and will ultimately be useful for many years to come. ... [In the burnout phase], I'll spend this period as ferociously devoted to my leisure activities as I was to my productive tasks. But after a few months of this, I start to feel an itch...'"
I think this is a reasonable description of 'most everyone's productivity cycles. Granted I'm just another more-or-less Asperger's engineer/physicist with a strong love of music, but take a look at writers, artists, or almost any field of endeavor. You'll find people's output varies significantly over time. Vacations help too. :-) . The ability to take on side-projects without feeling guilty is probably a very handy thing in one's life.
https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
Those goals still form the focus of my motivation, even 7 years after I first wrote them down.
lol n00b
One of the most important is financial independence – I want my day job to be a lifestyle choice, not a requirement.
Translation: "I can't function in a society, and never will have any joy until I am rich enough to do whatever I want".
Here is the reality: you will never be that rich. No one ever will.
Contrary to the popular belief, there indeed is no God.
You misinterpret.
Hacking is a joy unto itself; the ostensible goal is only an object, something to hack. Hacking isn't random, it's purposeful. But if the enjoyment doesn't come from the hacking, but from the ostensible goal, well, the enjoyment is fleeting.
-- hendrik
Ditto.
Fucked me in school.
"Write a paper on X". Cool. Read about X, learn about X, sit down to write paper that will be read once and thrown in the trash and that a billion other people have already written... motivation goes out the window. I can already write well (I've written 1,000 of these goddamn things) and I already know the material that's going in the paper. No one truly cares about what I'm about to write—no one needs it, and no one really even wants it. Suddenly a blank wall is more interesting.
Give me a real need to learn something or just let my curiosity take me where it will, and I'm the world's most dangerous carnivore. I'll run a problem down and eat its damn heart, then take out the rest of the herd for funsies. Otherwise? I'm probably boned.
The elimination of the uselessness of the end product that comes with doing actual work rather than "homework" has helped a lot, but it's still something I have to fight, years later. The multi-year process of adjusting my image of the way thought I ought to be to accommodate the fact that I simply was not compatible with a formal educational setting really sucked. Those were some sad years full of serious self-loathing. My self-loathing is far more lighthearted now :-)
I still hate maintaining systems and chasing bugs that don't require much sleuthing. Any time I'm required to make some "quick hacks" to fix something in an ugly way for lack of time is a bad day, and I'll go home in a bad mood and show up the next day in a bad mood. I'm probably the happiest at work either designing systems or fixing things that have broken in strange ways, when I'm fully engaged in a problem for hours on end. Exercising the clever-muscle in my brain is great and makes the hours fly like nothing else, and playing grown-up legos when designing is fun. Practically everything else about being a programmer sucks, but WTF else am I going to do? At least it's fun some of the time, which beats most jobs.
As with any personal trait or behavior I'd guess I'm far from being alone.