131–140 of 232 posts
I'm currently looking for a new job in development... should I be looking for an exit instead?
Imagine we had this technology 20 years ago and we switched to fully automated web design. I bet all web design would still be deeply nested tables. I doubt that something like React, Vue, Svelte would exist.
As I see it, the issue with using tables for layout is that they made it difficult for humans to maintain and iterate over time, but I don't have a problem with an LLM working at that level. Equivalently, I don't care that the machine code that my system gets compiled into is full of GOTOs if I don't ever need to concern myself with that level.
Not to mention the inefficiency of a pure table approach, so much wasted render time and energy.
So who is liable if the AI makes severe mistakes? Not that MS has been held accountable for all the security problems they've had recently.
I don't think so AI will replace SW jobs. It will definitely change the way engineers work. Software development involves: 1. Understanding the requirement 2. Solving the problem with given constraints (and thereby innovate) 3. Talking to stakeholders 4. Code (& unit tests) 5. Review #4 6. Troubleshoot in testing 7. Troubleshoot in prod, both perf & subtle issues (this is hard) 8. Take the input from #6 & #7 and use…
It’s been a good run everyone, good luck out there
I'm a software and product guy; what I don't get, is how we're going to replace us lowly engineers and not a substantial percentage of a company's Human stack. Close to engineering, what about the SCRUM masters? The testers. What about the product owners? What about devops? Further from us, what about the people signing up on our vacation? Or the ones signing up on our daily budgets when traveling, or hell, even the…
I'm currently looking for a new job in development... should I be looking for an exit instead?
Afterwards, you better be in the top 10% of engineers, or be doing something novel like research.
I don't think so AI will replace SW jobs. It will definitely change the way engineers work. Software development involves: 1. Understanding the requirement 2. Solving the problem with given constraints (and thereby innovate) 3. Talking to stakeholders 4. Code (& unit tests) 5. Review #4 6. Troubleshoot in testing 7. Troubleshoot in prod, both perf & subtle issues (this is hard) 8. Take the input from #6 & #7 and use…
Earlier quoted context omitted.
Yeah. The shocking speed of progress on AI - especially for coding - tells me quite clearly what the future holds for much of software engineering. Despite the human factors (yes, requirements gathering and specification is messy) our profession is intrinsically automatable at the end of the day. Being in denial is pointless.
I am quite confident my job is not in danger. Sure - scaffolding and boilerplate can be automated using ML - but problem solving - not at all. The reason is simple - to find a solution is to create a program that has a specific set of properties. This - by Rice's Theorem - is not possible to realise using a Turing Machine. So as long as the solution search space is small (ie. we are talking about very similar program…
I don't think so AI will replace SW jobs. It will definitely change the way engineers work. Software development involves: 1. Understanding the requirement 2. Solving the problem with given constraints (and thereby innovate) 3. Talking to stakeholders 4. Code (& unit tests) 5. Review #4 6. Troubleshoot in testing 7. Troubleshoot in prod, both perf & subtle issues (this is hard) 8. Take the input from #6 & #7 and use…
I think most people would agree that AI will probably advance enough in the next 100 years to make engineers obsolete. Some people might think 100 years is actually 5/10/20/50, but it's going to happen unless AI is heavily regulated.