5 ms·
Maybe it's just because humans are not as creative as they think. Whatever you do, thousands of others have done the same already. So no need to pay a high leve
by croes 5y ago
Maybe it's just because humans are not as creative as they think.
Whatever you do, thousands of others have done the same already.
So no need to pay a high level programmer, just a mediocre one and the right AI assistant gives the same results.
- jqbd 5y ago> So no need to pay a high level programmer, just a mediocre one and the right AI assistant gives the same results. I think of it as not needing juniors for boring work, all you need as a company is seniors and AI.
- sterlind 5y agowithout juniors, how do you get more seniors?
- spaced-out 5y agoMaybe programmers will adopt a similar model to artists and musicians. Do a lot of work for free/practically nothing hoping that some day you can make it "big" and land a full time role.
- kyawzazaw 5y agowe already have that with unpaid interns and PhD students
- Jeff_Brown 5y agoAnd most people who consider the job are driven away by the economics of it.
- ganzuul 5y agoThat is already the recommendation. Pick an open source project and contribute.
- 9dev 5y agoSo where do these seniors come from?
- failuser 5y agoThat’s beyond the planning horizon.
- Dylan16807 5y agoYou could have a much smaller pool of juniors/journeymen that are focused on maximum learning rather than amount of output.
- juancampa 5y agoQuite the opposite. Menial work will be automated away (e.g. CRUD) and only good programmers will be needed to do the more complicated work.
- IshKebab 5y agoI think it's more that this tool is only capable of automating the non-creative work that thousands have done already. It's still insanely impressive (assuming the examples aren't more cherry picked than I'd expect).
- etripe 5y agoWith an AI assistant, in the best scenario, you'll get a "wisdom of crowds" effect on implementation details and program architecture. At worst, you'll get a lot of opinionated code bloat and anti-patterns as suggestions. For most backend programming jobs, the challenge is not in writing complex code but figuring out what the business wants, needs and should have in the first place and distinguishing between them. Figuring out how to integrate with existing systems, processes, fiefdoms and code. Knowing when to say yes and no, how to make code future proof, etc. This is a task fundamentally unfit for what we currently call "AI", because it's not actually intelligent or creative yet. On the frontend, it becomes even more nebulous. Maybe Copilot can suggest common themes like Bootstrap classes for a form, CSS properties, the basic file structure and implementations for components in an SPA, etc. As I see it, the main challenge is in UX there, not the boilerplate, which again makes it about understanding the user, figuring out how to make UI feel intuitive, etc. Again: unfit for current AI. I cannot offer any opinion on the utility for actually complex, FANG-level code, for lack of experience.