[{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/ai/","section":"Tags","summary":"","title":"Ai"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/byte/","section":"byte","summary":"","title":"byte"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/","section":"byte\u0026beat","summary":"","title":"byte\u0026beat"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/governance/","section":"Tags","summary":"","title":"Governance"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/low-code/","section":"Tags","summary":"","title":"Low-Code"},{"content":"No-code / Low-code was supposed to save us from code.\nThat promise was always a bit theatrical. What low-code really did was lower the floor: more people could build useful software without opening a full development stack and summoning architecture review as a form of recreational punishment.\nThat worked until the apps became important.\nNow AI is changing the bargain again. The result is not the end of low-code. It is low-code becoming code again — and the model replacing it has a name: vibe coding.\nThe arc looks like this:\nflowchart LR A[No-codeVisual assembly] --\u003e B[Low-codeGuided customization] B --\u003e C[AI-assisted low-codePrompt + project files] C --\u003e D[Governed software deliveryGit, code agents, pipelines] The old promise had a ceiling #No-code and low-code worked best for a narrow class of problem:\ninternal tools straightforward workflows lightweight automation apps that fit neatly inside the platform\u0026rsquo;s happy path The appeal was obvious: faster delivery, less ceremony, fewer developers rebuilding the same approval workflow for the 400th time.\nThen the apps got real. Integrations appeared. Security mattered. Environments multiplied. Someone asked about deployment, audit, or scale, and the cheerful drag-and-drop story started sweating through its shirt.\nLow-code was never fake. It just had a ceiling. Complexity did not disappear. It waited off-screen until somebody tried to run the thing properly.\nMicrosoft\u0026rsquo;s tooling is telling the truth #The clearest signal is not the marketing. It is the tooling Microsoft is shipping.\nPower Pages now supports CLI and Git workflows.\nCopilot Studio has moved into VS Code.\nPower Apps Code Apps turns apps into code projects.\nPower Apps Vibe starts from prompts and generates from intent.\nPut those together and the pattern is obvious: the visual layer still exists, but the serious work is moving toward files, repos, local tooling, and AI-assisted development.\nThat matters because once these things become code projects, they can be used with Claude Code, Codex, and GitHub Copilot instead of being trapped inside a browser designer.\nUsing Claude Code with a Power Pages code project Using Claude Code with Copilot Studio in VS Code That is not low-code failing. That is low-code maturing into the same operational reality as the rest of software.\nflowchart TD A[Prompt or visual intent] --\u003e B[Project files / generated assets] B --\u003e C[Claude Code / Codex / GitHub Copilot] C --\u003e D[Git + review + pipelines] D --\u003e E[Power Platform runtime + governance] AI did not remove engineering #AI makes creation cheaper. It does not remove engineering. If anything, it raises the premium on judgment.\nWhen a platform can generate an app, flow, or agent from a prompt, someone still has to answer the questions that matter:\nIs the data model any good? Are the security boundaries sensible? Will this survive multiple environments and deployment cycles? Does the generated logic solve the actual problem or just produce a convincing demo? The old fantasy was that no-code meant engineering disappeared. The real version is stranger and more useful: you describe intent, AI works against project files underneath, and engineering moves from manual construction to review, structure, and governance.\nThat is closer to \u0026ldquo;true no-code\u0026rdquo; than the original sales pitch ever was. It just is not the kind people expected.\nThe citizen developer did not disappear #The old model rewarded people who could assemble solutions inside a guided UI. The new model rewards people who can direct AI, inspect output, and tell the difference between \u0026ldquo;works in a demo\u0026rdquo; and \u0026ldquo;will not become a governance incident by Q3.\u0026rdquo;\nThe manual effort is shrinking. The judgment requirement is not.\nSo what is Power Platform becoming? #It is becoming less of a place where software is handcrafted visually and more of a governed runtime for software assembled through prompts, code projects, configuration, and platform services.\nThat is a more honest role. Power Platform is good at governance, environments, connectors, policy, and control. None of that is glamorous, which is exactly why it matters.\nThe visual experience still matters. The productivity story still matters. But the durable value is shifting toward this:\nlet AI accelerate creation let code projects expose the work to better tools let humans provide judgment let the platform enforce guardrails That is not the death of low-code. It is low-code growing up.\nWhere this lands #Low-code is becoming code again because success raised the stakes.\nOnce these platforms started carrying real processes, real data, and real risk, they inherited the same concerns as every other software stack. AI accelerates creation, but it also removes the comforting illusion that visual tooling alone is enough.\nThe future is not no-code versus pro-code. That was always a slightly silly binary.\nThe future is faster generation, real project artifacts, stricter judgment, and governance that can survive contact with production.\nThe winners will not be the people who prompt the fastest. They will be the teams who can absorb that speed without turning their platform into a compliance-themed escape room.\nReferences # Power Pages CLI Copilot Studio in VS Code Power Apps Code Apps overview Power Apps Vibe overview ","date":"12 March 2026","permalink":"https://byteandbeat.dev/byte/low-code-is-becoming-code-again/","section":"byte","summary":"\u003cp\u003eNo-code / Low-code was supposed to save us from code.\u003c/p\u003e","title":"Low-Code Is Becoming Code Again"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/power-platform/","section":"Tags","summary":"","title":"Power-Platform"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/software-architecture/","section":"Tags","summary":"","title":"Software-Architecture"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/","section":"Tags","summary":"","title":"Tags"},{"content":"So here we are. Nobody asked, yet here we both are. 600 million blogs on the internet, and I decided to add one more. You\u0026rsquo;re welcome.\nWhy a blog? #Great question. Here are the real reasons, in order of honesty:\nPersonal brand. I attended one too many LinkedIn thought leadership posts and something broke inside me. Catharsis. Sometimes a Teams message just isn\u0026rsquo;t long enough to explain why a particular architectural decision was, technically speaking, a war crime. Proof of life. If I\u0026rsquo;m going to spend my evenings running in circles and dancing with strangers, I might as well also write about it. What to expect #Roughly two things:\nbyte — tech stuff. Microsoft ecosystem opinions. Power Platform hot takes. The occasional post that starts as a how-to and ends as a therapy session.\nbeat — life stuff. Running. Brazilian Zouk. The art of convincing your body to do things it didn\u0026rsquo;t sign up for.\nThe entire foundation of this blog. And most enterprise projects, honestly. A word of warning #I write the way I think, which means:\nSarcasm is the default tone, not the exception I will have opinions about your tech stack I will also have opinions about your running shoes Neither set of opinions was requested If you made it this far, congratulations. You\u0026rsquo;re already more committed to this blog than most enterprise digital transformation projects.\nSee you in the next one. Or not. No pressure.\n— atrinh\n","date":"9 March 2026","permalink":"https://byteandbeat.dev/byte/hello-world/","section":"byte","summary":"\u003cp\u003eSo here we are. Nobody asked, yet here we both are. 600 million blogs on the internet, and I decided to add one more. You\u0026rsquo;re welcome.\u003c/p\u003e","title":"I started a blog. Nobody asked."},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/life-choices/","section":"Tags","summary":"","title":"Life-Choices"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/tags/meta/","section":"Tags","summary":"","title":"Meta"},{"content":"","date":null,"permalink":"https://byteandbeat.dev/beat/","section":"beat","summary":"","title":"beat"},{"content":"Nothing to see here yet.\nCome back later if you\u0026rsquo;re really that curious. Or don\u0026rsquo;t. I\u0026rsquo;m a blog post, not a cop.\n","date":"1 January 0001","permalink":"https://byteandbeat.dev/me/","section":"byte\u0026beat","summary":"\u003cp\u003eNothing to see here yet.\u003c/p\u003e\n\u003cp\u003eCome back later if you\u0026rsquo;re really that curious. Or don\u0026rsquo;t. I\u0026rsquo;m a blog post, not a cop.\u003c/p\u003e","title":"me"}]