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.
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.
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.
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.
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.
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.
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.
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).
Projects die all the time or start being very lazy with the maintenance. Not that I expect anything more, there is literally no money in them.
The criteria I like to use is "Will I be able to fork it and fix it when it goes unmaintained"?
I have been thinking about Rust, but it has too much stuff like ownership I rather don't want to think about on top of the already complicated things my code does.
A compiler from Swift (or a subset of Swift) to TypeScript would make it a viable option for me. Maybe I write it myself.
There's a couple of other heuristics for whether or not something is worth using on a project (like complexity of learning, and context within a larger stack), but suffice to say it's about looking past a specific problem and on to subsequent problems down the line.
I beg to differ. I've been using it client-side for years. I do not like the hybrid offerings.
Rust seems like an excellent server language, and I look forward to seeing it get more mindshare. Swift smells a lot like Rust.
But I’ve used PHP for my backend work. I’m not really a backend engineer, and I am sure it could be done better; even with PHP.
One of the reasons for my choosing PHP, is because it is so widely known, and is a perfectly good language, as long as it is written well.
There was that study that was done recently, where they showed what I call “the fishtank graph.”
This was the graph that showed which server languages were in use.
PHP was this fairly steady line along the top, and every other language looked like gravel in a fishtank, along the bottom.
I feel like Dart gets me reasonably close to the kind of elegant, intuitive code I can write in Python...but with static typing.
What I like about Swift is its "protocol oriented programming", which is basically pragmatic Haskell type classes. There is just so much done right in Swift, that I have a hard time going back to any language that doesn't have it:
* protocols, integrated with struct/enum/class
* dot-syntax when the context is known (like .blue instead of Color.blue)
* immutable data structures via copy-on-write, nicely integrated into the language
* best integration of optional type (like Int?) I've ever seen in a language
* (optional) named function parameters (in the beginning I was annoyed, but now I am a big fan)
* the way exceptions work
* cheap garbage collection (kinda; ARC is working like garbage collection for most of the code I write)
* great package system
* great IDE (Xcode)
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.
I think I've just come to a point where I don't want to split my attention between formalisms for reasons that have nothing to do with the formalism, and just its ecosystem.
Also, a core policy of any development company, using any languages/frameworks/etc but more so if using JS currently due to the exceptionally high churn, is monitoring dependencies for liveliness so a transition to something else when they inevitably fade can be planned in advance and not implemented in a mad rush (leading to bad decisions) when deprecation notices start to arrive or, worse, after deprecation when security issues become apparent but not fixed upstream.
It needs to be policy, with someone who is responsible (or hands out responsibility but is where the buck stops), or it won't get done reliably. It isn't an interesting task, at least not for most people.
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.
It was an email system; before what's-his-name-The-Nanny's-husband "invented" it.
It's made me rethink the supposed "skill reset" that happens in software which leads to software developers leaving for other roles more often than other engineering disciplines.
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."
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.
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
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.
Really great team, great project, great codebase, loved a lot of things about it.
Then a leadership change happened. I've got a new job, gave my notice, and hopefully will keep in touch with the people I like here. Very bittersweet time.
that’s just capitalism
Human capital has value and appreciates over the long-term
Sorry, I'm old and jaded.
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.
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 :(
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.”