[mostertoaster]

Do you think maybe this is less of a big deal in the brave new world of chatGPT.

I know I have zero worries about having to code in a new language or framework with the ability to get answers so quickly to my dumb questions, but maybe that is because I’m still choosing languages and frameworks that are fairly popular and have so much online documentation that the LLMs know about them, and if something is really esoteric maybe the help wouldn’t be that good?

[nonchalantsui]

Due to the restrictions (short term at least) when it comes to training data and availability of documentation, I believe coding in a new language or framework becomes an even bigger mountain than usual due to chatGPT providing misleading information.

This is made worse if there are breaking changes in a new release that you are using. Even when the thing is popular, like Svelte, it was giving me outdated information before the introduction of Runes that often led to deadend packages or solutions that resulted in odd performance.

I'm sure eventually it'll be resolved, but ultimately I would only recommend people sticking to more traditional languages and frameworks that have been around for many years now and are relatively unchanging in order to benefit from chatGPT. Basically, the more projects you find using that thing on github, the better your outcome is going to be with current LLMs.

[sunaookami]

Maybe JS devs will learn to stop reinventing the wheel every half a year thanks to the knowledge cutoffs.

[brokencode]

I think companies are way too worried about hiring developers based on their specific technology they’ve previously worked with.

Unless maybe you are doing something radically different, like web development to graphics drivers or something.

Development skills are typically very transferable between languages, libraries, etc. And I think it’s healthy for developers to branch out and try new tech stacks from time to time.

I’d be more worried about a developer who doesn’t have the versatility to pick up something new. Because they probably also haven’t invested the time and effort to really understand what they’ve worked on in the past.

[PebblesHD]

Your example of web devs writing drivers is why I posed the question, as go is very much not a widely used web dev language, and the devs who know go may not at all understand the common web development patterns and practices.

Rather than the specific language, I’m more thinking of the domain, meaning ‘web devs who know go’ being a smaller cohort than ‘webdevs who know react’.

[iforgot22]

An LLM makes it even more beneficial to use popular tooling, because it's going to be better at answering questions about it. Meanwhile it's basically useless for whatever I'm doing at work with internal tools unless I have a pure language question (which for C++ is still ehh).

Maybe this is what will get people to stop reinventing wheels.

[pjmlp]

In the brave new world of chatGPT, developers will be in for a shock once they get good enough to generate executables.

It will be like looking for a job as Assembly programmer, when everyone else has moved into high level programming languages.

Better improve those architecture design and social skills.

[gf000]

If anything, LLMs require "boring tech" much more so than people.

Sure, it may know the language, but God save us from all the hallucinating in case of some niche lib