Advertisement · 728 × 90

Posts by Adam Marcus

It has an RSS feed! Yay!

3 days ago 3 0 0 0

Subscribing

4 days ago 1 0 0 0

“Why now?” is a great question! Maybe with overall review load increasing, people are looking for short-term efficiencies, or maybe it’s some comfort in agentic reviewers. I’d love to see studies of the tradeoffs regardless.

1 week ago 0 0 0 0

Aww thank you! I'm particularly curious about the interviewing and managing portion for "Review plans & code you didn't write." Models are getting better at working with loose task definitions, but speedrunning "the engineer is thinking more critically about AI-generated code" is a tough one

1 week ago 0 0 1 0
A timeline of the professional experiences a junior engineer used to develop over several years. Skills that used to take years to hone are now required in your first moments with a coding agent.

A timeline of the professional experiences a junior engineer used to develop over several years. Skills that used to take years to hone are now required in your first moments with a coding agent.

Late last year, I gave a talk at Northeastern to students in a few software engineering classes about what's changing and what's staying the same for junior engineers in industry with the introduction of coding agents. Slides and notes here: blog.marcua.net/2026/04/08/a....

1 week ago 2 0 1 0

It took me way too long to understand what was going on there.

3 weeks ago 1 0 0 0
Video

I made a tiny tool for quickly sharing small datasets (< ~1000 rows) without uploading any data to a server.

🔗 ziptbl.com

It compresses the data into the link itself, so there’s no account, hosting, or storage layer involved.

Here's Florence Nightingale's famous 📊 data:
ziptbl.com#d=eNpdlE-LGz...

4 weeks ago 304 95 14 12

Have a slice of Tercel

4 weeks ago 0 1 0 0
Preview
Project Document Study Interest Form Hi! 👋 We are researchers at the Allen Institute for Artificial Intelligence (Ai2) exploring AI-powered tools to support researchers as they work on their research projects. We are looking for partici...

Are you a researcher in CS or a CS-adjacent field curious about how an AI agent can help you with your research project? Want to try a new tool for your research support in a paid user study ($100, 2 hr)? Limited spot numbers. See details and sign up here: forms.gle/JzLtkAhe7Ttv...

1 month ago 1 1 0 0
Advertisement
Vampire Weekend - Oxford Comma
Vampire Weekend - Oxford Comma YouTube video by Scott Parsons

Not an endorsement of its death, but this feels obligatory www.youtube.com/watch?v=_9os...

1 month ago 0 0 0 0
Preview
B12 3.0 A decade of helping customers build their home online

I've never built anything for a decade professionally, but here we are! blog.marcua.net/2026/03/12/b...

1 month ago 2 2 0 0

Clawrd

1 month ago 1 0 0 0

"...managers who treat AI as a productivity multiplier for their junior engineers are optimizing for output. The managers who use AI to push their juniors into harder problems are optimizing for growth. These look similar on a quarterly roadmap. They produce very different engineers over two years."

1 month ago 1 0 0 0

I want to talk about why AI-based mass surveillance is so dangerous, and why I would oppose it no matter which party or president is in office.

1 month ago 49 10 3 0
Preview
AI And The Ship of Theseus Slopforks: what happens when a library gets rewritten with AI?

chardet was vipeforked to MIT and I have thoughts about it. Spoiler: I like it. lucumr.pocoo.org/2026/3/5/the...

1 month ago 58 15 10 5
A photo outside a black building labeled "The Punk Rock Museum" in neon green, with a hat that says "SKA" at the bottom of the photo

A photo outside a black building labeled "The Punk Rock Museum" in neon green, with a hat that says "SKA" at the bottom of the photo

If you find yourself in Las Vegas, The Punk Rock Museum is a pretty good place to go!

It's like 50% nostalgia for whatever 1-2 decades of punk you liked, 50% stuff Fat Mike / NOFX liked or collected.

1 month ago 1 0 0 0
Advertisement
A snippet from the introduction to the blog post:


Four questions agents can't answer

Software engineering after agents write the code

Feb 25, 2026

