Adam Jacob Profile picture
3 Dec, 25 tweets, 9 min read
@webframp Ok! Basics first. F1 is a constructors sport. Each team must build its own car, from scratch. They can use listed parts, outsource some, but the design and build has to be done in house by the team.
@webframp That means the team often can build the car around the driver. They give feedback on how it feels and behaves, and the teams change and adapt over time. It also means each teams car is unique to the team.
@webframp The cars themselves have no driver aides allowed. No power steering. No traction control. If you’ve ever driven a rear wheel drive sports car with no assists, I’ll tell you: it’s difficult. You have to pay maximum attention all the time. They’re absolute monster cars.
@webframp So each team builds two, according to the regulations. They then out two drivers inside them. So that’s the first bit of sport - every driver on the grid has another driver, in an identical machine, that they need to race every weekend. Between each other, it’s a pure driver race
@webframp The margin between the best car on the grid (Mercedes) and the worst (Williams) is measured in tenths of a second. Built by hand. The margins are razor thin. It’s supremely difficult technically. Layer in reliability, and there’s tons of angles just in the cars themselves.
@webframp That brings us to the first championship, the constructors. Each race awards points, which translate to💰. Tally up the points for your two cars, and that’s what your team gets for the race. Winning means you (maybe) built the best car. It’s a real achievement.
@webframp But the real drama in the constructors is the middle of the grid. It’s brutally hard to get better. Every step forward risks going backwards. Every track is unique. Every driver is different. Teams also race for prestige. Mercedes over Ferrari!
@webframp This year, the drama is Ferrari dropping way down the order. They cheated fuel flow last year. McLaren, Racing Point and Renault are neck and neck for third place. Every second means millions of dollars. It’s compressed business competition as sporting angle.
@webframp Hundreds of people working in the factory, in design, mechanics, strategy, simulation. All pointed at winning that prize money.
@webframp Each of those teams has a “principal”, who runs the team. They’re personalities in their own right, who are part of the drama of it. It’s great.
@webframp The other aspect is, of course the drivers. These are the best of the best of the best. Most trained from karts starting at 8 years old. The cars put incredible stress on your body. They’re in elite shape.
@webframp The level of control required to plant a car through one lap without crashing is insane. Remember, no driver aides allowed. Small variations of throttle, breaking, grip, timing, feel. Every tenth of a second is worth millions of dollars.
@webframp Your entire team put every minute of their work life into you getting it right, every time, in the most difficult situation. Hesitate and you’re done. Over do it and you’re cooked. Getting is right is a zen mastery lesson at 200mph.
@webframp And every time, you’re measured against another person, in identical machinery. And every once in a while, a driver can take a car and get more out of it than they should. George Russell has done this the last two years. Max Verstappen. Fernando Alonso. Lewis Hamilton.
@webframp Only 20 seats available. Every young driver on the planet wants one. To keep it you have to perform, every time. And nobody can. Cars break. Drivers make mistakes. Each one is heartbreaking - opportunity, cost, revenue. All on them. Huge pressure.
@webframp Lewis Hamilton is probably the GOAT because he finds that place more than anyone. He drove a pair of wet tires into slicks a few weeks back. It was a master class. But the drama of it is, again, in the middle. Who can rise up? Who can meet the challenge?
@webframp And every race is a reset. Every Sunday is another shot. When the lights go out, it’s just them, the work of hundreds of people, and the fastest cars on the planet. Racing for money. For a career. For their livelihoods. It’s peak drama.
@webframp To really see it, you have to watch a full season. Ideally with practice and commentary too. Which is a big investment (at least four hours+ of content on a race weekend). Or read the F1 news. Jump start with the Netflix show Drive to Survive.
@webframp That drama unfolds in real time. You watch those stories all year long. It’s fucking great, man. :)
@webframp Oh! So the drivers also have a championship. With prize money! If you’re in a great car, you’re expected to perform. If you don’t, you loose your shot.
@webframp The team, the cars, the drivers. The circuits. Throw in weather, incredible risks, and huge personalities - it’s truly an amazing thing. That it exists is insane.
@webframp Imagine watching VC backed startups try and perform every weekend, with their revenue on the line. That’s what F1 is. Elite athletes backed by elite technical talent vying for a fixed pool of prize money.
@webframp More on drivers. No assists at all. So you’re driving at 200mph, and to get the best exit you change the brake bias, gear ratio, and engine timing. In a tenth or two, while doing multiple G. Every time. For an hour. Never getting it wrong. It’s bonkers to watch.
@webframp It looks smooth and placid on tv - it is anything but in real life. Loud, hot, demanding, hair trigger decisions. Perfect focus. Perfect training. Perfect teamwork. That’s what it takes. Every weekend. For years.
@webframp Then they wreck the car! And the best mechanics on the planet put it back together in 10 minutes. Or they do a pit stop in under two seconds. It’s precision teamwork.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Adam Jacob

