Not separating out your work and personal life can screw both work and life. It will lead to burn out eventually

Don’t flame people. Ask polite questions. Like can you explain this instead of I didn’t understand it

Simple things like being methodical, organized, and have a good process to build new things can take you very far.

You can't become a programmer if you don't write code. You can't become an exceptional programmer if you don't read code

Be careful who you vent to at work.Just because they listen, it doesn't mean that they are your friend or have your best interests at heart.

Approach work as a way to maximize your free time

Being inexperienced and willing to learn is better than being experienced and thinking you know it all.

Mindset is important. If you tell yourself you're an above average developer, you're more likely to improve your craft because it's part of your identity.

Do not bash any idea or belief based on your past experience. It is true until you have a clear reason to think otherwise.

Own your calendar. Have enough time carved out for "deep-focus" time, 2-4 hours of uninterrupted time, plan dev tasks to line up with these and aggressively block out time as needed.

Keep detailed notes when in meetings, find a system that works for you where you can easily index and search things.

Keep detailed notes about your contributions, what you've done, how you've helped others, discussions led, etc. Invaluable for performance reviews and promotions and in general seeing where you're spending time. I used to keep this in a public .plan file, now-a-days it's shared doc that I let my managers see.

Do not sacrifice your health. Carve out time for exercise. Carve out time for learning. It's sometimes nice to work late for that big block of quiet uninterrupted time, but schedule it on your terms and only once or twice a week.

Know your toolsets. You should be able to easily execute, test, profile, and debug. If this is painful, then investments need to be made on your codebase.

When building systems, focus on interconnectivity and getting a base skeleton working first and then fill in details. Avoid "big-bang" integrations, they never work, and can result in last minute surprises. Strive to have the skeleton component building and working daily as you add in details.

Improve documentation for the next person. That person may be you.

Learn jq, awk and sed.

Pair with more experienced devs and if they do something that seems magical, ask how.

Read Getting Things Done and learn about Inbox Zero. You may not end up using these methods, but just learning how they work will really help you figure out what works best for you. Pro tip: they actually work.

Hone your skills. Remember to take some time to learn things, even if it's just a new Vim command or something.

Be nice to people. People who like you may propel your career in unexpected ways. This happened to me. Help people learn and grow. Don't try to compete with people in your team.

Communicate. Learn how to do it if you have trouble. There are a lot of people with brilliant technical skills that don't end up having great careers because they can't communicate.

Work 8 hours per day. Learn how to focus on those 8 hours and actually be productive. Don't work more than that, try not to work less than that. It's all you'll ever need to be above the curve.

Focus on iteration speed. Ship small changes as fast as possible. There’s no point trying to sit back and have deep strategic thoughts about what needs to be done until you’re so proficient at the basic mechanics of writing and deploying changes that it is instant and effortless. Just pick a clear, important improvement to be made to the system, find the tiniest change that makes progress toward that goal, do it and repeat as fast as possible. This should be your general modus operandi for a long time in your career.

A second point I would make, get yourself in a position (company/team/whatever) where you get exposed to lower abstraction levels. Mid/late game in your career it’s important to have an understanding of operating systems, databases, networking, memory layout, etc. Otherwise you plateau.

There's one good meta productivity hack: pair with other devs. You quickly learn so many tips and tricks that no one even thinks of asking about that have been acquired over a long time. Anything from specific command-line-isms to sequencing operations and how to think of them.

Don't be a jerk. How you treat people matters.

Why is that a productivity hack? Because medium-to-large-scale software development is all about communication. You don't initially know what your code is supposed to do. It isn't obvious; someone has to communicate that to you. You don't know how it's supposed to work with other code; someone has to communicate that to you. Being a jerk makes other people less willing to talk to you.

If you find yourself doing something that's the same, try to automate it. Stuff like bat, ksh, powershell, etc.

Email folders and filters to sort what is important and what is just noise.

Write notes use a PKM system like Obsidian.md or similar