We just entered a new era of software engineering Writing code is no longer the bottleneck Thinking, designing, and making the right decisions is AI didn’t replace engineers It exposed who actually understands systems, products, and trade-offs The job is shifting from typing code → orchestrating intelligence Specs → prompts → PRs → production. If you’re still fighting AI, you’re already behind If you’re learning to work with it, you’re early This changes everything 🚀🤖

Quick look at the NFT marketplace architecture I’m building ⚙️ Not the user flow yet just reviewing the codebase structure and system design so far. Start with the foundation. Build the features later. #BuildInPublic #Web3 #DevTwitter full video here tiktok.com/@devp_b

AI didn’t make software engineering easier It made bad engineering impossible to hide Architecture, context, and decisions matter more than ever

Be a software engineer, not a developer AI can write code now. That part of the job is shrinking fast Developers ask: "How do I code this?" Engineers ask: "Should we build this at all?" AI handles the first question better every month. The second? Still 100% human System design. Architecture trade-offs. Understanding the business. Making it work in production That's engineering. And it's not getting automated The question isn't whether AI will replace developers. It's whether you're still just a developer

As a software engineer, you have two choices: work with AI, or struggle trying to keep up without it

Being a great software engineer isn’t just about code🧠 It’s about clarity Can you explain your architecture to a junior? Can you defend a design decision without ego? Can you document so well that others don’t need to ask? Strong communication is a multiplier. It turns good engineers into leaders⚙️ 💬 What’s harder for you: writing code or explaining it? #SoftwareEngineering #Communication #TechLeadership #CleanThinking

The biggest skill in software engineering isn’t learning new tech, it’s learning to design systems that don’t collapse under their own weight Anyone can make something work. Few can make it last 🧠 Senior mindset: •Fewer dependencies, more clarity •Small modules, big thinking •Code you can delete > code you can show off Good engineers ship features Great engineers reduce future pain What’s something you’ve built that aged badly? 😅

Cada semana publico de CERO a SENIOR, una newsletter para programadores que quieren crecer más allá del código. Ideas, proyectos reales y aprendizajes sobre cómo pensar como desarrollador profesional. 👉substack.com/home/post/p-177…

You don’t need another framework, you need deeper understanding A lot of devs jump from Next.js → Svelte → Astro → Remix thinking the tool will make them better But tools change Fundamentals don’t The developers who grow the fastest aren’t the ones who try every shiny new stack… They’re the ones who understand: 🔹 how the web actually works 🔹 how browsers render 🔹 how HTTP behaves 🔹 how to reduce complexity, not add it Frameworks are shortcuts, not replacements for knowledge 💡 If you can only build when a library tells you how, you’re not building, you’re assembling ✅ Learn the core concepts first ✅ Use tools because they solve a problem, not because they trend ✅ Master ideas, not dependencies The web changes every year Foundations stay forever 🙌🏻 #webdeveloper #webdev

Refinement is underrated 🧩 Breaking down tasks into small, isolated, and deployable pieces is where real engineering happens That’s the stage where problems surface , and where you solve them before opening your editor When you refine well, coding becomes execution, not improvisation⚙️ Plan precisely. Build calmly. Ship faster. 🚀 💬 How detailed do you go when refining your tasks? #WebDev #SoftwareEngineering #Agile #CleanCode

🧠 Weekends? No breaks here 🙌🏻 I’m still working on DDD-Forge, my open source PHP scaffolding tool for Domain-Driven Design The make:context command is almost fully refactored, cleaner code, better separation of responsibilities, and following Clean Code principles Next step: writing the tests, the most important part to make this command rock solid #buildinpublic #php #ddd #opensource #cleancode #IndieHackers

Good logging is invisible until you need it When everything works, no one cares about logs But when something breaks at 2 AM, good logs are gold ⚙️A solid logging strategy isn’t about printing messages, it’s about: 🔹 Context (who, where, when) 🔹 Structure (JSON > chaos) 🔹 Levels (info, warn, error, not everything is “critical”) 🔹 Traceability (connect requests end-to-end) Logs tell the story your app can’t 💬 How much time could better logging have saved you this year? #WebDev #Backend #CleanCode #Observability #SoftwareEngineering

Consistency is underrated in software design ⚙️ You don’t need the “perfect” architecture You need a consistent one Naming conventions, folder structure, error handling, API responses, all of it matters Consistency makes your code predictable, and predictability makes it scalable A messy system with good patterns beats a perfect system applied inconsistently 💬 How consistent is your codebase: 1 (chaos) to 10 (zen)? #WebDev #SoftwareEngineering #CleanCode

Frontend architecture isn’t about frameworks, it’s about boundaries. 🧩 Modern UIs often mix logic, data fetching, and presentation in one place It works… until it doesn’t A clean frontend separates concerns: 🎨 UI components → display data only ⚙️ State management → keeps the app predictable 🌐 Services / API layer → handles data fetching and transformations 🧠 Hooks or Utils → reusable logic for specific behaviors Good architecture scales with your app and your team. It’s not about React or Vue, it’s about clarity 💬 How do you structure your frontend projects? #Frontend #WebDev #CleanArchitecture #JavaScript

Error handling is architecture, not just code. ⚙️ Too many apps treat errors like afterthoughts, random try/catch blocks everywhere, mixed with business logic In a well-structured system: 🚪 Controllers → catch and translate errors into responses 🧠 Application layer → defines what’s recoverable and what’s not. 🏗️ Domain layer → throws domain-specific exceptions (e.g., UserNotFound). Proper error flow = predictable behavior. It’s not about avoiding errors, it’s about designing for them 💬 How do you structure error handling in your projects? #WebDev #CleanCode #Backend #SoftwareArchitecture

Why “Separation of Concerns” matters in web app design ⚙️ A good architecture isn’t about frameworks, it’s about boundaries Take an API example 👇 🧩 Controller → receives the request and delegates. 🧠 Application Service → validates input, handles errors, orchestrates logic. 🏗️ Domain Service → contains core business rules and retrieves data. 📦 Then, the controller returns the response to the client Each layer does one thing, and does it well That’s how you avoid spaghetti code, keep testability high, and make future changes painless Clean boundaries today = fewer headaches tomorrow. 💪 💬 Do you separate responsibilities this way in your projects? #WebDev #SoftwareArchitecture #CleanCode #Backend

🔧 Still working on my open source project DDD-Forge! After reaching the first minimal functional version, I’ve started a major refactor on the make:context command, improving structure, separating responsibilities, and cleaning up the codebase 3,654 additions later… it’s starting to look much better 👀 #buildinpublic #php #ddd #opensource #cleancode #IndieHackers

One day more building DDD-force🚀 My PHP Scaffolding cli-tool for Domain Driven Development package

🕒 What’s your most productive time of the day to code?