Andrew
672 posts

Andrew
@dremnik
founder, designer, and engineer | part-time token dealer






everything is programming




Unpopular take: You should learn more programming. Take more courses. Watch more videos. Practice by hand. Read books. Yes, freaking books. Even if, and especially if, you are using AI to do most of the work. Do it in between instead of scrolling f*ing TikTok. Do it at the gym on the bike. Do it at night. Do it whenever. Focus on things you can't do well manually yet. Study other languages like Zig and Rust. Get really good at React and Typescript and other things you use all the time in your projects (whatever they are, these are just examples). Study the various libraries and the choices those developers made. The more you understand, the more you can guide the AI. And you will make stronger architectural decisions and spot security issues and bad coding practices that you can overrule as you shepherd your AI sprites.







🚨INTERVIEW: Bryan Johnson just took the world's biggest dose of psychedelics... here are his reactions 48 hours later. @friedberg sits down with @bryan_johnson (0:00) Friedberg intros Bryan Johnson (0:54) Why Bryan Johnson did 5-MeO-DMT (12:56) What brain scans actually show (18:36) Psychosis, bad trips, and life-altering decisions (26:23) The next frontier: organoids and gene therapy (33:26) GLP-1s, abundance, and human optimization (35:35) The longevity drug nobody's talking about? -------------------------------------- Thanks to our partner for making this happen! The Pod by @eightsleep cools your bed to 55°F and uses Autopilot to optimize your sleep, all night. Use code ALLIN at eightsleep.com/allin for up to $350 off.

This is a great report on the state of software and AI by @Redpoint - thank you, @loganbartlett! Where I disagree is the build vs. buy slide: 1) I'm not sure if it takes ~12 engineers to build/maintain a Slack clone for 1 customer. As AI keeps getting better at not only code gen but all software engineering tasks I think you'll be able to do it with a smaller team. Doesn't mean you should spend engineering time on it because I expect... 2) ... there will be agencies who specialize in this kind of work (e.g. build a Slack clone and sell customized versions of it). 3) ... there will be lots of cheap, (more or less) good enough Slack clones 4) ... there will be AI-native startups that rethink the category. All of these factors, I think, will contribute to pricing pressure for Slack and other traditional SaaS companies ... which they will only be able to defend against if they get a share of the agentic revenue enabled by their products.





I hope schools are teaching kids to just sit down with codex / claude code and make stuff.








