[Sean Goedecke]

This is very good. It's advertised as a piece about shipping in big tech companies, but honestly, I think it's true of many smaller companies too. It's not true in the smallest startups or for organizations with certain kinds of engineering cultures - but I suspect they may be in the minority.

"What does it mean to ship? It does not mean deploying code or even making a feature available to users. Shipping is a social construct within a company. Concretely, that means that a project is shipped when the important people at your company believe it is shipped."

Software engineering isn't a technology business: it's a people business. You're building tools that solve real problems for real people, and you're doing it inside an organizational structure that is also made of real people. There's no way to get around this: unless the organization is exceptionally organized around engineering needs (which many small and medium tech companies are!), you will have to navigate these sorts of interpersonal dynamics.

This hits the nail on the head for just about everybody:

"I think a lot of engineers hold off on deploys essentially out of fear. If you want to ship, you need to do the exact opposite: you need to deploy as much as you can as early as possible, and you need to do the scariest changes as early as you can possibly do them."

It seems counterintuitive, but again: if your goal is to ship (and it probably should be), you need to focus on doing that.

#Technology

[Link]