I JUST RECEIVED THE FINAL VERSION OF THE BOOK!🥹 We poured EVERYTHING into this book. Many books focus on AI from the perspective of the highest levels of education but what about the average corporate dev that wants to stay ahead & do well at their jobs? We wrote this for you!

CYC 27 September 28-30th 👀

CYC 27 September 28-30th 👀

Critical thinking and ability to effectively communicate processes is an essential skill requirement that cuts across different disciplines.

You should read and watch this...!!!

💯 Judgements and decisions are now the moats

One of the biggest mistakes developers are making in the 2026 job market is confusing a finished project with proof of engineering ability. Y'all need to understand something: Nobody is hiring you because your portfolio has a cool application. They ARE hiring you because of the engineering conversations that application allows you to have. Think about two candidates walking into an interview with the exact same AI-powered project. - Candidate #1 explains what the application does, which AI tools they used, and shows off the features. - Candidate #2 explains WHY they designed it the way they did. Where they used deterministic logic instead of AI. How they handle unreliable model outputs. What happens when the system fails. What tradeoffs they made and WHY. Same exact project. Two completely different interviews. One demonstrated that they could produce software. The other demonstrated that they understood how to engineer it. And this is why I keep pushing developers to understand the decisions they're generating with AI. I don't really care if AI wrote 100% of your code. But if you can't explain the architectural decisions, defend your tradeoffs, or identify where things could go wrong, you've missed one of the biggest opportunities that project was supposed to give you. AI lowered the barrier to building software. It did NOT lower the bar for understanding it and making the right decisions. We got into this on the latest episode of The Programming Podcast because I think developers need to fundamentally rethink what they're trying to accomplish with portfolio projects. #code #coding #programming #softwareengineering

Learn how to become a better software engineer from an Apple veteran with over 12 years of experience building products. This The Programming Podcast episode is with @RayFernando1337 and @leonnoel! 00:00 Meet Ray Fernando: 12 Years at Apple 01:51 How Ray Uses AI Agents to Build Software 05:24 The Real Cost of AI Agent Workflows 07:25 Automating Email with AI 10:52 A Word from Our Sponsors 13:13 Building Reliable AI Agents and Verification Systems 18:31 How to Keep Up with AI as a Software Engineer 21:01 Skill Chaining: Building Better AI Workflows 24:05 CSV vs. JSON and Why AI Constraints Matter 26:32 Claude vs. Codex vs. Gemini: Choosing the Right Model 31:17 Leon's AI Workflow for Shipping Code Faster 35:41 Behind the Scenes of Undersold AI 39:01 When Is an AI Product Ready to Launch? 43:04 Why Danny Walked Away from Two Software Projects 48:40 Fail, Pivot, Grow: Turning Failure into Progress 49:13 From Wedding DJ to Apple Engineer 53:09 How to Build Relationships and Network in Tech 58:19 What It Takes to Succeed as an Engineer at Apple 1:02:56 What Separates Great Engineers from Average Engineers? 1:06:50 Listener Q&A: What AI Portfolio Project Should You Build? 1:10:52 Why Most Developers Build the Wrong Portfolio Projects 1:14:41 Final Thoughts and Outro

Super hyped for this episode. Got into pstack & Grok Bot plus lots of alpha.

I recommend watching The Programming Pod with @leonnoel @DThompsonDev and @RayFernando1337 talk about skill chaining, token efficiency and other cool agentic things 🔥🔥🔥 piped.video/y-Kb3RSk0bo?si=SHsO…

Will we still have a job in five years? On Nov 13, JetBrains AI.js Day puts frontend's scariest AI questions on air, live, online, and free. Kent C. Dodds, Marina Wyss, Danny Thompson, and more. Register now: lp.jetbrains.com/ai-js-day-2…

Be completely honest software developers. When is the last time you actually touched code instead of just prompting AI?

Closing keynote and a packed house after an extremely busy week at Team ’26 Europe in Amsterdam! From a Software Developer and Product perspective, this week was GOLD! The most valuable part of this week was proximity to problems. Here are some huge takeaways: - 15 MILLION+ MCP tool calls every day! Atlassian's MCP server just got a massive upgrade with 220 tools, expanding what developers and AI agents can access and accomplish across the Atlassian ecosystem. - Loom can turn a screen recording into instructions for an AI agent. Instead of spending time explaining every visual change in a text prompt, developers can show what they want, talk through it, and have Loom generate structured instructions and acceptance criteria. - Loom can also generate video walkthroughs of pull requests. It can run the previous and updated application, demonstrate what changed, explain implementation decisions, and show how the changes were tested. Think about how this changes code reviews as AI-generated PRs become more common. - Atlassian built its new Artifacts application entirely on Forge! Not just a custom panel or extension. The UI, search, Teamwork Graph integration, Smart Links, and MCP tools were all built using Forge. If you've been wondering what you can actually build with Forge, this should expand your thinking. - 250 BILLION+ objects and relationships in the Teamwork Graph. AI is only as useful as the context it can access. Connecting work, knowledge, code, people, and decisions gives agents a much better foundation to operate on. - Up to 25% fewer tokens with the upgraded MCP server. More capabilities don't automatically have to mean higher token costs. How we design the infrastructure around our agents matters. One thing became increasingly clear this week. The conversation around AI development needs to move beyond which model you're using or how quickly you can generate code. How are you giving agents the right context? How are you making their work reviewable? How are you connecting that work to the rest of your organization? Those are engineering decisions, and they're becoming more important as AI adoption accelerates. There's a LOT for Software Developers and builders to explore here! #AtlassianTeam26Europe #Team26Europe #Atlassian

5 am and the only person in the gym. Even though I'm in Amsterdam for Team 26 Europe, the workouts haven't stopped! Locked in and determined to get healthier 😤

Huge shout-out to @rbolte and team for a great event tonight bringing the Atlassian community together in Amsterdam! Amazing time and such a great opportunity to learn about how many developers are leveraging Forge, Rovo, and Teamwork Graph to solve problems! The house was packed with Marketplace Partners, App creators, engineers, Product Managers, and more! Great event after all the great talks at Team '26! #AtlassianTeam26Europe

Yesterday I taught a 3-hour Forge workshop at Team ’26 Europe in Amsterdam! We took meeting notes, used AI to understand the work inside them, created Jira tickets, preserved context in Confluence, added human approval, and handed eligible work to an agent. The thing I want software developers to understand is this: Forge is not just “build something inside Jira.” You can build real workflows across the Atlassian ecosystem with backend logic, state, queues, permissions, AI, and agents. If you’ve never built with Forge before, I hope that makes you think a little differently about what’s possible. I’m at the Forge booth today! Come build with me and geek out about what you can create!