Yeah, I understand your frustration. This is an issue with Paramiko which pyinfra relies on. We have been debating moving away from Paramiko, but it will take a while for that to materialize.
I'm arguing against it with the other two arguments you didn't address.
Yes, AI will change the role of software engineers - and it's my personal belief that in the next couple of years this change will be smaller than many people think. But no, AI will not replace engineers like Mark Zuckerberg thinks.
Why not? Because AI makes too many mistakes and AI is not going to support and maintain your code.
I don't understand why so many people subscribe to this "prediction". It seems unsubstantiated hyperbole to me.
There are a few reasons why I don't believe AI will replace programmers anytime soon:
1. The job of a developer/engineer entails so much more than writing code. Figuring out what the business wants, turning that into a good (system) design, etc. takes up more time than the actual coding itself.
Unless of course you take "programmer" literally, but I have not seen many companies that still hire programmers in the most narrow sense, that only focus on writing code.
2. Support and maintenance is a huge part of the job that I don't see AI doing. Theoretically you could let humans focus on that part, but I believe support and maintenence will become much more costly if the people doing they job have no familiarity with the code because they didn't write it.
3. As evidenced by many comments in the thread elsewhere on HN about the announcement of Claude Sonnet 3.7 AI still routinely makes mistakes that are super easy to spot and verify. As long as that remains the case, it's going to be detrimental to the success of you company if you give AI too much autonomy.
I know people will argue that AI is evolving so fast that the above will be solved soon. But I think all three aspects I mentioned are such fundamental roadblocks that they won't be solved soon.
What I do believe in is engineers becoming so much more productive as AI evolves.
I experienced the same in my previous job. And it makes me wonder: what do those applicants hope to get out of this ruse? It's not like hiring managers will think "oh, we've gotten this far into the process, we might as well arrange a lengthy and expensive visa process for them"
So now you need a framework on top of React - itself a framework. Has React really become so complex that mere mortals cannot comprehend it without another abstraction layer on top?
And the first suggestion for this extra abstraction layer is NextJS, developed by a company with a vested interest to make it hard to run your app on anything else than their own service.
Seems to me that the time is ripe to disrupt frontend development yet again and introduce a simpler stack.
In a way that makes it worse. A community fork that is repurposed by a select few to make money off of work that those few did not do for the most part.
In certain areas of the US maybe. I believe the average wage in the EU is actually higher than in the US. Need to look up the Source, which is hard because I'm on mobile right now.
I find it interesting that another comment states that they love Kagi exactly because Kagi uses all their search terms as opposed to Google. Not doubting your experience here, but I wonder how those experiences can differ so much.