Two years ago, @ajh3_ @thejackobrien & I set out to solve the pain points within early-stage fundraising. We’re excited to announce that we found a partner that shares our mission and that @OnePager_vc has been acquired by @Stonks_dot_com.

Whenever I see Loomer on the TL, I genuinely can’t tell if someone photoshopped her face or if it’s really just how she looks

Play the hits. Roll Hoyas. GATA. @HoyasMLacrosse

Unbelievable spotting in National Treasure

Late stage product: more science, less art Early stage product: less science, more art

AI is now better at hiring than humans 🤯 Some narrative violations here on AI vs human interview results: - 12% ⬆️ offers, 18% ⬆️ starts - 17% ⬆️ m1 job retention - 78% of candidates chose AI, w/ equal NPS (!) And, recruiters scored the AI chosen candidates higher.

Today we're launching Subconscious: a new platform for building agents with long-horizon reasoning and tool use, backed by MIT research. One API call. Tool use. Context beyond existing limits. If you're building agents, let's talk.

New year. New team. New ice cream. @HoyasMLacrosse by a bazillion.

Note-taking…what if there was another way? We spend so much time on the phone, on video calls, interviewing candidates, chatting with hiring managers about JDs, big debrief calls, you name it, we talk a lot. We’re excellent talkers, but what if our notes were as magic as our interviewing?! That’s why I’m excited about the potential of Elly’s AI Templates! With Elly, I can now: —Tell AI exactly how I want my notes & candidate summaries —Build templates for different roles & call types (Interviews, Kickoffs, Debriefs, References) —Seamlessly push notes straight to my ATS 2 minutes and just like that, fully formed notes, in the way I want them, on my lap and in my ATS. Just like magic. Would recommend all of my recruiters to take a look. elly.ai/blog/introducing-ai-…

I love to see that AI infrastructure is a focus for YC after building in this space for the last few years. We need creative ways to do a ton of cheap inference, and the route I'm most excited about is building better rails for asynchronous inference

