Dan
7.1K posts





One question I've been asking founders is: do you try to review all the code that the LLMs write or do you just accept it? I think it's about 50-50 right now but the momentum is towards just accepting the AI-generated code and I think that number will eventually go to 100% This is one of the most telling indications of how AI-native a team is. It's hard to get super high throughput if you are reviewing every line Poll: what do you do?


This is so stupid I shouldn’t even be tweeting it. In my role I context switch so many times during the week that a simple task can take days to weeks to get done. It also means I need to ramp back up on what I’ve done so far all over again. To combat this I start a doc and I document what I’ve done so far in realtime. Example: I went to the UI and here’s a screenshot of what options I picked, here’s a link to the feature flag I changed, here are the Kafka messages that were generated, here is the link to the logs, here’s a slack link to the question I asked the integration team. Inevitably when my manager decides something needs to happen sooner, or I ask if someone wants to take my task, or I just come back to it days later… boom here’s a doc outlining exactly where I am. I just read through the doc and it takes less time than redoing everything all over again. I have 4-5 of these docs during the week because I don’t work on just one thing at a time.



@DrizzleORM Independent governance. Open source. Full-time team. PlanetScale played this perfectly.



Programming was deeply satisfying work to me. Work for hours/days before getting the payoff of the code working well on your machine. I’m feeling so much friction now to open the editor and do this kind of task by hand, but also increasingly depressed with the nature of work in an AI assisted dev workflow. Back and forth prompting seems to eat at my soul. Need to find a balance that brings back some of the toil.




















