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.

It will be all right. I have been in a similar and made it out fine. Take a deep breath, step back and try to look at the big picture.

1. What are the immediate problems? How big are they really (what is the worst that could feasibly happen, is it really as bad as you think it is, vocalize them)? Filter out the things that aren’t actually a big deal, prioritize the rest and work on them one at a time. No more, no less.

2. Make it a priority to get yourself a diagnosis and a treatment plan. If your current psychiatrist won’t help you, look for another one.

3. Don’t worry about the big picture stuff right now. You’re not in the right headspace to make any big decisions. If you can put your studies on pause I would advice you to do so until things have calmed down. Make sure you have something going on though that keeps you active and occupied without being stressful or taking over.

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.

You seem to be correct. Additionally, it seems to not be handled properly in the in-app browser.

EDIT: Strike that second part. It’s just very confusing.

Not sure this is an ADHD thing but what will happen to me is I’ll be in a flow state, working on something, and feeling that my attention is about to run out while struggling to solve a particular problem. It’s incredibly stressful and annoying to know I have like 10 minutes tops or I’ll be stuck on this problem for a week (because God forbid I break it down into small enough chunks where it’ll be easy to pick back up tomorrow).