Suggestions
Andrew Chen
a16z
Andrew Chen is the Principal Attorney at SoHo Law Group, where he focuses on providing legal services to both businesses and individuals. He has a background that includes working as an Associate at Weil, among other prestigious firms. His experience spans various areas of law, contributing to his expertise in the legal field.1
Chen is actively involved in the legal community and maintains a professional presence on platforms like LinkedIn, where he connects with other legal professionals and shares insights related to his work.2
Highlights
why are spreadsheets the GOAT of no code tools?
- unintimidating interface, just type numbers in a grid
- easy to make something useful
- shareable with a link
- copy and make your own
- insanely deep use cases (as a database, CRM, forecasting tools, etc)
- finance team loves it, and they approve the budgets lol
how many of these translate to agentic coding tools?
- it's chat, could the UI be simpler?
- you can build one-shot apps easily
- insanely deep
- share the output with a link
- finance loves it as it gives more leverage and will cut SaaS costs
There's more to do, but history rhymes. It has to be easier to share the code (not just the output), better management of forks, and more demonstration of operating leverage. But it's so powerful that it's inevitable agentic coding spreads as wall-to-wall as spreadsheets have
And as I argued before, agentically coded apps I think will ultimately subsume spreadsheets completely. Maybe some will still want a grid UI, but underneath will be agentically created code
prediction: we'll soon view coding the way we view using spreadsheets today - a commonplace skill that every white collar worker is expected to have. Knowing how to code will sit alongside email, making slides, word processing, etc etc. It'll be <18 months before this is widespread in every job description
Customer-facing employees will code as well as sell/market/support, so that they convert their domain expertise into repeatable workflows and software. We'll have an explosion of internal bespoke apps. But to complement all of this coding happening at the edges, we'll also have centrally expert teams of agentic coders who build infrastructure, make it secure/scalable, and create canonical software. These central teams will help scale agentic engineering.
There's a spreadsheet metaphor here too -- yes, if you are an expert at spreadsheets, you write macros, build huge models, etc., we'll put you in a group of your own. It's called Finance. :) We'll have the same central teams to help manage the widespread use of coding tools throughout the org.
You might ask, won't this be a mess? What happens in a world where everyone has many many variations of bespoke software? (It's already happening) Maybe! But I think it'll be fine, in the same way that it's fine to make a copy of a spreadsheet or deck. Making it easy to fork makes it easy to participate. But you might want an "official" forecast maintained by an official finance person, in the same way that there will be variations of canonical and bespoke software
excited for the Gdrive of many many forks of disposable apps made and shared by my co-workers!!! 😂
