rob pikeI saw the phrase "full stack engineer" cross my path recently. The first time I saw this, I wrote something on Google-internal Buzz. Read on.
"Much has faded now, but there was a time when I had at least a rudimentary working knowledge in gravitational physics, particle physics, nuclear physics, solid state physics, quantum electronics, electronics, quantum optics, LSI design, circuit design, chip layout, circuit board layout, system architecture, plus: machine code, assembler for various architectures, a wide variety of programming languages, device drivers, operating systems, 2-d graphics, ..." ...
"... 3-d graphics, libraries, regular expressions, parsing, compilers, application design, networking, and so on. Plus odds and ends like cosmology and physiology. It felt really good to know what the machine was actually doing, and surprisingly much of that came in handy from time to time, such as when I was working on Voyager.
Is that what they mean by full stack? If not, push back. Nowadays it seems some people graduating from university know Java and little else."
Is that what they mean by full stack? If not, push back. Nowadays it seems some people graduating from university know Java and little else."
Yes, it's snarky, rude even. But I do wish more software engineers had a broader grasp of what makes technology work. It makes one a better software engineer.
Daniel Darabos@robpike My dream is a book about the classic interview question, "what happens when you type a URL in the browser". From the switch in the keyboard to USB to CPU to kernel to IP, DNS, HTTP, and rendering HTML and rasterizing fonts. But the more I learn the more this sounds insurmountable.
Phillip Hallam-Baker@darabos @robpike I would take it a step further back and start with a page of HTML clicking on a link to info.cern.ch.
Typing in the URL was not supposed to be how the Web worked. NCSA introduced that and then Chrome turned it into the Omni box. If we had thought people were going to be typing in URLs, we would have fixed the :// thing.
Jeroen Ruigrok van der Werven@darabos @robpike There's a collaborative repository for that over at https://github.com/alex/what-happens-when
GitHub - alex/what-happens-when: An attempt to answer the age old interview question "What happens when you type google.com into your browser and press enter?"
An attempt to answer the age old interview question "What happens when you type google.com into your browser and press enter?" - alex/what-happens-when