Hi, PapaFam! ☀️ It is no longer news that FABLE, which was recently released, has been shut down for reasons best known to its creators. shout-out to Sonny and every other dev who play with it before it remove However, this post is not really about FABLE. It is about the lessons many of us have learned from following the AI Agent Series Sonny started and watching how software development is gradually evolving before our eyes. First, a special shout-out to our great teacher and the entire team Sonny and Jay who continue to lead from the front, helping us understand what these new AI models can truly do. Through every episode of the series, we have seen ideas transformed into real applications faster than many of us thought possible. At this point, we are no longer surprised that AI can write code. The bigger question is: HOW DO WE POSITION OURSELVES AS DEVELOPERS IN THE AGE OF AI? After following every episode of the AI Agent Series, here are five lessons that stood out to me that we can learn from SONNY. - 1. INSTALL YOUR DEPENDENCIES AND PACKAGES YOURSELF One thing I have noticed repeatedly is that AI does not always recommend the latest packages, versions, or installation methods. Sometimes it suggests outdated dependencies, deprecated libraries, or approaches that are no longer considered best practice. As developers, we should always verify package versions, check official documentation, and understand exactly what we are installing before adding it to our projects. - sonny preach the above a lot the OG should know by now AI CAN ASSIST YOU, BUT IT IS YOUR RESPONSIBILITY TO ENSURE YOUR PROJECT IS BUILT ON THE RIGHT FOUNDATION. - 2. INSTALL ALL THE SKILLS AND PLUGINS REQUIRED FOR YOUR PROJECT An AI agent is only as effective as the tools available to it. Whether it is APIs, MCP servers, SDKs, plugins, databases, or external integrations, the quality of your output often depends on the tools connected to your workflow. Many times, the limitation is not the model itself but the lack of the right tools needed to accomplish the task.

Episode 12 of our new Series 'Code with AI the Right Way' is here! — and this time, we're building a Zendesk / Intercom clone LIVE from scratch! (It even includes AI Agents and B2B Billing!) This is a LIVE build — mistakes, debugging, and all. That's the point. You learn more watching someone solve real problems in real-time than from a polished, pre-recorded tutorial.

Hey Papfam, Let’s talk about what’s really happening in our editors right now especially in this new era of Opus 4.6 and Codex. You’re building something complex maybe a real-time comment system or a deep auth flow. You get stuck. You prompt your AI. And just like that boom. 200 lines of clean, confident TypeScript. Structured. Typed. Production ready. You paste it. It works. You ship it. Then someone asks: Why is that hook structured that way? What happens if that cache invalidation fails? And suddenly: Em… let me check. --- Welcome to the Age of the Black Box Developer We’ve entered a new phase of development. Not just AI-assisted coding but AI-driven building. Models like Opus 4.6 are designed for deep reasoning and understanding entire systems, while tools like Codex are optimized to execute and ship code fast. Together, they’ve changed the game. You no longer need to struggle through every abstraction. You can generate architecture. You can delegate implementation. You can ship faster But here’s the problem: You can now build systems you don’t understand. --- This Isn’t Just About Speed It’s About Ownership Let’s be honest. We’re not just coding faster we’re thinking less about the code itself. And that creates a new kind of developer: > Someone who can ship features at 10x speed… > but can’t explain 40% of what they shipped. That’s the Black Box Developer. And in the Opus + Codex era, it’s becoming normal. --- Why This Becomes Dangerous AI today isn’t just autocomplete it’s a collaborator. But it has a split personality: According to researchers Opus thinks deeply but may overcomplicate or abstract Codex executes quickly but may skip deeper reasoning If you blindly trust both, you inherit their blind spots. That leads to three real problems: Debugging becomes impossible You don’t know the system you only know the outcome. Architecture becomes accidental Your app works, but no one truly designed it. You lose technical authority

Anyone with an idea how long does TikTok take to approve the App its been over a week

Set your reminder here 👉 https://youtube.com/live/jDTuQTR8gU0 Episode 4 of our new Series 'Code with AI the Right Way' is here! — and this time, we're vibe coding a Quickbooks / Xero Clone LIVE from scratch! This is a LIVE build — mistakes, debugging, and all. That's the point. You learn more watching someone solve real problems in real-time than from a polished, pre-recorded tutorial.