Remix.run Logo
▲ halfcat a day ago

> The numbers are shooting up and to the right but people don't want to get on board.

Revenue is one of those numbers, right? Right??

> It's too much too fast.

Yes, that’s exactly what being over-leveraged looks like.

“The number one indicator of fragility is leverage” -Nassim Taleb

We have one of you at my work. He’s a god, but for the wisdom.

▲the_sleaze_ 19 hours ago | parent [-]

Yes revenue is up 2x and might be 3 this coming week. Costs are down over 99% on certain tooling. Bugs are down 50%+ if not significantly more. Security is at an all time high. We are able to identify and patch holes in human logic in all aspects of the system, old and new.

I feel that there is an amount of hubris in saying "I understand this codebase". You may remember the highlights, but every company in the dozen I've worked for that was actually making money - the codebase was too large for anyone to know fully. A wizard with the wisdom as you so eloquently put me down with would leave. And guess what? Nothing would happen. It is only in your own mind that you are so important.

▲halfcat 16 hours ago | parent [-]

I agree, understanding the code does not save us. Knight Capital wrote every line of their code but it didn’t prevent a $440 million loss in under an hour [0].

Regarding wisdom, I do not mean knowledge of how the system works. That is a thing, too, where the person who built it is the only one who understands it. That’s not what I meant here.

In the examples of my coworkers, for example, I see at least two things:

1. The things they create are 90% well crafted, 30% well engineered. If they were building a rocket, every part would be well machined to high precision. Then when we assemble the rocket, we find out it’s too heavy to ever get off the ground. That’s a kind of wisdom gap.

2. They work in a way that excludes everyone else on the team. From their perspective, they are wondering why everyone else isn’t getting on board. But it’s a situation where one person understands it, and their deep understanding of it contributes to them moving fast, and then add AI and now the ground is shifting faster than anyone else can understand enough to contribute. This is another kind of wisdom gap, knowing how to get a team performing at a high level, versus an individual contributor performing at a high level.

This is where, from your perspective, you’re driving a speed boat as fast as you can, wondering why your coworkers aren’t on board. But from their perspective, they’re following your boat in their boats, but your boat is creating waves behind it and splashing water up, so their experience is a bumpy ride getting water splashed in their face constantly while they’re yelling “hey can you slow down up there?” From your perspective, it makes no sense to slow down. You’re not experiencing any problems. Yet both perspectives are still true.

The person who is charging forward as fast as possible also seems to be the one who has less experience operating and supporting systems, understanding how systems fail in unexpected ways, and so forth. Every week I have a conversation where someone tells me, “oh, I didn’t consider it might fail in that way”, and every time I think, yeah it would have been really nice if we’d had a 20 minute conversation 6 weeks ago when you started.

In general, it’s not that “other people just haven’t figured out the tools yet”, it’s also a significant part of who’s leading each initiative. I could absolutely do what my coworker does and setup my custom harness to pull off amazing stunts of productivity. I just think it’s irresponsible much of the time.

[0] https://en.wikipedia.org/wiki/Knight_Capital_Group