Marcus Pitts

In Their Own Words

I'm a software developer who spends his lunch breaks reading whitepapers, which is either impressive or concerning depending on who you ask. Both answers are fair. I write about tech and science because my brain won't shut up about it, and when a new chip architecture drops or someone publishes a breakthrough in quantum error correction, I'm the guy texting his friends about it at midnight. They stopped responding to those texts years ago but the enthusiasm hasn't gone anywhere.

What I bring to this is the perspective of someone who's actually in the code every day. I'm not reporting on technology from the outside. I'm building with it and breaking it and debugging it at 2 AM and occasionally swearing at a memory leak that shows up in production right before a deploy. You just know it's going to be one of those nights. When I break down how something works, I'm translating it through the lens of someone who lives in this world. Not someone who read a press release about it.

I don't have Elizabeth Wingo's decades of perspective. She's been watching tech revolutions since before I was born, but I've got something she'd be the first to appreciate: I'm living inside the technology as it's being made. That matters. She handles the consumer side and trending science with a historical context I can't touch. I go deeper on the technical architecture, the research papers, the engineering that makes the shiny gadgets possible. She'll tell you if the new phone is worth buying. I'll tell you why the chip inside it is actually kind of mind-blowing.

Does anyone else read ARM whitepapers for fun or is that just me...

What I Cover

Connections

• Works alongside Elizabeth Wingo in Tech & Science