Zaujímavé rozhovory na ktoré ste narazili

[wingo]

V minulosti som prečítal viacero zaujímavých rozhovorov, len často som sa k nim dostal náhodou a rád by som objavil aj nové ktoré mi určite unikli, a tiež postupom času na ne zabúdam kde som na ne narazil takže ich už neviem nájsť, preto ma napadlo založiť tému kde by sme ich mohli navzájom zdieľať a tiež prakticky aj archivovať.

Sem dávajte linky na zaujímavé rozhovory s ľuďmi hlavne z IT na ktoré ste narazili a ideálne aj nejaký popis/zaujímavú myšlienku z neho.

[wingo]

Rozhovor s legendárnym CPU dizajnérom Jimom Kellerom o celej jeho kariére:
https://archive.computerhistory.org/res ... 01-acc.pdf

So, the companies were big, but the teams were 100 people and so, there's a certain dynamic about how teams worked. For a while, I had a theory, and I had some data, which was like it takes 400 people four years to build a computer, and 300 people three years, and 200 people two years, and 100 people a year and a half. I wasn't sure a team bigger than 400 people could ever finish one. But then Itanium was 800 people and they finished the computer. So, I thought "Oh, that's weird." But it turns out, a certain group of people inside the team literally detached themselves from the management layer and built the computer. I talked to a whole bunch of people who worked on it, and they sort of finished the computer despite the fact the team was too big to actually build something.

Rozhovor so zástupcom Oxide ako na kompletku prekopali celú server infraštruktúru plnú historických prežitkov:
https://chipsandcheese.com/p/an-intervi ... n-cantrill

A big problem that we have with the BIOS, is that the BIOS has to boot the system in order to boot the system.
So one of the things the BIOS has to do... it needs to find like, how do I boot this thing? I need to actually do I/O, to pull a boot image off of somewhere. I/O, as we know, everything's complicated... you can't just like "do I/O", like, we actually have to bring up PCIE engines, you have to bring up all the CPUs... so you're doing all this work to boot the system, and then you find the image you want to boot, and now you have to be like, "okay, now we have to pretend like we were never here".
So it then tries to- we call it "setting the machine backward", where it makes the machine *look like* it has not been booted, when it executes that first operating system instruction. But in reality an *entire city* has been constructed, and ploughed under; and the operating system can actually see the artifacts of that over time.

[mp3turbo]

velmi ma zaujalo, dakujem ! taketo veci zo zivota si rad pozrem.