Mastodon
Experienced software engineer working hands-on at a modern development workstation, surrounded by visual representations of system architecture, APIs, integrations, workflow automation, inventory visibility, operational dashboards and connected business systems. The image reflects the combination of practical coding, technical leadership and systems thinking, with subtle branding for veloso.dev and systemsnotsilos.com.

Experience Should Bring You Closer to the Problem, Not Further From the Code

Experience in software engineering should not create distance from the work itself. The more years I spend across architecture, systems integration, technical leadership, cloud platforms and operational software, the more I value staying close to the code, the users and the real business problems being solved. For me, seniority is not about stepping away from implementation. It is about bringing better judgement to it. That means understanding the wider system, anticipating failure points, considering maintainability and operational impact, and still being willing to open the IDE, investigate the issue and build the solution. The most rewarding engineering work is often practical rather than flashy. It is reducing manual effort, simplifying workflows, connecting disconnected systems, improving visibility and creating software that genuinely makes someone’s day easier. That is the kind of work I continue to enjoy most.
Senior software engineer reviewing AI-assisted code, system architecture diagrams, API integrations, cloud services, automated testing, observability, and security checks in a modern engineering workspace.

AI-Assisted Engineering Still Needs Real Engineering Judgement

AI-assisted development can accelerate delivery, but it does not replace software engineering judgement. The strongest engineering teams use AI to move faster while still protecting architecture, testing, security, maintainability, and long-term system quality.
Diagram-style image showing an AI-assisted engineering workflow with agents moving through intake, planning, build, verification, review, evidence, and retrospective stages.

AI Agents That Ship: From Prompting to Evidence-Based Engineering

AI-assisted engineering is moving beyond simple code generation. The real value comes from designing controlled workflows where agents produce evidence, pass verification gates, and support delivery without weakening engineering discipline. This post explores how intake, planning, implementation, verification, review, closing, and retrospective agents can form a safer AI-enabled software delivery pipeline.

Principal AI Engineers Are Not Building Models. They’re Building Systems.

One line in a recent Principal AI Engineer job advertisement stood out to me:“Ideally you’re a software engineer first, ML engineer second.”That single statement captures one of the biggest shifts happening in AI engineering right now.For years, many organisations treated AI as a research problem.Build a model. Run experiments. Create a proof of concept. Present some impressive metrics.Then production arrived.And suddenly the hardest problems were no longer the model itself.They became: ArtificialIntelligence #AIEngineering #MachineLearning #MLOps #SoftwareEngineering #SoftwareArchitecture #DistributedSystems #CloudInfrastructure #PlatformEngineering #DevSecOps #SolutionsArchitecture #SystemIntegration #TechnologyStrategy #EngineeringLeadership #VelosoDev #SystemsNotSilos #GumtreeDev
A split-scene professional illustration showing a senior engineer standing between two worlds. On one side, an overloaded digital hiring pipeline filled with glowing AI resume scanners, automated rejection dashboards, keyword matching systems, and thousands of faceless resumes flowing through dark enterprise systems. On the other side, real human interaction: technical whiteboard discussions, architecture diagrams, engineering leadership meetings, and professional networking conversations. The engineer looks calm but skeptical, holding a resume while distorted AI scoring metrics incorrectly label credentials as “Poor Match.” Use sophisticated dark tones with subtle amber, graphite, and muted purple highlights instead of excessive blue. The visual should feel modern, enterprise-oriented, intelligent, and slightly cautionary rather than dystopian. Include subtle references to systems architecture, interoperability, and enterprise technology ecosystems. Suitable for LinkedIn and WordPress feature image usage.

The Resume Arms Race Is Breaking Hiring, Not Fixing It

The technology hiring market is entering a strange phase where candidates increasingly use AI to mass-apply while recruiters increasingly rely on AI to mass-reject. After receiving an ATS report incorrectly rating his education and experience as “poor,” Pedro reflects on how automation is reshaping engineering recruitment, trust, and professional visibility.
A cinematic technology and logistics themed infographic showing a software engineer overseeing AI-driven workflow automation, systems integration, and operational platforms connected to a modern shipping port with cargo vessels, containers, APIs, cloud systems, and digital engineering overlays.

AI Automation Is Not About Prompts. It Is About Fixing Operational Friction.

A lot of AI conversations still focus on prompts, models, and hype. But in real operational environments, the biggest gains often come from workflow automation, systems integration, and reducing friction between disconnected processes. This post explores why practical AI implementation, systems thinking, and engineering fundamentals may matter far more than simply “using AI”.
Feature image showing a futuristic software engineering workspace focused on Cursor IDE, featuring an AI-assisted coding interface on a laptop screen, modern development dashboards, code generation panels, and visual elements representing intelligent software development, code review, refactoring, debugging, and AI-powered engineering workflows.

Cursor IDE Is Not Just an Editor. It Is Changing How Software Engineering Works.

Cursor IDE is changing software engineering far beyond autocomplete. AI-assisted workflows are reducing engineering friction, accelerating code reviews, improving architecture understanding, and reshaping how modern engineering teams build large-scale systems.
Illustrated enterprise AI architecture showing autonomous AI agents coordinating through a central orchestration layer across cloud infrastructure. The scene includes API gateways, workflow automation pipelines, secure data services, monitoring dashboards, event-driven microservices, and integrations with CRM, analytics, and logistics platforms. Engineers and solution architects are shown collaborating around large digital displays featuring TypeScript, Python, .NET, AWS, and agentic workflow diagrams. The visual style is modern, highly technical, and enterprise-focused, representing scalable AI-driven automation and distributed systems engineering.

Designing AI Workflow Platforms Is Not About “Adding ChatGPT”

Modern AI platforms are not just “ChatGPT integrations”. The real engineering challenge is designing reliable, scalable, secure workflows around AI in production environments.
Please activate Your licensed with purchased email address. ! let's activate Now