Live data from Hacker News

My biggest mistake as an F1 engineer

linkedin.com

1–10 of 70 posts

Re: My biggest mistake as an F1 engineer

#4
post #2

Linkedin demanded me to log in to read.. I'd be happy to read this w/o logging in / registering. Are you aware of a non-Linkedin link?

I read it on android via Materialistic just fine. I don't even have a LI account

Iinteresting.. Lynx/Curl gave me the page straight away, Chrome though keeps redirecting me to the "register or login" page.

edit --

It's some Javascript based redirect, I can see this in curl: ... "baseRedirect":"" rel="nofollow">https://www.linkedin.com/uas/login?session_redirect="}--> ...

I'm not investigating further.

Re: My biggest mistake as an F1 engineer

#9
Short version: He didn't fuel Raikkonen's car up enough which forced an early pit stop in the second-to-last lap of the race. However at the end of the race they placed the same as they had planned, and they had for the laps before the pit stop the advantage of having a stress-free race due to being in pole position.

And the lesson he learned from that: Don't stick to the rules too closely, but also try to see if breaking some rules can have positive side effects. Experiment.

Not a fun read. Very badly written as he constantly leaves out the consequences and details of decisions and circumstances, or only mentions them paragraphs later.

Re: My biggest mistake as an F1 engineer

#10
I'd be interested if anyone has any anecdotes that compare from software engineering. Sending a car out with suspension thingamies still attached seems like the equivalent of pushing a build to production with `DEBUG = True`, and I'm not sure much useful can be learned by you in that situation.
Post reply on HN