Get the latest tech news

A bunch of programming advice I'd give to myself 15 years ago

I finally have the feeling that I’m a decent programmer, so I thought it would be fun to write some advice with the idea of “what would have gotten me to this point faster?” I’m not claiming this is great advice for everyone, just that it would have been good advice for me. If you (or your team) are shooting yourselves in the foot constantly, fix the gun I can’t tell you how many times I’ve been on a team and there’s something about the system that’s very easy to screw up, but no one thinks about ways to make it harder to make that mistake.

I decided to fix it, and it took ten minutes to update our subscription layer to call subscribers on the main thread instead, which eliminated a whole class of crashes and removed mental load. But it’s also really easy to write code that follows absolutely every best practice, with 100% test coverage, and has been fuzz-tested and mutation-tested for good measure – your startup will just run out of money before you finish. This makes it easy to pull out bits of code and play around with it to get a better idea what’s going on In the staging environment, I limit parallelism to 1, so that it’s easier to visually parse logs

Get the Android app