Then teach us. Advocate for us. Help us improve and understand.

A very large part of the problem is that the people who are knowledgeable are often the ones that bought into the whole lone wolf coder shtick.

Most junior people I work with are interested and want to learn, but between high demands, no time to do it and senior devs who focus only on their own problems - it’s very hard to know how to learn and improve.

We can and need to solve this but it requires that we work together and actually sit down to bridge the knowledge gap.

I wonder of this will also apply to npm then. I have a package that uses private packages which requires a personal access token to be present in env. Would make for nicer DX in our case.

Thanks for summing it up! I get the point of the article a bit more clearly now.

I wonder if “AI engineer” isn’t kind of superfluous in that case? It’s essentially just the new normal for software developers/engineers. Another API or tool to interact with to produce whatever product we’re building. Where does the specialist competencies come in, besides having a more intimate knowledge of the APIs and basic understand of how this tech works?

Interesting, but for some reason I found it very hard to read and get anything of substance out of the whole thing. Anyone care to help a dumb dumb out? Or is it just as fluffy as it seems?

Also, is the newsletter any good? Or is it mostly speculative non-fiction with words thrown around that don’t really amount to anything?

Don’t mistake my sarcasm for disinterest. I’m genuinely curious.