5 ms·
Yes, if you just want to coast. Coasting is certainly a perfectly legitimate goal, it just doesn't work in this industry. You have to constantly grow the bread
by wahern 10y ago
Yes, if you just want to coast. Coasting is certainly a perfectly legitimate goal, it just doesn't work in this industry.
You have to constantly grow the breadth _and_ depth of your skill set.
Depth because, from a theoretical perspective, change in computer science is exceptionally slow and incremental. The basic theories and algorithms in the latest machine learning craze, for example, are not much different from those of 30 years ago. If you understood the 30-year-old theory, grasping the modern stuff is much easier. The big enabler has principally been from new hardware.
Breadth because what passes for "skill" today (just like it did yesterday) is effectively familiarity with tooling and buzzwords. You have to pay attention to how tooling and best practices evolve. The tools may be inferior and the best practices not very effective, but the productivity of teams and companies depends on everybody being on the same page. And even if the tooling and practices are worse, it won't that bad. (See depth, above; change is slow and incremental.)
Personally, I took a mid-career break for law school. One of my varied reasons was because the law is perhaps the last professional domain where age and experience is still highly valued. Even a 21-year-old hot shot millionaire would rightly think twice before choosing as his counsel a young top-of-his-class Stanford graduate over a 70-year-old attorney with 50 years of experience in battle.
Philosopher-lawyers from Harvard and Stanford don't have particularly good track records in winning cases. Another reason for my choosing to go to law school was my confusion about Lawrence Lessig losing his case at SCOTUS challenging copyright extension. That's when I began to realize that maybe I (and others, like Lessig) was living in a bubble regarding my understanding not only of the law effecting my professional life, but the law more generally.
Plus, I did some of my best coding while going to law school. Nothing feeds your desire to hack like an extended absence from the grind of programming for a living. And being immersed in an unrelated body of knowledge seems to enhance creativity when programming. I immediately returned to San Francisco after graduating and went back to coding (pay was better, anyhow), but every penny spent was well worth it. The stress, however, probably shaved years off my life. Law school is like bootcamp for the mind, but even more harsh and unsympathetic. My first year was pretty darned close to Paper Chase, including scenes where the professor chastises students in front of the class, tells them to get out of his class, etc. If only undergraduate school were like that. To see some students flunk out their first year only to return to try again was unexpectedly humbling and inspiring, more so than the sheer terror of being one of those to flunk out.
- mikestew 10y agoCoasting is certainly a perfectly legitimate goal, it just doesn't work in this industry. Maybe not when you're young, but you can coast just fine as an older software dev. I'm doing it right now. Now, it might not look like coasting. Sure, I get pulled in to build test infrastructure from the ground up, prop a build server to fit the source control flow that a particular team has chosen, can walk a dev through writing unit test and integrating them into their flow. Hire some testers and dev with a high percentage of "good fits". Hell, manage a team if you need me to. Deal with the client in a professional manner instead of coming across as some basement dweller? All of that before my first cup of coffee without breaking stride. But only because of years of experience does it become second nature. The tech stack? Meh, you've learned a dozen, you've learned them all. That's the easy part, and when it's not easy I'll go read up. But to me, the truly hard stuff gets easy after enough years and one can cruise through the non-tech parts that (to me) are the hardest part of the job. The only thing I still struggle with is putting up with bullshit in a tactful manner. That gets harder with each passing year, probably because experience makes it more obvious and harder to ignore.
- logfromblammo 10y agoI had a hard enough time dealing with other people's bullshit when I was 10. I can't even swallow my own bullshit now. And it seems like more jobs out there are constantly increasing their ratios of of bullshit filler to useful, productive work. But I can't really tell whether it is objectively increasing, or if I am just getting better at recognizing it.
- wahern 10y agoI think you may be insufficiently fearful of the current and future economy. Or maybe I'm just too fearful. But I grew up rather poor, and while I thankfully learned to shed most of the proletarian work ethic that keeps poor and working-class people in economic shackles (that is, the political mindset, perceptions of character, and in particular the kinds of labor considered meaningful), I still believe that the prudent economic life demands a constant hustle. My financial advisor says the average cost of a 4-year private education will be well over $350,000 in less than 20 years. (It'll be that in just a couple years for the elite private schools, including non-Ivy League elites where most students don't get much aid.) Now, I don't plan on paying for my son to attend a private university if we can help it (public undergrad is fine by me), even though we might be able to swing it without too much damage, but that number serves to really drive home the cost of keeping your family securely middle-class. Also, yes, middle management is always an escape. OTOH, middle managers are always the first to get the axe during layoffs. I probably misinterpreted the original question, but moving to middle management is not something I aspire to. I respect it, but I'm not a people person and I don't like managing people. I've been fortunate that the few people I have managed I was able to hire myself, people who I felt were much more self-motivated and self-directed than the average engineer. If I can't continue hacking for an income, I'll probably return to the law. I left it unsaid, but IMHO ageism is rife in the software industry. There'a ageism in almost every industry (including the law, it's just reversed ;) but IME it's comparatively greater in the software industry. Many people won't bother even denying it, and aren't afraid to excuse it. I saw ageism even when I was in my early-20s, working with an original Amiga veteran (a bone fide historical figure in the Silicon Valley) whom other young engineers would constantly deride, arguing he was too "behind the times" and just "didn't get it". It was all bollocks of course, and I understood that. (Though I never completely understood why he chose to stay in the trenches, and continues to do so AFAIK, despite the fact he could probably join a VC firm.) Now that I'm older and approaching grey beard status (an age which decreases every year), I won't let myself forget the mentality among the junior engineers, as well as the bean counters, recruiters, and other managers who not only tolerated it, but enabled it. In light of the ageism, if you want to continue hacking, and you want to minimize your risk of income volatility later in your career, you have to constantly dedicate yourself to improving the depth and breadth of your knowledge. That's a good idea in any industry, but especially in software. And that's why I don't see coasting as a viable option. But people's situations and preferences vary, of course. Coasting can make more or less sense, depending on context.