The blog is currently being ported from WordPress to over 12 years of static pages of content.
If there's an article missing that you're hoping to see, please
contact me
and let me know and I'll prioritize getting it online.
February 25, 2014
Found a great article on http://venturebeat.com about 10 best practices for developers, curated from engineers at some of tech’s biggest sites such as Google, Pinterest, and more.
http://venturebeat.com/2013/11/06/10-best-practices-from-top-coders-at-google-pinterest-more/
The article is worth reading, but here’s a summary:
- Think carefully before you choose your first language
- pick a language based on the community
- You’re no code monkey!
- understand the motivation behind why you’re being asked to build something
- Stay agile and don’t stop shipping
- fail fast, always be testing, release early and often, practice TDD
- Stay in control of the testing process
- TL;DR: TDD is awesome, do that.
- If you’re a freelancer, learn to say no, even to money
- assume all estimates of time and money are half what they should be
- Don’t rest on your laurels — theory matters, but practice matters more
- doing > reading
- side projects are awesome, but focus on one at a time
- Peer review is your secret weapon
- pair programming is awesome because feedback is essential
- Avoid premature optimization like the plague
When I prematurely overengineer my code. #programming pic.twitter.com/khF1DqTVTW
— Victor Porof (@victorporof) February 18, 2017
- You write your code once, but people will read it thousands more times
- pretend the person maintaining your code is a violent psychopath who knows your home address
- It’s a noble profession. Use your skills for good.
- don’t do evil