You’ve likely read countless words about how coding agents have massively changed software engineering. At the extreme, December 2025 was the turning point and we’re unlikely to write a line of code again. But amidst all this talk of change, it helps to understand what likely won’t.

I’m particularly interested in the questions agents can’t answer, doubly so if they are unlikely to answer them well in the coming years. Here are four such questions that blur the line between product management and software engineering. The questions reflect the fact that as coding agents cover more of the nitty-gritty of code generation, humans will be responsible for higher-level concerns. I think these questions will remain in the human domain for years to come:

    What should we work on?
    How much of it are we doing?
    How do we do it well?
    What’s getting in our way?

These questions are durable: we’ve encountered them since software engineering became a profession, and we’ll be responsible for them as long as we’re responsible for the products and systems we share with the world. The answers to these questions require judgment based on goals and constraints that are organization-specific, dynamic, and don’t live in some task management or issue tracking system you can integrate with. It’s hard to imagine an agent successfully synthesizing these disparate and context-specific inputs into answers.

What should we work on?

Companies tend to work at the intersection of what their users find valuable, what the business finds

A snippet from the introduction to the blog post: Four questions agents can't answer Software engineering after agents write the code Feb 25, 2026 You’ve likely read countless words about how coding agents have massively changed software engineering. At the extreme, December 2025 was the turning point and we’re unlikely to write a line of code again. But amidst all this talk of change, it helps to understand what likely won’t. I’m particularly interested in the questions agents can’t answer, doubly so if they are unlikely to answer them well in the coming years. Here are four such questions that blur the line between product management and software engineering. The questions reflect the fact that as coding agents cover more of the nitty-gritty of code generation, humans will be responsible for higher-level concerns. I think these questions will remain in the human domain for years to come: What should we work on? How much of it are we doing? How do we do it well? What’s getting in our way? These questions are durable: we’ve encountered them since software engineering became a profession, and we’ll be responsible for them as long as we’re responsible for the products and systems we share with the world. The answers to these questions require judgment based on goals and constraints that are organization-specific, dynamic, and don’t live in some task management or issue tracking system you can integrate with. It’s hard to imagine an agent successfully synthesizing these disparate and context-specific inputs into answers. What should we work on? Companies tend to work at the intersection of what their users find valuable, what the business finds

Just posted "Four questions agents can't answer: Software engineering after agents write the code"

We're dedicating a lot of brain space to what coding agents can do, but it's equally important to consider what they won't accomplish for years to come.

blog.marcua.net/2026/02/25/f...

1 month ago 2 1 0 0

Only a few more days (full consideration deadline: March 1) to apply to our lecturer position at @cornelltech.bsky.social!

1 month ago 1 2 0 0
Preview
‘The bathrooms were rank, but we didn’t care’: how the grimy-but-great CBGB changed rock for ever Half a century ago, the famed New York venue run by a former marine and folk singer was ground zero for the punk and new wave scenes. Now the bands who played there are being celebrated on a 101-track...

CBGB&OMFUG. Iconic and mourned.

www.theguardian.com/music/2026/f...

1 month ago 19 4 2 0
A snippet from the introduction to the blog post:


Four questions agents can't answer

Software engineering after agents write the code

Feb 25, 2026

You’ve likely read countless words about how coding agents have massively changed software engineering. At the extreme, December 2025 was the turning point and we’re unlikely to write a line of code again. But amidst all this talk of change, it helps to understand what likely won’t.

I’m particularly interested in the questions agents can’t answer, doubly so if they are unlikely to answer them well in the coming years. Here are four such questions that blur the line between product management and software engineering. The questions reflect the fact that as coding agents cover more of the nitty-gritty of code generation, humans will be responsible for higher-level concerns. I think these questions will remain in the human domain for years to come:

    What should we work on?
    How much of it are we doing?
    How do we do it well?
    What’s getting in our way?

