I really hate, how it will gladly generate dozens of lines of complex algorithms, when it doesn't find the obvious solution right away. Particularly, because you will readily find colleagues that just do not care.
They probably stop reading the code in detail when it's sufficiently long enough. And when you tell them that what they've checked in is terrible and absolutely unreadable, they don't feel responsible for it either, because the AI generated it.
It's like those headlines "bicyclist hit by car" or similar, where you might think the car developed a mind of its own. I guess, we are on our way there, though, with self-driving cars and such...
This also took me far longer to realize than I'd like to admit:
Cows only need to be milked after a pregnancy. And pregnancies lead to babies. In effect, we're talking about 5-6 calves over the lifetime of 1 milk cow. Some of those calves will become the next generation of milk cows, but you're not gonna keep those 4-5 extra calves around. Those will get slaughtered.
So, yeah, consuming milk products directly leads to cows being killed...
In my corner of the embedded world, it feels like everyone is practically jumping to integrate Rust. In the sense that vendors which haven't had to innovate for 10+ years will suddenly publish a Rust API out of the blue. And I'm saying "out of the blue", but I do also regularly hear from other devs, that they've been pestering the vendors to provide a Rust API or even started writing own wrappers for their C APIs.
And while it's certainly a factor that Rust is good, in my experience they generally just want to get away from C. Even our management is well aware that C is a liability.
I guess, I should add that while I say "jumping", this is the embedded world where everything moves extremely slowly, so we're talking about a multi-year jump. In our field, you need to get certifications for your toolchain and code quality, for example, so lots of work is necessary to formalize all of that.
Die Spieleindustrie hat da auch echt so ein bisschen ein Problem. Einen spaßigen Gameplay-Loop bekommt jede Solo-Entwickler*in hin. Mit mehr Budget kann man dann teilweise andere Gameplay-Loops bedienen, sowas wie zum Beispiel Echtzeitstrategie oder VR. Aber spätestens bei AAA-Budget holt man aus so einem Gameplay-Loop nichts neues mehr heraus.
Stattdessen werden dann oft weitere Gameplay-Loops neben dran geflanscht (in so einem GTA kann man Autofahren und Schießen und Roleplay und Minigames usw.). Und dann wird aber auch Beiwerk geschaffen, das um den Gameplay-Loop herum existiert, also Story und Lore und Open-World und Gedöns. Und dieses Beiwerk ist unausweichlich weniger spaßig als der Gameplay-Loop. Es nimmt Zeit weg, die man im Gameplay-Loop verbringen könnte. Im Schnitt wird das Spiel dadurch weniger spaßig.
Jetzt muss nicht jedes Spiel maximal spaßig sein. Es gibt zum Beispiel absolut eine Daseinsberechtigung für Story-lastige Spiele, die auch mal schwergewichtige Themen aufarbeiten. Aber wo es eben dann doch zum Problem wird, ist wenn AAA-Spiele gar nicht mehr maximal spaßig sein können, sondern immer krampfhaft dieses Beiwerk haben müssen, weil man das Geld ja irgendwie ausgeben muss.
Yeah, particularly the broadcasting really irks me.
That is an opinion you can hold for yourself and then make compromises as you encounter reality. I do expect programmers to hold strong opinions.
But when you broadcast it, you strip yourself of the option to make compromises. You're just saying something which is going to be wrong in one way or another in most situations. I do expect programmers to be smarter than that.
Like, I understand that brains are supposed to be wrinkly and there's an actual disorder where the brain doesn't have those wrinkles, which leads to developmental delays: https://en.wikipedia.org/wiki/Lissencephaly
But it still sounds to me like you're just calling them "smooth" as in "cool".
I mean, for me, it's also mostly a matter of us doing embedded(-adjacent) software dev. So far, my company would hardly ever choose one stack over another for performance/efficiency reasons. But yeah, maybe that is going to change in the future.
Large shared codebases never reflect a single design, but are always in some intermediate state between different software designs. How the codebase will hang together after an individual change is thus way more important than what ideal “north star” you’re driving towards.
Yeah, learned this the hard way. Came up with an architecture to strive for 1½ years ago. We shipped the last remaining refactorings two weeks ago. It has been a ride. Mostly a ride of perpetually being low-priority, because refactorings always are.
In retrospect, it would've likely been better to go for a half-assed architecture that requires less of a diff, while still enabling us to ship similar features. It's not like the new architecture is a flawless fit either, after 1½ years of evolving requirements.
And ultimately, architecture needs to serve the team. What does not serve the team is 1½ years of architectural limbo.
I mean, don't get me wrong, I also find startup time important, particularly with CLIs. But high memory usage slows down your application in other ways, too (not just other applications on the system). You will have more L1, L2 etc. cache misses. And the OS is more likely to page/swap out more of your memory onto the hard drive.
Of course, I don't either sit in front of an application and can tell that it was a non-local NUMA memory access that caused a particular slowness, so I can understand not really being able to care for iterative improvements. But yeah, that is also why I quite like using an efficient stack outright. It just makes computers feel as fast as they should be, without me having to worry about it.
I posted that comment, because people generally wildly underestimate how common depression is. Because of that and because they don't know how to deal with depression, they will look for other "explanations", like yeah, sure, my kid's just lazy. And that even despite these other "explanations" being extremely toxic and worsening depression.
So, this basic fact, that depression is among the most common disorders, would be part of my rebuttal. In hopes that she can accept that and help you work through it, like an adult should, rather than this silly game of peek-a-boo, where she hopes for it to not exist, so long as she doesn't believe in depression. That is not helping anyone.
I would expect larger corporate projects to do so. It is something that one needs to know about and configure, but if one senior webdev works on a project, they'll set it up pretty quickly.
Major depressive disorder affected approximately 163 million people in 2017 (2% of the global population). The percentage of people who are affected at one point in their life varies from 7% in Japan to 21% in France.
Whut? Are you supposed to pay money for a singular splash of smelly water?