Tessera
Folgen

Adam Marcus

@marcua.net

Hummus, people, and data. Co-Founder & CTO of B12. Previously Locu, MIT CSAIL. He/him. https://marcua.net/ Queens is the future.

251 Posts2901 Follower236 Folgt
Adam Marcus@marcua.net · 2w ago

Any data engineers in my network or on #databs looking for a short-term contract setting up a Databricks-based ingestion/analysis pipeline? Would be for an academic lab studying the platform economy in collaboration w/ NYC gov. Happy to connect you!

Kurt Luther@kurtluther.bsky.social · 2mo ago

Abstracts due today for Papers and Talks at ACM Collective Intelligence and HCOMP 2026. Hope you'll submit!

ACM Collective Intelligence Conference@acmci.bsky.social · 2mo ago

🚨 Today is the abstract deadline for the 2026 Collective Intelligence Conference! 🚨 If you've been thinking about submitting, now is the time. ⏳ 📌Abstracts are due TODAY 📌Full papers are due June 8. Join us! ➡️https://ci.acm.org/2026/submit.html #CI2026 #HCOMP26 #CI26 #HCOMP2026

Phil Eaton@eatonphil.bsky.social · 3mo ago

Whatever your transactional database is, help me understand your use of it. This survey is run by @theconsensusdev, independent of any database or vendor. Repost or pass along to industry peers for broader representation forms.gle/fqjQsezWsztx...

Transactional Database Usage Survey

All questions relate to the primary database(s) you use to store transactional (e.g. typically user data, not event / activity data) data. This survey is run by The Consensus, independent of any data...

forms.gle

Adam Marcus@marcua.net · 3mo ago

A fine use of CLAUDE.md: a coworker instructed their agent to use Ska bands as example constants in tests. If you're wondering, the examples are geographically spread across the US (not internationally) and the later waves of Ska. They will be on `main` soon.

Olivier Grisel@ogrisel.bsky.social · 4mo ago

The team of JupyterCon 2023, PyData Paris 2024 & 2025 organizes a new conference named Compute! Paris 2026 on open source computation and data. The event will take place on November 25–26, 2026 at Sorbonne Université in Paris. CfP deadline: May 24, 2026: compute.events/paris2026/cf...

Call for Proposals — Compute! Paris 2026

Submit your talk proposal for Compute! Paris 2026. The Call for Proposals is open from April 15th to May 24th, 2026.

compute.events

Evan Peck@peck.phd · 5mo ago

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...

Pao Siangliulue@paopow.bsky.social · 5mo ago

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...

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...

forms.gle

Adam Marcus@marcua.net · 5mo ago

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.

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
Adam Marcus@marcua.net · 5mo ago

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...

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
Adam Marcus@marcua.net · 5mo ago

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...

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