wise men learn from other people’s mistakes
As Zack from Github says “You can have the best, most comprehensive test suite in the world, but tests are still different from production”, amen! — and he says a lot of other useful things as well:
Twenty-two good pieces of advice for software engineers including:
From American CEO, fifteen essential CEO skills:
And then, from one of the smartest, most inspiring, CEOs I know:
Unfortunately, I’ve definitely met these people:
From the article: “There’s a familiar path now to SaaS companies that start in the SMB (small-to-medium business) part of the market. Over time, they seem to inevitably begin serving larger customers. Box, Hubspot, Zendesk and among many others have exhibited this pattern. Why does this happen?” …
This is my model for feedback: frequent, followed up with writing, augmented with coaching, and always honest:
And finally, this statement is just too true. It’s not just because I’m a reader and prefer a book or a written report over a movie or a webcast, but because if you’re busy you can read a book incrementally:
A group of crows is called a murder.
A group of developers is called a merge conflict.
Successful teams have members who communicated a lot, participated equally and possessed good emotion-reading skills:
Words about meetings:
It’s not enough to just do stuff, you have to make sure that people know you are doing stuff:
We went public:
Be careful what license you put on your work and then, when you do, don’t complain when others use it according to that license. Personally, I prefer CC-BY-NC-SA to avoid problems and here’s someone who agrees with me:
The role of a senior leader is to build a strong organization and a talented leadership team. That team then drives the results. It’s an indirect thing which makes it extra hard to do:
Part of building a strong leadership team is to adopt practices like Completed Staff Work:
It’s such a disappointment when one finds oneself in a political organization. Nobody ever starts a start-up saying “I’m going to build a miserable political culture” and yet every company ends up there:
Words on hiring:
Words about leadership and leaders:
Leadership is about others. That includes the boss. https://leadershipfreak.wordpress.com/2015/01/09/dont-poke-the-lion/
And many other nuggets of wisdom:
Here’s an example of why merely showing an average, or even an average and a variance, is insufficient in the real world:
“Immutable Servers are a deployment model that mandates that no application updates, security patches, or configuration changes happen on production systems.“:
This is one of the fundamentals of my management philosophy: the team is more powerful than the individual:
While this article is about nuclear war, the same belief-in-the-absence occurs in software systems all the time:
As an example of the above, here’s a great story about a seemingly improbable bug that surfaced in Facebook’s systems:
A good article about how rewarding the wrong thing leads to bad behavior:
If I have learned anything from the Internet, it is this: be very, very careful when you put a number next to someone’s name. Because people will do whatever it takes to make that number go up.
Of course this applies to everyone, not just executives:
And, as a fun end to the list, here’s an article that includes the architect who designed the New Relic Portland office. And an excellent job he did:
People do their best work in the face of constraints, but the kind of constraints make a big difference:
Amazon continues to amaze:
“Customers crave completion” so the goal should be to build a complete something, even if it’s very small:
So build something like this:
Here’s a third-party who writes a good introduction to New Relic’s most recent product; he “gets it”:
In a SaaS business, one sells not only a product but also the operation of that product, thus it is essential that one spends the time necessary to make the system robust:
Humorous, but maybe partly true as you would have built-in vendor-lock-in. Of course in most cases one has vendor lock-in even if there are multiple vendors because the cost to switch is just too high, so perhaps that’s not really an issue…
Made my day:
Some of the signs are obvious (#3,4,5,6), others less so (#1,2):
- You’re never quite satisfied with deliverables.
- You often feel frustrated because you would’ve gone about the task differently.
- You laser in on the details and take great pride and /or pain in making corrections.
- You constantly want to know where all your team members are and what they’re working on.
- You ask for frequent updates on where things stand.
- You prefer to be cc’d on emails.