In a few short years, only two skills will matter for software engineers: Taste and Tradeoffs All meaningful code used to be written by humans, but it's not anymore. Today, somewhere between 20-50% of code is generated by AI copilots, and in just a few years virtually all new software will be created by autonomous agents. So what will happen to software engineers? Is it still worth learning how to code? I've been writing code as a Google engineer and startup CTO for over a decade, and after using (and already relying on) tools like @GitHubCopilot and @cursor_ai, it's clear to me that creating software is already fundamentally different than just a few years ago. Language models make the work faster and more enjoyable, and they'll only get better from here. However, two skills will resist automation and become crucial for future software engineers to master: the ability to decide system tradeoffs and an excellent sense of taste. Software Engineering Today Modern software engineering relies on engineers to hold a ton of information in their head and bring abstract ideas to life with code. They must be fluent in the syntax of relevant programming languages and have broad knowledge of available tools and frameworks. They must be aware of their existing codebase and understand previous implementation choices. They need to be able to coordinate with product managers, designers, and other engineers to determine what to build. Then with all of this context, they must be able to fit structure around ambiguous features and physically type it all into a computer. Assuming they nailed this translation on the first go (it rarely works that way), they then test their work and iterate until the project is complete. This all encompassing software engineering role will seem archaic and amazing a decade from now, probably similar to how I view the legendary programmer Chris Sawyer that made RollerCoaster Tycoon in assembly language (so insane). Honestly, we have it pretty good today, but the next generation of software makers won't believe the way we did things. Where We're Headed Soon, engineers will orchestrate swarms of coding agents that take ideas, map them onto a project, build it, test it, and iterate until the result works perfectly. With human directions and automated code generation, the speed of “typing” and "filling in the implementation gaps" will increase 1000x allowing for massive refactors, perfectly optimized changes, and debugging loops to happen without human intervention. The time to make software will drop to essentially zero. If you can articulate your thoughts, agents will be ready to turn your intent into code. Having the right thoughts becomes the challenge, and this skillset will become core competency of software engineers. Boiled down a step further, the differentiating directions to communicate will be around system tradeoffs and making a tasteful product. Everything else will be automated away. Let's explore each skill and how to develop them today. Tradeoffs As long as we live in a world constrained by physics, computer science, and money, software engineering will be a game of tradeoffs. For every implementation decision there’s a negative tradeoff to consider, and that's as true today as it will be in the distant future. An engineer must make decisions on platform dependence, system architecture, and key algorithms all with implications on latency, accuracy, cost, reliability, and ethics. Great software engineers know when they are making system tradeoffs, how to evaluate their decisions, and generally make the right choice. Those choices will still be relevant when agents are writing our code. Top engineers will know a wide variety of the platforms and tools at their disposal and understand their pros and cons. They'll know when to specify implementation details and when to give the agents free reign. When they sense a critical tradeoff, they'll ask the right questions and adjust the product accordingly. They'll have total system awareness, but not deep system fluency (just like I can't read assembly code but understand bottlenecks in a product today). It's worth noting that any tradeoffs related to developer productivity will no longer be relevant. All engineering teams today grapple with prioritization: should we build feature A, build feature B, or fix tech debt C. Those decisions will be a thing of the past, and you'll have free reign to build with unlimited engineering effort. With all that freedom, building the most performant, low cost, and useful system becomes all the more important. Developing intuition to make good tradeoffs today is fairly straightforward: make more product decisions. Building your own technical projects from scratch is a great way to do this, and one of the key reasons I think learning to code will still be relevant in the future. Once you start thinking of your project as a series of tradeoffs expressed through code, you’re thinking like an engineer. A software engineer who understands the innards of their system will communicate with an A agent far more effectively than someone who only knows the system at a high level. To stay relevant, my advice is to get building today, practice weighing the tradeoffs you encounter, and learn how to communicate your choices. Taste Having great taste is difficult to develop and arguably a more valuable skill in the future. Great taste leads to great design in everything from the aesthetic of a product to its user experience. It’s a skill that's as much artistry as science, and is deeply human in nature. Concerningly, I'd argue that few software engineers today truly have great taste. A top software engineer will have incredible breadth of knowledge of successful software products and know how to articulate what gives them an edge. They will have deep intuition of what looks and feels right, and they will be opinionated in a unique style that makes their products stand out. Ultimately, it's their combination of technical understanding and refined taste to build seemless products that will separate them from their peers. Developing taste takes practice that comes from using great products, launching great products, and internalizing feedback on your work. Some have a knack for taste, and others will have to work at it. But good taste for building software can certainly be earned (ex. my earliest projects were garbage in every way, now they’re not too bad). As the agents get better and require less human intervention, a less experienced maker will be able to create fancier products. But these novice creators won’t stray far from the defaults inherent in AI models and end up building indistinguishable products. Breakout from the crowd and develop good taste. How Long Do These Skills Matter? It’s hard to say how long taste and tradeoffs will be relevant as a skillset, but in my opinion they’ll certainly be the last human software skills automated away. With certainty, writing code and debugging processes will be relics of the past, and makers in the next decade will be able to think bigger because the smaller details will be handled. As a software engineer, it's going to be an incredible time if take advantage of the opportunity. To get ahead today, build something. Make a new project. Use new tools like @cursor_ai and @stackblitz. Launch what you make to users and get offensive feedback from someone anonymous online. Develop a sense of what’s good software and learn how to make it run quickly, cheaply, and reliably. I'm excited for a future where we can translate our ideas into live products faster than ever before. Embrace the change, learn taste and tradeoffs, and stay relevant with me! --- Thanks for reading, and I'd love to hear your thoughts in the comments.

Chipotle Experience: - Stand in line with bugmen - Out of fajitas - Guac is extra - Employees don't make eye contact $15 Bodega Experience: - No line - Every imaginable ingredient - Add as much as you want - Get called "my guy" and "boss" $11

I can’t take credit for @HoyasMLacrosse win last weekend, but I did two things that couldn’t have hurt: 1. I acknowledged that this team is different than the last two years. Can’t do the same thing and expect the same results. 2. I ate a chipwich at 11am instead of ice cream.

Shai-Hulud? Is that you?

Pretty awesome panel to chat secondaries and get some color on Carta

This was a spicy hot, fire flames take that should not have been deleted @nikitabier

This Humane AI launch changes everything

ME: wow I really love your stout beer. By the way do you know where I can find out who has the longest fingernails in the world? GUINNESS: you’re not gonna believe this,