We raised $21M to help small businesses beat the giants We're giving $1M of it back to you today Today we're launching Runable Grow: world's first agent that runs your entire go-to-market. 24/7 The last few months have been unreal. Millions of users came to @runable_hq and built their entire business on it, websites, databases, payments, analytics, pitch decks, product videos & scheduled work. Every single one of them asked the same question: "How do I grow it?" So we built the answer. Runable Grow handles GTM end-to-end: → Runs ads on Meta, Google, and ChatGPT without any account, fully managed by Runable → Cold calls + cold emails from a real phone number and your business inbox → Generates and qualifies leads → Social listening → SEO + AEO optimization Not a dashboard. Not a "copilot." An agent that does the work. It's a world-class media buyer, SDR, SEO lead, brand analyst working for your business while you sleep. Don't believe me? Prove me wrong. Your first $100 on Grow is on us. Every paid user. No catch. Go break it 👇 runable.com

Software Engineers, what's your backup plan if Artificial Intelligence writes better code than you in 2 years?

Why did software engineers create AI to replace them?

In my experience, the cost of building software hasn't decreased at all. People are still working 40 hours every week. They are still putting in maximum effort to build whatever they are building. Are we shipping more and better software? Likely yes. But we are also paying a ton of money in tokens, and I don't really see companies firing half their development teams to save money.

can you imagine a "vibe coder" being able to answer so many questions without technical understanding? software engineering is not dead. and probably won't be for a long time to come because RL env companies won't be able to build an environment for *ALL* kinds of problems. why? because we will always have more problems to solve at higher levels of abstraction. period.

I think it might still be valuable to learn how to code. Basics, like intro to Python type stuff. Not because AI can’t do it for you and infinitely better than you. I just think you need it to be more effective with AI. The more you know about what you are asking AI to do ———> the better the prompts AND results. But I’m not sure how much you need to know. How much is enough?

Reading books matters more now than it ever has. Should we start a book club?

We are all learning here, so I’m in no position to tell you how you should write and review your code. What I can tell you is what's working for the people I work with and me. We aren't manually reading the code anymore. We don't care about individual lines. We don't have anybody trying to understand the thousands of AI-generated lines we get. Instead, we have designed (and continue to invest here) automated processes to verify that we are shipping high-quality software, The quality of our software hasn’t gone down in any way, shape, or form. We are delivering more and faster. People are working the same amount of time, but the nature of their work has changed significantly. I don't know what you are building and how you are doing it, so I'm not going to pretend I can speak about how you should do it. If you find value in reading AI-generated code, good for you! If you think that's the best way for you to verify the software you build is good, then keep doing it.

Many different things: • Automated tests (unit and integration) • Acceptance tests (QA team) • Automated QA (many tools do this now) • Verification loops (another agent checking the code) • Code reviews (many tools do this now)

I still don't understand how people are not reviewing code for things they care about. Parallel implementations just spread like wild

me every day: I need to record more videos > but let's solve this bug first I need to record more videos > but let's check Slack first I need to record more videos > but let's build this feature first I need to record more videos > but let's check my stocks first