13,028 karma · joined October 8, 2008
I've done so much startup stuff I'm equally bad at all of it.
I currently work coaching Founders globally from a base in Singapore: https://coaching.figuringshitout.com/
I formerly was a 3x Founder and have worked in Engineering, Design, Product & Growth.
I also have a background in Computer Vision (designed a single camera 3D tracking algorithm), Augmented Reality (Designed a AR prototype for FEMA to manage disaster response workers), Tabletop/Touch Computing (Studied how people's collaborative behaviors change when put under time pressure), HCI (Studied it for 4 years), Interaction Design (ditto) and am well read in Psychology (esp. Social Psych), Economics, & other random trivia.
I also cook... a lot.
The problem now is people use "agile" to mean anything from the 2001 agile manifesto meaning of the term to the 2024 F500 meaning and that's too long a span of time so the word has lost all communicative value. You can either engage in a fool's errand trying to drag the word back to the original meaning or accepting reality and letting people have it and come up with some new term like "katana development" or some bullshit that means essentially the same thing.
The "Observability" crew are good at this, I feel like every 10 years, there's a new coat of paint on essentially the same basic SRE concepts. Like how we went from Oriental to Asian American to AAPI, the mental burden of keeping up with these language changes serves as a basic shibboleth to who is paying attention enough to developments in the field.
<doing a poor job> --- <doing a average job> --- <doing a good job>
Whereas the more accurate mental model is:
<doing nothing> --------------------------------------- <doing a thing> -- <doing the best thing>
The former mental model is intellectually satisfying because you get to infinitely yak shave over every little tradeoff and doing nothing isn't even on your mental radar.
The latter is deeply humblingly mundane and doesn't get to center us as masters of the universe which is why we all initially resist it. Even for the people who become great at it, they become great against their inclinations, and still have to fight the urge at every step.
This doesn't just apply to tech, look at it in politics. How much time do we spend in politics debating policy? Which of our different political philosophies lead to different tradeoffs that are a deep expression of our values? How much time in politics do we spend debating state capacity? A state that can do none of the things, it's irrelevant which of the things we want the state to do. A state that can do more things, almost always just the sheer option of things they can do means they can find a better policy.
And yet policy arguments are just so fun while state capacity arguments are incredibly wonky and depressing.
But I've drawn that same diagram on 100 different whiteboards in front of 100 different juniors and said the same words of "before we figure out how to do the best thing, let's just see if we can even do a thing first" and it seems to have gotten through to an appreciable number of them enough that it feels like a high converting meme.
To be clear, the pathway to management noticing is not you going around the building loudly blaring that you did a thing, it's that churn went down, or ARPU went up or CAC went down or uptime went up or something management cares about.
But the essential thing to also understand is that this doesn't just happen for free. Figure out what metric your ship is meant to affect, put monitoring in place and proactively notify those above you about how your ship impacted that metric. If you don't do this last step, you didn't ship.
There's no way to engineer it such that you don't get to live in this reality. Be it tech companies, marketplaces, politics, revolutionary movements; once you reach a critical mass of people, all meaningful change looks like this.
Someone decided to call the Mac Mini a workstation... for what purpose? Did categorizing it as a workstation illuminate or confuse the larger point they were trying to make? If the former, then it's a workstation in that context and if the latter, it's not, again in that context.
Fundamental to my worldview is that we put things into boxes solely to aid in communication and the box is not important except insofar as it serves that functional purpose. But for others, the boxes themselves are deeply important and a huge amount of effort is spent cramming continuous functions into discrete containers for the sheer, seeing like a stateesque satisfaction of seeing the world organized. I'll never understand it.
As long as you keep changing, the quantity of books to read is infinite. I like the analogy of the article that books are like a stream and just dip in and pick the one of the moment and let the rest float by. It’s only people who don’t change enough who consume too much from the same point in the stream and feel the effects of water sickness.
You need trust in your team to make this work but you also need trust in your team to make any high velocity system work. Personally, I find the ideas here extremely compelling and optimizing for distraction minimization sounds like a really interesting framework to view engineering from.
> If you get interested in what you learn about the new technology, you may want to keep trying to understand it better; you may read more or embark on a personal project using it to gain more practical knowledge. As I said, it isn’t that you must stop coding. It is that, eventually, it shouldn’t be your day job anymore.
One thing that gets elided in a lot of "servant leadership" style chatter is, as a manager, you have permission to be straight up selfish. New leaders often struggle falling back into their old "inefficient" patterns of learning things but you have a team of resources at your disposal now.
You can just straight up ask a member of your team to prepare a bunch of background on the new technology and book a solid hour for them to personally tutor you through it. Sad to say but your time is more valuable than theirs and it does them no good for you to struggle at the other parts of your job because you're too modest to use your vested power. Often, teammates are actually happy to take the burden off your plate, if you poll ICs about gripes about their manager, one that comes up a lot is they wish they could get a few solid hours of the manager's time so they can educate them properly on a technology concept.
If you look at leaders as they move up the chain, one mark of who gets to the next level is who has learnt to be "selfish" enough to really leverage the resources under them. People are often under the misapprehension that these leaders are just sociopaths or heartless but if you actually ask them, it's not comfortable for them either and it's something they've had to learn but it's necessary mathematically to get any work done as your span of control increases.
If you want to repair phones to the equivalent quality of Apple stores, Apple makes it possible via their "overengineered" machines. There's nothing in Apple's ToS that forces you to make repairs this way, you're welcome to buy the Apple genuine part and use your own heat mats and press and whatever and knowingly make that tradeoff.
He's making low value content/the culture of the company is horrible/he's a fraud/it's more luck than skill. The actual critiques are personalized to the content and, to one extent or another, valid, but the social purpose of the critiques is universal which is that I felt uncomfortable that reading this might mean I have to re-evaluate my worldview and I'm going to dive into the comment section and upvote all the people telling me actually, I don't have to do that.
I actually spent over an hour writing 750+ words of my takeaways reading this document and shared it privately with a few founder friends of mine and I briefly considered also posting to share with the community but I took a look at the comments and took a look at what I wrote and decided I didn't have the energy to face the endless onslaught of nitpicks and misunderstandings that are driven, at the end of the day, not by a genuine intellectual desire to reach an understanding, but by the need to prove emotionally that others are not taking this seriously so I don't have to either.
All I can do is be vague and say I think this was an enormously valuable piece of writing that is worth engaging seriously for what it is as it might change your worldview in several important ways.
But also my larger meta-point is that there's a now near ubiquitous "sour grapes" attitude that's pervaded HN that makes it an extremely unpleasant place to hold a conversation and people reading should be aware of this systematic bias when reading comments here.
The range of practices I’ve seen go from just come up to the booth to get some trinket to put in your email address to get something a bit more valuable to listen to our 5m spiel and you can pull something out of a claw machine.
Is there a line there that you personally wouldn’t cross? A line that’s prohibited by your company policy? A line that you believe makes a company unethical and should be prohibited? Curious where everyone falls on this.
Of course, retro is usually the first thing to go in a deluded attempt to increase velocity and story points hang on as this vestigial tail, contributing to more cargo cult software engineering.
edit: One scenario that might play out:
The team all agreed that tasks A, B & C were worth 3, 5 & 1 points respectively but Steve and Mei thought task D was worth 5 points but Carol thought it should be 13 because it involved integration of an external API where her experience was that other API integrations in the past had exposed hidden complexity.
Task D ultimately was not completed because during the process of integration, it was discovered that the API did support a key feature that was needed and instead, an in house alternative needed to be built.
It was decided that going forward, the team would instead assign a 1 point task to building a toy app for any new API integrations that would then feed into the process of deciding the story points for features requiring that integration.
I was glued to the series as it plodded on week by week and it still sticks in my mind today as simultaneously the best and worst job in the world I could imagine. Part of what made it so enthralling to read was this grand act of human perversity that a single woman would endure such a gruelling quest for such a trivial question and she made you feel that perversity along every step of the journey.
[1] https://fivethirtyeight.com/features/americas-best-burrito/
At big companies, there's more of a formal process but the key is get the attention of the hiring manager and make sure that hiring manager has enough juice to quietly backchannel to whatever process to treat this as a default-yes conversation. A good sign of how effective your manager is at a Bigcorp is how well they know how to work their internal system to get the right people onto their team.