7 ms·
"Unlike Engelbart, I have re-tooled. I now work in JavaScript in the browser and on the server. I had to walk away from the codebase that I loved. I understood
by jgrahamc 12y ago
"Unlike Engelbart, I have re-tooled. I now work in JavaScript in the browser and on the server. I had to walk away from the codebase that I loved. I understood that the price of relevance is to give up fighting at some point and settle for a partial victory. I think I was right in the development environment I created. But right doesn't mean the world uses what you created."
Yep. That's the key to staying relevant: change with the times.
- bentcorner 12y agoI think I'm coming to grasps with this too. I'm over 30 and have spent most of my life building large desktop applications in C/C++. I want to eventually work remote, and looking at what's out there, there are very few opportunities with someone with my skillset. It's all modern frameworks and languages. So, I'm spending some of my own time learning some of this stuff.
- _yosefk 12y agoEmbedded programming is much more stable wrt languages and (often non-existent) frameworks. Nice for C/C++ devs.
- sgt101 12y agoI worked as a C and then C++ dev for a few years and then I started a Ph.D writing a C++ code base. I remember the day that I got java 0.7 running on my spark 20. I would never touch the STL again, never have to worry about malloc and #def overwrites. No more gdb. There's not much nice for c/c++ devs, pity them.
- tosseraccount 12y agoHow many java programs are running your desktop now? How many C/C++ programs?
- housel 12y agoEmbedded programming is also harder to do remotely due to needing hands-on access to development hardware, frequent access to hardware engineers, expensive test equipment, and so forth.
- vonmoltke 12y agoIt's also a silo that can be hard to get out of and is very hard to get into, because all you do is C or C++ work and everyone wants C or C++ experts for their jobs.
- curun1r 12y agoThis. I see too many older developers who complain about ageism, but what's really going on is that they're essentially the same developer they were 2-3 years into their career. If you've been working in the industry for over 20 years, employers can and should expect that you've made the most of it. Those developers have very few problems with ageism. It's the ones that have become comfortable and stagnated that have trouble.
- hoprocker 12y agoWho was it that said, "It's not 10 years worth of experience, it's the same year repeated 10 times"?
- spacemanmatt 12y agoSomeone with 10 years of experience, unable to recognize the nuances one picks up by repeating those 10 years of experience with 10 years of context to make better sense of it.
- hoprocker 12y agoExcellent point; that 10 years can make you a specialist.
- scrozier 12y agoI am 57 and quite current. I have launched several startups and kept fresh constantly. My current client has me doing lots of leading edge stuff that some of their younger devs couldn't do. And yet I do feel the ageism. I understand it and I'm not angry about it, but it's real, nonetheless. It's not a good feeling.
- 31reasons 12y agoWhat kind of ageism have you experienced ? Can you describe some experiences ?
- rayiner 12y ago
- ams6110 12y agoFor me, the thing that gets a bit discouraging at times is the feeling of riding a slow-motion merry-go-round. Every 10 years or so you see the same ideas start to come around again, only with some new paint and landscaping. I have found myself more than once thinking that learning about some new trendy buzzword is just ultimately a waste of time, since I will barely have mastered it before it's been replaced by the next new/old thing. On the other hand, it gets easier since none of the concepts are new anymore, and I tell myself, "hey, if you want to pay me to build a client-server app in the browser like it was 1995 (substitute Powerbuilder for Firefox/Chrome), great, happy to take your money."
- timmy-turner 12y agoAnd you hopefully have learnt from the mistakes Powerbuilder did back in '95, not making them again. So in theory you're ahead of the crowd of today. Though that means that you have acknowledge that things were not all that great back then as you remember - which seems to get harder as one grows older.
- derefr 12y agoI see the same thing, but feel much more optimistic about it: it's not, in my mind, that tech is effectively fashion, but rather that there are "futurist" ideas that tech keeps trying and which keep not getting adoption, because it's not their time yet—the state of the art isn't there to make the experience for the average consumer (or the average developer) justify the costs. An example of what I mean: the Apple Newton, and then 10 years later the Palm Pilot, and then 10 years later Windows CE and flip-phones supporting J2ME, and then 10 years later touchscreen phones and tablets. There have been four generations of "mobile app developers", but only the latest generation has seen any traction for their apps. This time the idea stuck; it will stay around, rather than coming around again. If something like Paypal's prototype service (beaming money from one Palm Pilot to another) were set in this "revolution" of mobile instead of that one, it would be much more successful.
- smitherfield 12y agoNot to be that guy, but Apple Newton: 1993 Palm Pilot: 1997 Smartphones: ~2002 iPhone: 2007 Android: 2008 iPad: 2010
- vezzy-fnord 12y agoGenerally sound, but there does seem to be a certain breed of vanguard who lives off being heterodox with regards to the computing mainstream, yet functions just fine and likely harbors plenty of insights. Much of the Go team lived full time on Plan 9 at one point or another, and it's not like all of them were Rob Pike or Ken Thompson. There is value in keeping up with trends, but on the flip side there is value in sticking with sound ideas, even if they are not necessarily attractive in the labor market, and learn enough to be employable or self-sustainable in some regard. I would say server-side JS might not necessarily be a great long-term prospect, at least in part due to limitations with SMP and unwieldy concurrency models. Even if it persists, the value of knowing might be more of a labor necessity than any inherent utility. Because programming operates on lots of trends and conjecture, knowing which ones not to waste time on is a much more valuable skill than jumping to stay "relevant".
- wwweston 12y agoSomething I've found as I've gotten older, though, is that I have a stronger and stronger sense of wasted time every time I have to learn a new way of doing the same thing. Particularly if the new way involves a bleeding edge leaky abstraction. Because every hour I spend investing in a new stack and its details is an hour I can't spend thinking about product-level details, can't spend learning more learning about organizational-level matters, can't spend on improving more timeless investments like statistics, math, and soft/interpersonal skills. Not to mention fun things like music and travel and enjoying the company of people you like. It wouldn't be so bad if most of the new shiny things in the software world were an order of magnitude better. But saying that 1/4 new frameworks or even languages present tha kind of power/productivity jump would be optimistic.
- fsk 12y agoThat is one of my biggest concerns. A lot of the new tools are just different, not better. But you're expected to know all of them. It's also hard to predict what will be popular five years from now. I thought that using Javascript on the server was pants-on-head retarded, but it's very popular, with no signs of passing on.
- georgemcbay 12y ago" I thought that using Javascript on the server was pants-on-head retarded, but it's very popular" Well, there's no law against things being both terrible and popular. It is quite common.
- fsk 12y agoWhat does it say about software as a serious career, if tools that are awful are popular and widely used?