Computer Science vs. Engineering: The Alien Tech Test
Description
A two-panel comic illustrating the difference between a Computer Scientist and a Computer Engineer. The top panel, labeled "COMPUTER SCIENTIST," shows a man looking worriedly at a strange, alien-looking computer. He says, "THIS ALIEN COMPUTER HAS AN ARCHITECTURE ENTIRELY FOREIGN TO OURS. WE HAVE MUCH TO LEARN FROM IT. AND WE MAY HAVE MUCH... TO FEAR." The bottom panel, labeled "COMPUTER ENGINEER," shows a younger engineer with a screwdriver popping up from behind the same machine, excitedly proclaiming, "BAM! I GOT 'DOOM' TO RUN ON THIS THING!" The first man looks on with a dismayed expression. This meme humorously contrasts the theoretical, cautious approach of computer science with the pragmatic, hands-on problem-solving of computer engineering, encapsulated by the classic "Can it run Doom?" benchmark for new hardware
Comments
7Comment deleted
A computer scientist sees a black box and asks 'What can we learn from it?'. An SRE sees the same box and asks 'Can I get root and does it have a stable API?'
Some study ISA whitepapers; others just cross-compile, disable the MMU, and call it a successful benchmark
The computer scientist spent three years writing a paper on the alien system's novel memory model while the engineer already has a Kubernetes cluster running on it and is debugging why the pods keep getting abducted
The eternal divide: Computer scientists see an unknown ISA and start drafting papers on computational theory and architectural paradigms. Engineers see the same thing and immediately check if it has enough registers to run a 1993 game engine. Both are valid approaches, but only one results in 'Doom' running on your smart toaster by Friday
Bring-up checklist: reset -> clocks -> DRAM -> UART -> framebuffer -> input -> Doom; once the WAD renders, the architecture review becomes a retro
CS diagrams the alien pipeline stalls; the engineer yanks JTAG pins until it fetches instructions
Unknown ISA bring-up checklist: clock, memory map, interrupts, serial - and whether Doom boots, because nothing validates your ABI like a WAD screaming at your framebuffer