6 ms·
I’m not sure that things are sustainable. COVID was just one more stressor. Wages have been rising for software people since long before COVID, and the average
by ChrisMarshallNY 5y ago
I’m not sure that things are sustainable. COVID was just one more stressor. Wages have been rising for software people since long before COVID, and the average tenure of engineers has been 2 years or less, for close to a decade. The entire industry is formed around it.
This (IMNSHO) has led to many, many problems, like project architectures, designed to compensate for many engineers of mixed skill levels, working on the code, instead of a smaller number, with consistent skills, shepherding the project from start to finish. This is opposed to designs for deliverable-focused Quality and market fit.
It’s nice to think about making lots of money, but I prefer writing and delivering projects that make me proud, and that I design and implement from napkin sketch to shrink-wrap. I don’t find it attractive at all, to contemplate an industry that is totally focused on keeping developers happy, because it won’t keep all developers happy; just ones that “play the game.”
- kqr 5y agoThe short tenures also lead to a bias toward technologies and techniques that look good in their first 0.5--1.5 years of usage but then ages badly with increased maintenance.
- gitfan86 5y agoNPM packages are by far the worst offender of this. Some packages are great, but others drop maintnentece completely after a year of support. Then you have to move off of them because they are tied to old versions of react or other core packages.
- nicoburns 5y ago> Some packages are great, but others drop maintenance completely after a year of support. Indeed. I would consider it one of the key skills for a JavaScript developer to be able to differentiate between packages that will be maintained and those that won't. Luckily JavaScript itself is quite straightforward, so JS devs should have plenty of time for learning this stuff.
- auggierose 5y agoOh, so all you need is somebody who can see into the future? Sorry mate, these guys are already busy otherwise as stock brokers. I've tried to come to terms with TypeScript during the last two months, but I am sorry, it is still too messy and does not give me enough guarantees about my code. What I would love is a Swift to TypeScript / JavaScript compiler.
- mooreds 5y agoNot quite what you asked for, but here's a relatively mature Java to JavaScript compiler: http://www.gwtproject.org/ http://www.gwtproject.org/
- alisonkisk 5y ago
- danuker 5y agoI wish GMail stil used GWT. The current UI is a dumpster fire of sluggishness, even with a brand-new CPU and plenty of RAM. It made me switch to Thunderbird. I had to sift through tons of mails to unsubscribe, without the Promotions/Social/Updates tabs. The ones that kept sending me mail go to spam now.
- auggierose 5y agoSorry, I wrote my last commercial Java App about 20 years ago. I don't intend to start again :-)
- nicoburns 5y ago> Oh, so all you need is somebody who can see into the future Well yes, anticipating future developments is one of the main things a software developer does. And IMO one of the main differentiators between junior and senior developers. A library that has a history of regular maintenance is unlikely to get suddenly dropped. And a library that has a large user base will have its maintenance picked up by others if the original maintainer(s) do step down. If the library doesn't meet these criteria then you probably shouldn't be using it.} I don't think you can realistically use Swift client-side. But Rust is an increasingly viable option (for browsers that support WASM). WASM compilation is built in to the official toolchain, and the js/ts-interop story is quite good too at this point (modulo some overhead when calling between JS and wasm).
- trinovantes 5y agoIt's likely most of those packages were created on the job and the person left the company (and package maintenance) after 1-2 years
- Beltalowda 5y agoPresumably those packages are open-source, so you can just fork, update, and continue using them?
- dragonelite 5y agoI get why the old timers say they prefer proven technology now. When i had less then 4 years of experience every new framework was worth checking out no maater how unproven it even was.
- majewsky 5y agoMy first job out of college was maintaining and refactoring a 10+ year old Perl CGI application. After a bit of adjusting, I found it quite rewarding to refactor overgrown messes into nice and readable OOP patterns, and more significantly, it was character-forming because it really hammered home the point that one person's quick fix will always become someone else's maintenance burden down the road. It's definitely been a positive influence for me to experience the other side of the stick early on in my career.
- ChrisMarshallNY 5y agoOne of my first jobs was as a maintenance programmer for about 100KLoC of 1970s-era FORTRAN IV. Not one comment to be found, short, inscrutable variable names, no indenting, and having been stepped on by dozens of junior devs before me. It was "Voodoo bug fixing." I had to close my eyes, and throw a dart, hoping I got it. It taught me, very early on, to write good code.
- rdevsrex 5y agoThat sounds like the stuff of legends or a horror novel.
- ChrisMarshallNY 5y agoImagine me, with a flashlight under my chin, as I recount the story... It was an email system; before what's-his-name-The-Nanny's-husband "invented" it.
- jcadam 5y agoSame. I'm in my early forties now. Most new technologies are just recycled ideas from older tech.
- BlargMcLarg 5y ago>instead of a smaller number, with consistent skills, shepherding the project from start to finish. This is opposed to designs for deliverable-focused Quality and market fit. Ultimately, if companies truly valued this, they would've done more to keep talent. Instead the majority keeps looking for the fine line between "they will quit" and "they will stay", even going so far as disregarding the basic premise of "a happy, stress-free employee produces more valuable output". >I’m not sure that things are sustainable. Of course things aren't sustainable. Nothing points towards most companies aiming for sustainability in the first place.
- danuker 5y ago> a happy, stress-free employee produces more valuable output The output is certainly more costly, but does it bring in more income for the company? Are there any studies published about this? I imagine Big Tech would keep it as a closely-guarded secret.
- ChrisMarshallNY 5y ago> The output is certainly more costly, but does it bring in more income for the company? Depends. A Mercedes is a lot more expensive than a Honda, but Honda's a bigger company. Both are quite successful, though. It depends on the metrics and targets.
- bluGill 5y agoIf I did the math right (euro vs yen, and wikipedia has different years) Mercedes is slightly bigger than Honda. Honda sells more cars in the US, but Mercedes sells much bigger trucks (freight liner is Mercedes), and both sell around the world.
- BlargMcLarg 5y agoConsidering Google came back on its brain teaser interview practice and several other practices, I have a hard time believing their decisions are largely empirical as opposed to short-term rational. This is even worse for "happiness" since individual happiness extends all the way to communities and back into society. Not only that, happiness is very dependent on culture, upbringing, cost of living and more. However, even HR at small tech companies in Europe follow the basic idea of "if employees are happier, they will produce more output!". Assuming this isn't a pretty lie, we know people are generally happier not having to live paycheck to paycheck by force. We know people are generally happier not having to sit in traffic jams because of a 9-5, at the office mentality. Even modern hiring practices are based on distrust and making things more tedious for both sides of the equation, when there are solutions which would at least help the employer out. There's plenty of room for them to actually follow their own advice, and we have plenty of studies at least suggesting benefits of remote work, less hours, different work hours, etc.
- rr808 5y agoI really like working on a project for 5-8 years at a time and really building tools to make the system run smoother and reliably. It really has backfired, I'm out of touch in the latest interviewing fads and I think hiring managers wonder what's wrong with me rather than thinking I'll be a good hire.
- throwaway123x2 5y agoI've been doing 4-5 and it's the same for me.
- ChrisMarshallNY 5y agoI just stopped looking for work. I got tired of being insulted, right off the bat. Too bad. I could have been an awesome hire, for a number of these companies; especially the smaller ones. I'm not "behind the times," at all, and would have been happy with far less compensation than most. It was funny, these little shops were doing the same kinds of interviews as major-league FAANGs, even though their workflows and requirements (and pay) were drastically different. I guess it's a case of "Monkey see; monkey do."
- kache_ 5y agoA lot of companies have found success in treating engineers fungibly. If you think of the engineers as part of the computer system, this actually adds resilience in that front, traded off by resiliency of the software itself. If you lose 10 software engineers due to the bus factor, the fact that you already are treating engineers fungibly gives you resilience on that front.
- tomc1985 5y agoMaking people fungible dehumanizes them. Personally I hate having to job hop just to get what I wanted from this industry. The business community wants everybody and everything as replaceable and fungible as possible, to its long-term detriment. That so many see short-term "success" and call it that should be far more appalling than it seems to be. Take Circuit City, for example, which, when it was already struggling, let go all of its senior sales people on the floor and replaced them with minimum wage. The knowledgeable salespeople was pretty much the only thing going for Circuit City at the time. Customers noticed, responded, and the business fell off a cliff
- hnxs 5y ago> Making people fungible dehumanizes them. that’s just capitalism
- tomc1985 5y agoNo, it's not. Far more capitalism in many other countries operates with workforces that have been there for generations. We used to offer pensions here in the US, that is still going elsewhere and in government Human capital has value and appreciates over the long-term
- jcadam 5y ago> Personally I hate having to job hop just to get what I wanted from this industry. A couple of times I've landed at a good company, where I figured I could stay for a long time and build something resembling a traditional career. But something invariably changes - the company gets acquired by some MegaCorp, a leadership changeover, your awesome team gets disbanded and scattered, etc... c'est la vie.
- bryanrasmussen 5y agoas a general rule my ADHD tends to get my burned out on being at the same place, same tasks after 2-3 years, and then I decrease in productivity. So if the system was set up to retain me longer than that, I don't think I would take advantage of it anyway.
- jcadam 5y agoI once worked at a company that specialized in R&D. Short projects, ad-hoc teams, etc. Kept things fast, interesting and ever changing. I consider that time to be one of the best (and happiest) of my career. But then some of our projects turned into production systems, and the place started to take on a more "traditional" software shop feel with terms like SDLC and CMMI being thrown around. Then we got bought by a bigger company - that was the last straw for me. Oh well, was nice while it lasted :(
- Calamitous 5y agoIn my experience, the industry is focusing on developer happiness at the expense of developer satisfaction.
- dgs_sgd 5y agoCan you elaborate on the difference? When would I be a happy developer but not a satisfied one?
- pklausler 5y agoIf your compensation, benefits, and perks are great, you might be happy, but if you're a functional programming expert spending all your time writing up TPS reports on a spaghetti legacy COBOL application, you may not be satisfied.
- jcadam 5y agoDepends, how much am I getting paid? Sorry, I'm old and jaded.
- black_13 5y ago
- jcadam 5y ago> Wages have been rising for software people since long before COVID Inflation is "solving" this problem. No way are companies going to give across-the-board 8-10% (or more) cost of living adjustments this year. And it's a safe bet inflation will still be high next year.
- black_13 5y ago