Ask HN: Anyone out there trying to help new devs avoid career pitfalls?

I'm interested in having less experienced people see those things before it takes a toll on their career, or at least find a cause where these actions are currently being taken.

Real life examples of "lost common sense" that people can help new developer avoid:

* I thought it would be okay to be unemployed a few months so long as I have savings to tide me over. Up until recently did I not know it also makes it harder to bargain for higher pay.

* Didn't change my job search strategy for a long time after graduating. For the first 7 years I was only using Craigslist for local jobs and didn't consider many bigger boards or alternative avenues (direct apply on corp websites, contact recruiters first)

* I don't really keep up with my co-workers outside of work for other things like referring them to jobs etc. so my network is rather weak for getting job leads.

Things that I did not know I want to see others help prevent these knowledge gaps and fill them, before they start their career or when they are early in their career. Especially for the self-taught people.

I'm still learning a lot myself, as I still haven't yet succeeded in re-launching my career. But I'd like to find out if there are others out there who are making efforts at preventing new developers from making the same mistakes I did. Having people in your life generally raising your awareness that there’s more out there and having drive and motivation is crucial, and I especially think the former is a bigger problem.

False, it shouldn't make it harder to bargain. Part of planning to be unemployed is making sure you don't need to accept the first offer once trying to go back to working.

The second part is one just says they were doing freelance or consulting work while they just worked on personal projects.

1. Only listen to people who have walked the walk. Many people with limited tech exp will try to advise you on how to build products/tell you what to do, don't listen to them unless they've done it successfully and it was they that did it -- not some other team they 'advised' or 'managed'.

2. Write stuff down. Promised a raise at X funding point? Write it down. Bring it up and don't let it go.

3. Avoid surrounding yourself with people who sound corporate unless you want to sound like that.

4. Be careful about hiring/working with big co folks for small companies/startups. They often bring politics etc. in and seem on average to be less creative. This is a sweeping generalization and a bit harsh, but basically if you want to be involved with startups, associate with people from startups. Build your network around that.

5. Be careful with first time founders, and see if you can get a gauge on their empathy. A good way to do this is invite them out to lunch and see how they treat the wait staff.

6. Build side projects and don't be afraid to look stupid/ask questions. That's how you get to be the best.

I have learnt a lot of things the hard way in 20+ years in tech / corporate life, there are a lot of truths that can't and won't be spoken about inside a big company. I've also done some career coaching in the past few years, and I think something specific for tech / development would be pretty good for a lot of entry level people.

I guess your 3 bullet points are really just general career issues and not really tech focused (which is fine, a lot of this stuff is pretty universal and probably applies just the same to accountants), but I think maybe mixing in some more tech focused advice would be helpful. (e.g., you really need to learn some basic shell / scripting, grep, git... if you have some complicated system that is failing, you might need to remove some complexity instead of adding more, etc.).

Maybe share a link / email address?