You can bring in a person off the street and have them run a prompt to generate code.
12 replies (most recent on top)
@ks what's rude about saying good luck to him?
No need to be rude, it's clearly possible to make such a transition and many people have. Might be good for his health too.
@f1 good luck to your middle-aged hubby, going from a desk job to a trade. LoL
Yup and Charlie is going to take full advantage of that by letting all the Americans go and having India do the code prompting.
Also there will be no need for playbooks or anything like that because Charlie's also going to give them an AI agent within co-pilot that will allow them to ask the questions like "how do I revert code I pushed".
My husband has his masters degree in AI + 20 years experience… and he is now spending evenings/weekends in trade school because he and all of his friends/coworkers are pretty sure most tech careers will be obsolete within 5 years.
the fact that they are removing jetbrains products, even the community editions, to facilitate of the deeper metrics available from copilot/vs code integration is a huge clue they don't care about the experience of, or expect human to be working with code in ide's anymore.
theres no question alot of busy work will be eliminated by auto-generated pull requests from centralized groups that developers just sleep-walk their way through approving (understandably), and if they have no problem with that, app teams at the bottom of the hierarchy will shrink and be consolidated, especially us based ones. work will flow upward or to india. however there are alot of 'architects and solutions engineers' who haven't touched code in a long time so I don't know.
@OP this isn’t going to trigger anyone. I am in Tech but not a “coder”, surely people will adopt this mindset and move forward with it. Those orgs will either die a horrible death or make a catastrophic error quite rapidly, be able to recover from it and then roll back their thinking and survive.
Churning out code to satisfy a request is one thing. Understanding what that code is doing, how it can affect any other work flows and knowing how to troubleshoot it when it doesn’t work is a whole other beast.
OK, so I write some software. Untrained in it but over the last 40 years I've taught myself assembly, basic, C and python.
Over the past year I have been vibe coding, but....you have to understand whats being built so when it doesnt work, you have a clue. So its true, simple stuff can be coded that way and I love it...because I need something that works fast, not really elegant, just need to get the job done. Its gotten better over the last 6 months too. Simple mistakes it used to make are no longer. I want a change in the text displaying? i just say make this list of changes. minute later its done, faster than I could have found each line, changed and started it again.
So vibe coding has its place, but more so with helping you do the job, not replace the job.
Is that why my receipt has semicolons at the end of each of the 7 different pumps I get in my Latte?
I agree that CS is the new Communications major. CS grads actually have one of the highest unemployment rates right now. Honestly, it's one of the easiest STEM degrees to get, and the pay-to-difficulty ratio was unsustainably high for a long time. Going forward, we're going to see average CS salaries drop every year, and grads will face longer bouts of unemployment until they give up and take jobs as baristas. The old advice used to be 'get any degree and you're good to go.' Now, universities hand out diplomas like candy, inflate everyone's grades, and give them a false sense of security.
Ah, troll thinks they found a new trigger.
I would love to see that person off the street debug a run-time issue with vibecode.