Perete Harrison

You give a coding agent a bug and say, “This is the problem. Fix it.” The agent works on it, changes a few files, and comes back with “Implemented.” Okay, good. But did it actually fix the problem? You can run the application, open your browser, and try the behavior yourself. You can also run automated tests. Another check we can stitch into that workflow is an LLM as a judge . Let’s reason this out. We give the LLM an output, a rubric describing what good looks like, and evidence. It assesses where the result meets those criteria, falls short, or still needs verification. 1. Start with the issue Describe the bug → coding agent → proposed fix. Say you enter the wrong password, click Log in , and the loading spinner keeps spinning. You ask the coding agent to fix it. The agent returns a change. That gives us something to assess. Define what “fixed” means Before accepting it, we put together what “fixed” should mean: A wrong password shows a clear error. The spinner stops when t...

Are you tired of AI coding agents churning out generic, flat, and uninspired frontend layouts? In this video, we dive into why standard LLM outputs often result in "AI slop" and how to fix it with the AXON framework. We explore AXON-COMPOSE, a specialized frontend design skill that forces AI agents to move beyond static, repetitive code. By enforcing composition-first principles, premium typography, and intentional motion, AXON-COMPOSE delivers high-fidelity UIs that are ready for production. In this video, we demonstrate: The common pitfalls of "Baseline" AI coding output. How AXON’s spec-driven development protocol changes the game. A side-by-side comparison of standard LLM results versus the high-fidelity outputs of AXON-COMPOSE. Stop the AI slop and start shipping predictable, visually stunning software with a protocol built for high-performance teams. Check out the AXON repository here: https://github.com/atopwebtechnologies/axon https://github.com/atopwebtechn...

This video features a step-by-step walkthrough of a Google code lab on building distributed multi-agent AI systems, led by Perete Harrison (DevOps Software AI Engineer) and Koye Adeyombo (Front-end Development Engineer) from Atop Web Technologies. Video Overview: Building Multi-Agent AI Microservices [RAW] In this comprehensive session, the engineers demonstrate how to go beyond simple chatbots to create a sophisticated, distributed system using the Agent Development Kit (ADK) and Google’s Gemini models. As this is a raw, unedited walkthrough, viewers will see the engineers encounter and troubleshoot real-world issues, such as credential and project resolution errors, in real-time. Perete Harrison explains the underlying concepts as they navigate the code lab, which was originally created by Amit Maharaj. They build a course creation system where specialized agents—a Researcher, a Judge, and a Content Builder—coordinate through an Orchestrator to produce high-quality educational conten...

  No doubt we have moved on from generation to verification . I mean, for the past few years, the amount of code I write with my own hands has dropped drastically. In some cases, almost to zero. Most times now, I am verifying output, reviewing generated code, checking if it actually solves the problem, catching hallucinations, and maintaining what comes out of the AI. That is a big shift. Years back, loose prototyping, implicit shortcuts, clever ways of doing things, all of that made sense. The developer was the one writing the code, so if it made sense in your head and saved you some time, fine. But now, when a lot of the code is generated for you, the question becomes different. Can I easily understand what this thing is doing? Can I verify it? Can I quickly spot when something is wrong? This is one reason I keep liking Go more. Of course, Go is my favorite programming language, so I may be biased. But seriously, Go code written by a senior engineer, a junior engineer, or generat...

  To me, as I advanced in programming, I came to realize the true difference between programming and software engineering. Software engineering is applying engineering principles to build software web applications, desktop applications, mobile apps, or services. But as you progress, you see it's much more about collaboration. Working with other engineers to architect, design, build, test, implement, and deploy robust, high-performance, predictable systems that can evolve over time. Programming is writing code to solve a specific problem. And that's part of it. But software engineering is the broader discipline. Collaboration and process that make those solutions durable and scalable. The gist is, programming focuses on writing code to solve a problem. Software engineering includes that, and adds design, architecture, testing, deployment, and teamwork to build systems that last.

  To architect, design, build, test, and deploy predictable applications and services, planning is inevitable. Given the pitfalls of coding agents and their non-deterministic nuances, we are excited to announce AXON , an open-source protocol and plugin from Atop Web Technologies for AI coding agents like Codex, Antigravity, and Claude Code. AXON stands for Atop eXecution Orchestration Network . Its main purpose is to solve a huge problem in AI-assisted development: agent drift . When building with AI, agents are very fast, but they often lack durable context between sessions. They forget product intent, design systems, tech stack decisions, workflows, testing expectations, and why certain decisions were made in the first place. That is where unpredictable results start. AXON introduces a protocol to fix this: Context first, specification second, implementation third, verification always. What AXON Does With AXON, the agent does not just jump into code. It initializes the project c...

How to Stand Out in a Tech Interview in 2026 Getting a tech job in 2026 is not impossible, but let’s be honest, it is difficult. The market is more competitive, AI is changing how companies work, and many candidates are applying for the same engineering roles. So whether you are a DevOps Engineer, Backend Engineer, Software Engineer, AI Engineer, Frontend Developer, or Web Developer, you need more than a polished CV. I have interviewed engineers across different roles, and one thing I have noticed is that most candidates focus only on looking prepared. They polish their resume, rehearse their answers, and try to present themselves well. That is good. It shows preparation. But that is not always what makes someone stand out. Find Out Why the Role Is Open Whenever a company opens a position, there is usually a real reason behind it. Maybe they are building a new team. Maybe they urgently need someone who can join and start contributing quickly. Or maybe an experienced engineer left, and ...

  Believe it or not, traditional software development is almost dead. Software development is heading toward AI-native product engineering: smaller teams, faster prototypes, more automation, agent-assisted delivery, heavier emphasis on quality control, and a stronger need for cloud, DevOps, and security discipline. The future stack is no longer just apps plus cloud. It is apps, cloud, automation, observability, security, and AI agents working together. AI is now embedded into development, infrastructure, security, and operations. One thing we have observed at Atop Web Technologies is that AI agents are now part of the team. Chatbots are almost dead. Companies are no longer just asking for chatbots; they are actively building and deploying agents that can support real workflows, engineering teams, operations, and product delivery. Personally, I have moved from coder to AI orchestrator. I now spend more time coordinating AI agents, reviewing output, setting architecture, deciding wha...

 Learn how to run multiple applications on one docker host with Traefik Reverse proxy

There comes a time when a person needs a proper home on the internet. Not just a social media account. Not just a company profile. Not just posts scattered across different platforms. A real place. A place where thoughts, work, ideas, lessons, experience, projects, writings, and personal reflections can live together in one public space. That is why I created this website. My name is Perete Harrison . I am a DevOps Software Engineer, Software Architect, AI Engineer, founder, builder, and problem solver . I am the founder of Atop Web Technologies , Perete Web Technologies , and other ventures I have co-founded. Over the years, I have developed a deep interest in, and practical experience across, the full lifecycle of web services and applications. This website is my personal space. It is where I will write about software engineering, DevOps, cloud infrastructure, AI, system architecture, automation, backend systems, frontend systems, performance, deployment, technical problem-solving,...