Every blog post that took off on Hacker News, ranked by the votes of its best submission. 1,339 posts.
The how, where, why, and when we communicate. Long form asynchronous? Real-time chat? In-person? Video? Verbal? Written? Via email? In Basecamp? How do we keep everyone in the loop without everyone getting tangled in everyone else’s business? It’s all in here.
To help meet growing demand, Apple today launched updated professional training and certifications for IT support and management.
Read more on Y Combinator's blog.
Twilio posts cloud communications trends, customer stories, and tips for building scalable voice and SMS applications with Twilio's APIs.
A long time ago, I performed technical interviews on a regular basis — I was recruiting candidates for the position of a programmer in a company. I had a simple, clear, and smart recruitment plan (I...
The what, why and how of effective teams
I’m a database nerd. Or, to be more precise, a DBMS nerd. But back in university, I avoided the Databases course at all costs. A little ironic when you consider I quit my job building IBM Db2 to work on CockroachDB.
if it doesn't come bursting out of you
A structure where software architects work on a team separate from the development team can lead to dysfunction, reduced quality, and poor morale.
Molly Graham helped forge a work culture at Facebook that's withstood huge amounts of growth. Today, she's something of a rapid scaling expert. Here's the key to doing it right, she says.
Over the course of my career, I've found two characteristics to be among the most important for software developers to thrive.
Tailscale's CEO talks about outages: what they are, why they happen, and how Tailscale is making them smaller and less frequent.
Learn 7 proven ways to say no to discount requests, protect margins, and strengthen customer relationships.
This is Part One in a three-part series examining how to become a data scientist. Supported by extensive research and expert opinions, it aims to provide a comprehensive guide to anyone looking to move into this field, irrespective of background and experience. The topic of Part One is: "What is Data Science?".
What's the real cost of interruptions? I illustrate all the context developers keep in their head and how it starts to decay immediately when interrupted.
