developerjackWelcome good readers!
This will be a short weekly post as I curl up on my couch battling a cold.
We fired our top talent. Best decision we ever made.
This one went viral – so if you missed it here it is. A fascinating read about ‘ninja coders’ and the impact they can have on a project, team and company. In it I saw a few of my own bad habits so it also reads as a wake up call to smash those head on.
Read the post.You fired your top talent. I hope you’re happy.
Alas this one got slightly less attention but its the reply to the afore linked post. This one is for all the managers out there thinking of firing their top talent
Read the post.Code Design Principles for Public APIs of Modules
Most of the code I work with was crafted by someone else’s brain and even when I’m writing my own code I always have to think about how someone else might be able to understand and contribute to my (self indulgent) masterpiece. These principles are an excellent starting point to think about how to improve another readers ability to understand your logic and the domain in which you’re thinking.
Read the post.API design: Choosing between names and identifiers in URLs
URI? URN? GUID? huh? This is an excellent post from Google’s GCP team exploring the addressing and identifying of resources in an API. I’m in love with their phrase ‘Identifiers are for look-up, names are for search’ – it’s so very true in the way we think about discovering data in an API.
Read the post.Don’t forget that GitHub Constellation is on this week (I’ve some announcements to make about pride.codes), and #hack4refugees is on next weekend!
Until next week!
@developerjack
