It's not just about salaries, but also the lack of a culture for seeding and financing. The fear of failed investments really dominates. Government and EU-backed financing is a joke, and I'm not even talking about the terms or amounts, but who actually gets them. It's pure waste of taxpayer money and should be abandoned.
I am not saying you are wrong, but Trump has shown exactly how quickly a "culture" can crumble down. Despite "checks and balances" the American democracy has done nothing to slow down the slide into dictatorship.
Nah. I'm using it daily for work and producing clean, fully controlled PRs. I don't get this denial, as the value is there, development is visibly faster, and without impact on quality (I'm controlling the agent, not vice versa).
There's plenty of good hardware outside the Apple world. Heck, whenever I get convinced to try Apple hardware or software, its quirks and obvious glitches put me off. Input lag is the topmost issue. It immediately washes off the "quality" impression. But I understand that Apple users are used to that and don't notice such issues.
IME this is a massive problem on windows and android and apple actually gets it right. They occasionally have stupid animations but those animations are responsive and trigger immediately. I don’t experience 3-5 second stalls (seriously the share dialog on android is a disgrace, and the windows start menu has become the least reliable part of the OS), and the input devices track to on screen movements - something I can’t say for win/android.
What do you mean? I haven't daily driven a Mac in almost five years now. I mainly run Linux and occasionally Windows on regular PCs. Whenever I open a MacBook, the first thing I notice is how reactive it feels. Sure, I could do without the animations, but I think that's a different issue. This impression is all the more pronounced if I'd been using Windows just before, but that's probably because Linux is a pretty bare i3 setup.
I mean mouse (Magic Mouse, precisely) and trackpad lag. The Magic Mouse also had random stuttering, a really horrible experience on brand new hardware. There were also other pain points. Returning to "standard" PC hardware and Linux was a real bliss.
LG Gram user here with Debian as a daily driver. Can confirm, maybe not 15h, but I don't think about charging. Plus, it's super stable, not a single crash or hang-up over years. It just works. I hope LG will keep this up and not mess up next iterations of the hardware.
Such "sleep(5)" is actually a milestone in a project, a milestone that marks the beginning of deterioration and the end of architectural changes. I've seen multiple pull requests with "sleep" and similar shortcuts, and worse, I've rewound coding agent context and changes because of such model suggestions. I'm responsible for informing management about the consequences of such shortcuts and why we have to take the correct, often more time-consuming and more expensive, approach to avoid project derailment in the long term. I believe that management picks employees. If they don't trust my judgment, then it's okay for me, but I don't feel obliged to be responsible for the consequences.
I'm certainly not defending such code, just saying that its out there and in some very successful projects.
If the managers where you work understand the dangers of taking on such tech debt and are willing to put in the resources to avoid it, consider yourself lucky, because in my experience that's not at all universal, or even particularly common, though it does certainly exist at some places.
As a Linux user, I feel like a different breed here: I'm pretty sure the software I'll be using 10 years from now will be pretty much the same, and I'm happy about that.
> I'm pretty sure the software I'll be using 10 years from now will be pretty much the same
It will be better, in ways I can't predict. But almost every detail of the interaction will improve somehow. But probably no big changes on the more mature parts.
Oh, and it will have one infuriating thing that people keep doing wrong because everybody insists it's the right way. I'll lose some small functionality for disabling it.
Whether it involves FAANG companies or not, a job is ultimately just a job. While it's nice to have such a company on a CV and to gain the experience, it is, in essence, similar to any other employment.
Eventually, you begin to consider the drawbacks, such as the monotony of the work or the exhausting nature of on-calls (which disrupt personal life). Then, an opportunity arises from a former colleague at another company, and the outcome is predictable.
Companies present numerous such inconveniences and actively introduce additional ones. Now, we are faced with mandatory RTOs, along with the continuous tightening of the screws and "cutting fat from the bone" (actual words of my company's CTO). Consequently, employees will depart, and it is often the high-performers who will seek opportunities elsewhere, as they are not afraid of the job market.
Well said. Languages are for implementation, not design. There isn't a single language that connects both. Also, every popular language has multiple patterns that communicate code intentions. We can add to that conventions added by frameworks, companies, and even teams.
reply