4 ms·
Steve Yegge has laid this thesis out: https://sourcegraph.com/blog/the-death-of-the-junior-developer https://sourcegraph.com/blog/the-death-of-the-junior-deve
by bryanlarsen 2y ago
Steve Yegge has laid this thesis out: https://sourcegraph.com/blog/the-death-of-the-junior-developer https://sourcegraph.com/blog/the-death-of-the-junior-develop...
He also has some good content out there on how to program using LLM's. He calls it Chat Oriented Programming, aka CHOP. That's a good term to Google for.
- whstl 2y agoI enjoyed the examples. My previous company's lawyers really had success writing complex contracts in LLMs. The writer one really hits home: a friend who's a writer is able to make amazing stuff with ChatGPT, because he knows how to do it himself. I can only make stupid shit, because I while can recognise quality writing, I don't really know why. Similarly, I see the same thing happening with junior devs: a lot of them just can't get the answers I get out of Copilot or ChatGPT. I have to sit next to them and tell them what to ask the LLM, or when to say no to a proposed solution. Similarly, I can get started myself on Computer Vision and Machine Learning projects with LLMs, but I need to hand over to a proper CV or ML Engineer to get the last 10% done.
- lgas 2y ago> Similarly, I can get started myself on Computer Vision and Machine Learning projects with LLMs, but I need to hand over to a proper CV or ML Engineer to get the last 10% done. Unless by "Computer Vision and Machine Learning" projects, you mean you are trying to develop new approaches to computer vision or ML, I don't see why you would need to involve a CV/ML engineer? The stuff is all generally packaged as re-usable libraries like everything else, no?
- whstl 2y agoI'm definitely doing new stuff that's not available on ready made libraries or as paid APIs.