These questions are durable: we’ve encountered them since software engineering became a profession, and we’ll be responsible for them as long as we’re responsible for the products and systems we share with the world. The answers to these questions require judgment based on goals and constraints that are organization-specific, dynamic, and don’t live in some task management or issue tracking system you can integrate with. It’s hard to imagine an agent successfully synthesizing these disparate and context-specific inputs into answers.

What should we work on?

Companies tend to work at the intersection of what their users find valuable, what the business finds

A snippet from the introduction to the blog post: Four questions agents can't answer Software engineering after agents write the code Feb 25, 2026 You’ve likely read countless words about how coding agents have massively changed software engineering. At the extreme, December 2025 was the turning point and we’re unlikely to write a line of code again. But amidst all this talk of change, it helps to understand what likely won’t. I’m particularly interested in the questions agents can’t answer, doubly so if they are unlikely to answer them well in the coming years. Here are four such questions that blur the line between product management and software engineering. The questions reflect the fact that as coding agents cover more of the nitty-gritty of code generation, humans will be responsible for higher-level concerns. I think these questions will remain in the human domain for years to come: What should we work on? How much of it are we doing? How do we do it well? What’s getting in our way? These questions are durable: we’ve encountered them since software engineering became a profession, and we’ll be responsible for them as long as we’re responsible for the products and systems we share with the world. The answers to these questions require judgment based on goals and constraints that are organization-specific, dynamic, and don’t live in some task management or issue tracking system you can integrate with. It’s hard to imagine an agent successfully synthesizing these disparate and context-specific inputs into answers. What should we work on? Companies tend to work at the intersection of what their users find valuable, what the business finds

Just posted "Four questions agents can't answer: Software engineering after agents write the code"

We're dedicating a lot of brain space to what coding agents can do, but it's equally important to consider what they won't accomplish for years to come.

blog.marcua.net/2026/02/25/f...

1 month ago 2 1 0 0
End of Productivity Theater I remember the early 2010s as the golden age of productivity hacking. Lifehacker, 37signals, and their ilk were everywhere, and it felt like...

[new blog post]

End of Productivity Theater

muratbuffalo.blogspot.com/2026/02/end-...

1 month ago 4 1 0 0

Move fast and break things?:)

1 month ago 1 0 0 0
Preview
Rust Engineer DuckDB Labs provides services around the DuckDB in-process OLAP data management system directly from its main developers.

🦆 ↔️ 🦀 DuckDB Labs is looking for a Rust engineer to join our team in Amsterdam.

📝 See the details and application page at duckdblabs.com/jobs/rust_en...

1 month ago 23 9 1 1
Advertisement
Preview
GitHub - tobilg/polyglot: Rust/Wasm-powered SQL transpiler Rust/Wasm-powered SQL transpiler. Contribute to tobilg/polyglot development by creating an account on GitHub.

Introducing polyglot - A Rust/Wasm SQL transpiler for more than 30 SQL dialects.

It has 100% coverage for sqlglot‘s test fixtures.

github.com/tobilg/polyg...

2 months ago 14 4 2 0

1/ ProPublica collected handwritten letters in mid-January from children held at the Dilley Immigration Processing Center, the same facility where 5-year-old Liam Conejo Ramos was taken.

Hundreds of kids are still detained.

We’ll let the children’s words speak for themselves. 🧵

2 months ago 11591 7426 204 829

I'm scheduling speakers for NYC Systems 2026. Please DM or email me if you've got a staff/principal engineer or phd student who can come tell us something interesting about compiler / database / systems / infrastructure work!

Schedule is on the site. nycsystems.xyz

2 months ago 5 3 2 0

So much great advice in this thread!

2 months ago 17 3 0 0

Oh this is so much better than what was in my head.

2 months ago 0 0 0 0

It's hard for me to read this and think about anything other than "AND YOU KEEP PULLING ME DOWN!" though I'm not sure if that was the desired effect.

2 months ago 0 0 1 0

I am recruiting a postdoc in HCI & AI!


Interested in augmenting human thinking and learning, futures of work & education, participatory AI, collective intelligence, or related topics? Please get in touch! This 2-year position will be based at a top university in Europe (email or DM for more info)

2 months ago 14 9 1 0