Comment

Comment by oatmealsnap

Code for the developer that comes after you, not for yourself.

If you’re going to implement a coding style, make it easy to follow. Provide a linter that works with multiple editors, and that can automatically fix common problems or design choices.

If the project is intended to be short-lived or you know for a fact your won’t update it after two years, then who cares. Try something new or get it done quick and dirty.

Pick the right tools and methods for the job, and make sure those methods decrease friction with your team (communicate and get feedback often).

parent oatmealsnap 6 years ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton