Developer Lessons Learned
- If a process isn't working and feels like a bad idea, don't force it. Use it to make lives easier, and don't introduce unnecessary red tape.
- Explore other languages. If you're in javascript all day, you're missing a lot of interesting language features.
- Have hobbies outside of coding.
- Go deeper than the web world. A great yearly re-read is this article on memory.
- Disagree and commit. Arguments are okay, but don't die on a hill.
- In largs orgs, speak the same release language with Semver.
- If you have a team of juniors who have poor commit practices, start with good habits using something like Conventional Commits.
- Don't block PRs due to nitpicks.
- Don't take PR reviews personally. They're great feedback and help you grow.
- A good mentor may never come. Enjoy learning and you'll discover the right way to do things along the way.
- Unless you own the product and really care, you will only have two of: features, speed, and quality.
- Setup observability with OTEL.
- A good software service requires optimizing, so make room for it in your roadmap.
- Use typed languages.
- Version APIs to help with breaking changes.
- E2E tests and integration tests are the important ones.
- Composition over inheritance.
- As a manager, make the most use of your best developers, and don't stick them in all of the meetings.
- Code should be simple and easy to read. Learn how to name things. Do not write fancy code.
- Be independent with projects, reach out to other teams, and ask questions.