Ask HN: Are there software engineering areas that are safe from LLMs invasion?
Are there any software engineering areas that are safe from companies forcing you to use AI editors to work? Like low-level architectures, electronic, crypto, ai, etc.
Maybe other related or not so far areas like SRE. How is SRE these days? Can you still work the way you want to work? Are you being forced to switch as well?
11 comments
[ 4.3 ms ] story [ 36.9 ms ] threadBusinesses often rely on these systems - and they rely on the processes to protect them so are reluctant to adopt AI
LLMs make for great tech demos, but when it comes to writing code for production that actually does something new and useful, it hasn’t impressed me at all.
But they do work for pair programming. Which explains a lot of the tech layoffs we've been seeing.
* Accessibility. Accessibility isn’t a huge challenge unless you’re in a business with a pattern of largely ignoring it. Then it can be a huge challenge to fix. AI won’t be enough and it nightly likely require outside help.
* Speed. If you want faster executing software you need to measure things. AI will be learning from existing code that likely wasn’t well measured.
To be fair the code they produce is dogshit, so it isn't a problem.
2. Low tolerance for LLM-induced errors: - Network protocols / telecom software - Medical software - Aerospace, automotive
3. Performance-critical code: - Game engine / graphics engine development (probably an area where we'll see them soon) - Kernels, drivers, microcontrollers.
etc. Not all is lost yet.
AI is predictive. Most people will fall to a comfort zone where AI tells them what to do. But you should become an expert and be one of the few who are telling it what to do.