ederamen
This is what I've been feeling too. It feels increasingly like the professional world has become a tower of scams. It's not worth building technical skills or focusing on quality; your boss doesn't know or care what good work looks like, he/she just wants your work to look good enough to his/her boss, who knows even less about the actual work being performed. And everyone reports up to an MBA CEO who was brought in from a completely different industry.
I want to work in an industry where skill, diligence and expertise is rewarded and respected, but from what I'm seeing political ability is 95% of the game and caring too much about the work is a career liability.
Uv combined with type hints reaching critical mass in the Python ecosystem, and how solid PyLance is in VSCode, feels so good it has made me consider investing in Python as my primary language for everything. But then I remember that Python is dog slow compared to other languages with comparable ergonomics and first-class support for static typing, and...idk it's a tough sell.
I know the performance meta in Python is to...not use python (bind to C, Rust, JVM) - and you can get pretty far with that (see: uv), but I'd rather spend my limited time building expertise in a language that isn't constantly hemorrhaging resources unless your code secretly calls something written in another language :/
There are so many good language options available today that compete. Python has become dominant in certain domains though, so you might not have a choice - which makes me grateful for these big steps forward in improving the tooling and ecosystem.
I might be able to get it replaced if support decides to be generous, but dealing w/support is a pain, and the alternative is buying a $400 replacement every 2-3 years when the battery starts to fail.
I don't have to pay the monthly subscription - they had a deal where you could buy a third gen ring (at full price) and would get lifetime access without paying a monthly subscription. Despite that it still doesn't feel worth it to me to have yet another device I have to babysit (remember to sync with the app every day, remember to wear, remember to charge) and pay hundreds of $ to replace every 2-3 years. With the subscription cost, there's no way this product's value proposition makes sense for me.
As a novice C programmer, the simplicity and immediacy of results opened my eyes to how C can feel as productive as higher level languages with robust standard libs.
If it were in their financial/competitive interest for PWAs to be amazing on iOS, they would be.
Unfortunately for us this would circumvent their 30% app tax, so they'll be dying on this hill.
...but when I see how petulantly defiant Apple's responses to other regulations which threaten their lock-in strategies have been, I'm not optimistic.
If you want to develop for Apple's devices, you have to sacrifice your future career options with any other tech stack/vendor by investing your limited time into skills that are only relevant in the Apple ecosystem.
Then you have to hope that it's still financially viable to do software dev in Apple's world for the next few decades - which given their demonstrated behavior of scraping back more and more of the pie for themselves and their shareholders, seems like a risky bet.
The intolerable part for me is that after you've spent years investing in learning their (non-portable outside of Apple) languages and APIs, they can reject anything you build for mobile for any reason, and you ultimately have zero recourse.
In other areas of software you could take the skills you've learned to your next job/project - but as Apple is moving more towards declarative frameworks where you aren't supposed to think about what's going on under the hood (I.e. SwitfUI), the amount of actual deep, transferable software engineering skills you gain from working with these frameworks approaches zero.
The investment just doesn't feel worth it to me, when there are so many other things I could be learning to advance my career.
They've made it practically impossible to write native cross platform code that runs on IOS, and they've everything they can (within political limits) to prevent web apps from being able to compete with native apps.
https://www.bts.gov/newsroom/2017-north-american-freight-num...
https://www.aar.org/facts-figures#:~:text=Freight%20rail%20a....