100x-engineering

You can't get there from here

So audacious it allows you to detach from what you know to be true... it frees your mind

Empirically... where do we actually spend our time?

Why aren't we already 100 X engineer?

What does that even mean? We are on a team, so really it is how could we make the output of a team won hundred times faster

Remove all micro blockers aggregation of marginal gains

If we scaled our data down by 10,000 times, we could have end to end in minutes and see the impact. With that we would want to be able to see a clear picture of the before and after impact on the system for changes that we are making. This would give us confidence to roll out very quickly. Also, if we knew we could get back to the previous state we would feel confident in the role out And our ability to recover

That quote from the big data book where he was able to do stuff that the others were surprised by

Decentralized processing. People should be able to work off of their laptops

Should think of system performance first. It will be the bottleneck

Human fall tolerant systems. A good example of this is snowflake and their ability to time travel

Illuminate ambiguity. Clear registry of what things do, and how they do them. If you provide data make the interface is very explicit. Try not to name things generically so they will be hard to find.

Improve tooling mercilessly. If you cannot get everyone to standardize on a single editor, then use things like language servers

Not everyone wants to be 100 X more productive. If they did, they would sweat all the details. There would be a code formatter

To be 100 decks more productive we would need to get people up to speed 100 times faster. We would need to leverage the very best educational materials, space repetition, and a self documenting and self describing system.

We would need to cut down on communication overhead

We would need to mercilessly reflector so overly complicated ideas, a.k.a. Tech debt, would not take hold. We would need to write code for deletion and with three factoring in mind.

But execution speed isn't top priority, necessarily. We need to be aligned on what we are executing on. We need to build a system that is low maintenance, resilient, and that we all understand collectively because people come and go, and even yourselfSix months from now is not the same as you now.

Blocks of time, focus on special projects with a complexity hump that arrives at greater simplicity

Or vacations, or babies, or medical problems

testing built-in?

⤢

In the first 10 minutes Steve Jobs talks about Next's ability to create operational tooling 5 to 6 times faster than anyone else. He sees this as a distinct advantage, and showed that companies that focus their IT budget on operational tooling were far more successful than others. ^{^operational-tooling-speed}

It's so unbelievable that you have to suspend disbelief do you have to disengage your skepticism

A set of admin tools that acts like an even faster version of Blazer (dashboard forking... ability to define static, persistent, datasets... help with linking things together (my historical blazers start to work like GPT... giving me big hunks of pre-existing SQL that helps pull lots of stuff together.