3 ms·
I don't agree, it's not like software engineering is the be-all and end-all of automation. Software engineers usually build something based om some sort of requ
by donkeyd 10y ago
I don't agree, it's not like software engineering is the be-all and end-all of automation. Software engineers usually build something based om some sort of requirement. When the development part is automated, there's still a need for requirements. There will still be a job figuring out what to create in the first place.
And then there's the idea that new jobs are created when others disappear. I'm sure there will be jobs in the future that we can't imagine yet. Maybe we'll actually forcibly create new jobs in order to keep people busy.
- visarga 10y agoSoftware is automation: compilers automate a large part of writing new machine code, libraries automate by reusing older code. If it can be automated, it has been automated. We have existed under the pressure of automation since the beginning of our field, we can take it.
- oblio 10y agoI don't know about you, but in a lot of situations when I'm asked to build something I have to actually figure out a lot of those requirements myself, as I go along. Theoretically that role is generally called "business analyst" or "product manager" or "product owner" but you know the difference between theory and practice. If we'd ever reach that point of automation my money's on many programmers just switching to some sort of "business analysis". After all, this job is all about making decisions, tons of micro-decisions.