Ask HN: What is your best advice for a junior software developer?

Become a PL polyglot ASAP. Polyglot perspective is so much wider that that of a person who only knows one programming language.

Please please study the tools and the principles you use. No schooling will offer these things you learn then through experience. If on your own then that takes a long time. To expedite find rules like Sandi Metz's rules and S.O.L.I.D. principles, Learn OOP patterns and code smells. Don't worry if you don't understand why these rules and principles are in place just follow them. You'll eventually get there and the code you produce will not cause catastrophes later on.

But if anything this simple rule is the best: K.I.S.S. (Keep It Simple and Small) Make small things. If you ever find yourself saying "do this and then do that" your talking about two things and make them two things (separate functions/objects) and name them.

This, plus do only 9-5 jobs. Do not work longer than 40hrs / week.

Start learning about the following topics: public speaking, leadership, health/fitness, sex/relationships, personal finance, investing, business/entrepreneurship, marketing, and copy writing.

Where to live, what apartment to live in, where to work, who to become involved with, what bed to get, etc.

Nootropics. Cognition enhancement. A multivitamin + D & K + chelated/TRAACS magnesium supplement. Meditation and/or brainwave entrainment audio. Stress management. Ensure quality sleep.

Nootropics that increase verbal fluidity tend to be great in corporate environment, especially as it becomes clearer what leads to a promotion/raise.

Being promoted every other year (0 = entry, 2 = mid-level, 4 = senior, 6 = staff, etc) is conservative/typical/traditional. Fast risers get promoted every year. Move around, especially if your job isn't great or well-paying, to maintain a pace.

Though an engineer, still network. Weak ties are better than deep friendships when networking. Approach all as though they are friends. No need to let someone draining waste your time. Cast a wide net, but choose wisely.

Don't let them work you to the bone. Startups fail 98% of the time (78% if BS exits are included) and corporations typically don't care about you.

Your employer owns everything you develop on company time or using company equipment.

Understand the business, users, and political landscape at your company. Avoid getting involved in politics and gossiping. Commit to maintaining ethics and professionalism, then set everything up such that it doesn't sabotage you.

People tend to be selfish, two-faced, and unconcerned about you. Smile and be happy while remembering they'll likely stab you in the back with little hesitation.

There's being irreplaceable and there's them knowing/thinking you're irreplaceable. Only the latter matters.

Many years ago, it was estimated that 4% of executives/CEOs were psychopaths (versus 1% of the general population). A study released in 2016 now puts the estimate at 21%.

Read, read, read, read...

Avoid stagnating and blindly following whatever's said. Things change and the world has little problem leaving you behind. Staying fresh/competitive can be difficult, especially as many companies heavy-handedly try to push you into the trap.

Take-home salary: 20% to savings (max out 401k even if just up to company match), 30% max to rent, and 50% toward expenses.

house_price Car: down payment >= 20% of car's value, finance period = 4 years, principal + interest + insurance + license + registration + gas + maintenance = 10% of one's gross monthly income. Buying without taking a loan is even better.

Ageism. Software Engineers have an expiration date. If not in management or a founder/consultant by mid 30s, things can easily get difficult.

I have never had to do this nor seen anything like this behavior in my 6 years of work in the industry. This sounds incredibly in bad faith, and I would probably take it as a signal to go job search for a better work environment if I witnessed this in my day to day.