Adam Jacob Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @adamhjk

2 Dec
There is a market opportunity for an alternative to k8s. You won’t “beat” it, but you don’t have to. You just have to decide to compete. Right now nobody even tries. Nomad is closest, and even their marketing is complimentary at heart.
To be clear - I’m not building one
Also, it’s not because k8s is bad. It’s because it’s such a success, the groundwork for the market is laid. People don’t question its place in the stack. They do question the implementation complexity. Operability.
Read 5 tweets
9 Sep
I haven't used Fluid, but I just devoured all the info on it, and I want to share why I think it should be a game changer for most of us.
First - doing large scale collaborative state transitions is really hard if you want it to feel fast. The number of different factors at play range from the low-level wire protocol to the high level application design. It all has to be right, or you get very hard bugs.
Until now, I suspect most everyone wound up taking either the Operational Transform route or the CRDT route. What Microsoft did here was cleverly different (unique? certainly to me, and I've done a lot of reading and implementing here)
Read 9 tweets
7 May
For people wondering if switching to the red hat model has worked for chef - super yes. It’s for others to give details, but I wouldn’t do the open core model again, if I wasn’t building on an existing free software island.
Selling the whole product, and having the whole product be open source, and having third party produced builds, collaborating together, it’s better on, I suspect, every angle.
It’s less clear you could begin this way, but I think you could. If we had, it would’ve been less of a shock to parts of the chef community. Not hearing a single conversation about lack of differentiation is like being in a hot tub, if you lived 13 years of it.
Read 7 tweets
28 Mar
Let's talk about this whole "k8s yaml is assembly" thing. When this gets said, it's often in a protective way. "The reason its so verbose is that it is assembly", or "The reason isn't dynamic is that is assembly". This is.. a bullshit excuse. It's not assembly at all.
What it is, is raw API calls. Without any of the kind of user tooling that might make it okay to make raw API calls. I know the story is, we're supposed to make those tools. But that's an enormous cop-out. A quick survey of the landscape shows that we're already @ ~6.
That's viable paths. None of which you could use effectively if you wanted to remain within the ecosystem broadly - each one will conflict with the others, do things slightly differently, and ultimately all of that will wind up straight on the user.
Read 19 tweets
18 Dec 19
Rust friends. Lets talk about async-std and tokio. There is a (relatively) polite cold war happening, and I'm pretty sure it's bad for all of us. Tokio paved a ridiculous amount of ground in the rust/async ecosystem, and it's been on a steady climb of improvement.
Much of that has been driven by real-world usage, building high performance networking code. That means it exposes all the knobs and fiddly bits you need when you care about the details. It also means that, when you first start, the experience is sometimes overwhelming.
It is, however, pretty damn solid. It's also quite quick, and pays a lot of attention to the details of what happens when you're in production (things like tail latency, which matters a lot when your request gets the shitty tail, and not so much when it doesn't.)
Read 9 tweets
30 Jan 19
I am not deep in k8s land. But I do have a drive by observation: the API being coupled to kubectl, and the behavior of a workflow being tightly coupled, is a mistake we made early at Chef with Knife.
We started out being very explicit about workflow. What happened next is predictable: it was the wrong workflow for some folks. So we made it pluggable (good!), but then it was harder to maintain and less portable (need this plugin for our workflow, sorry!)
The core set of behaviors need to be reliable and declarative, and accessible reliably from the API. If you’re going to include workflow in that, the above still applies. It’s either in or out.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!