[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"topics":3,"posts:sdd::1:6:":62,"$fmAbo7HX1697lOJ4AVNBJl1PR7wUF0IkR_62krtbwQAE":94},{"data":4,"meta":59},[5,15,23,31,40,50],{"_id":6,"name":7,"description":8,"image":9,"imageAlt":10,"slug":11,"createdAt":12,"updatedAt":13,"uuid":14},"6a92c7892f7e20762f654f94","AI","Posts on AI in real product and engineering work: building AI-powered tools, using large language models for SEO and data platforms, and honest takes on where AI actually helps versus where it's overhyped.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewsai-2.jpg","AI flying to you!","ai","Sat Aug 29 2026 19:50:33 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 20:18:46 GMT+0800 (Singapore Standard Time)","6f2f7079-c45c-4d74-b758-5419dd8755ee",{"_id":16,"name":17,"description":18,"image":19,"imageAlt":19,"slug":20,"createdAt":21,"updatedAt":21,"uuid":22},"6a92d5d26d3bae502260bcb4","CTO Show by TechVibe","Notes from the CTO seat - security, compliance, vendor relationships, build-vs-buy decisions, and the less glamorous parts of leading engineering that rarely make it into the highlight reel. All things given to Support TechVibe team.","","cto-show-by-techvibe","Sat Aug 29 2026 20:51:30 GMT+0800 (Singapore Standard Time)","afaf2020-622a-4b9c-961a-2e36d936230b",{"_id":24,"name":25,"description":26,"image":27,"imageAlt":19,"slug":28,"createdAt":29,"updatedAt":29,"uuid":30},"6a92d6156d3bae502260bcd3","Good Reads","Books Michal has actually read and would recommend to engineers and engineering leaders - from technical classics like Designing Data-Intensive Applications to leadership reads like Staff Engineer.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnews\u002Fagainst.jpg","good-reads","Sat Aug 29 2026 20:52:37 GMT+0800 (Singapore Standard Time)","a9f75c75-c1b9-4637-b7ee-592babde3aae",{"_id":32,"name":33,"description":34,"image":35,"imageAlt":10,"slug":36,"createdAt":37,"updatedAt":38,"uuid":39},"6a92d78c6d3bae502260bdc3","Technology","A running log of tools, frameworks, and technical decisions Michal has actually used and formed opinions on - from React and Tauri to DevOps culture, database architecture, and API tooling.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewscity.mp4","technology","Sat Aug 29 2026 20:58:52 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 21:03:33 GMT+0800 (Singapore Standard Time)","b9d2bf10-b22e-4afa-b778-2bb49d12a884",{"_id":41,"name":42,"description":43,"image":44,"imageAlt":45,"slug":46,"createdAt":47,"updatedAt":48,"uuid":49},"6a92dace6d3bae502260c000","CTO work","Notes from the CTO seat - security, compliance, vendor relationships, build-vs-buy decisions, and the less glamorous parts of leading engineering that rarely make it into the highlight reel. Plus bit of utopia in the topic image. ","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewscto.jpg","CTO of the Future","cto-work","Sat Aug 29 2026 21:12:46 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 21:13:06 GMT+0800 (Singapore Standard Time)","89273ffa-05fb-4e6d-bc6b-21fa593d4c8e",{"_id":51,"name":52,"description":53,"image":54,"imageAlt":55,"slug":56,"createdAt":57,"updatedAt":57,"uuid":58},"6a9373be6d3bae5022611315","DIY","Michal's own side projects and builds - desktop setup evolutions, Ace the chatbot, and small apps built for the fun of solving a real problem.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewsdiy.jpg","Do it yourself","diy","Sun Aug 30 2026 08:05:18 GMT+0800 (Singapore Standard Time)","ac6dffb6-41ee-41b0-8819-fed9ac1d26ca",{"totalnoOfItems":60,"perPage":61,"noOfItemsOnCurrentPage":60},6,24,{"data":63,"meta":92},[64],{"_id":65,"id":66,"title":67,"alt":68,"category":69,"categorySlug":70,"date":71,"author":72,"readTime":73,"content":74,"image":75,"postImage":76,"more":77,"extendedContent":78,"asHTML":79,"photoCredit":80,"headTitle":81,"metaDesc":82,"draft":79,"tags":83,"createdAt":86,"updatedAt":87,"uuid":88,"__v":73,"ogImage":89,"relatedTools":90},"6a8a97bfd86c72abadcf1fbd","sdd-might-be-the-answer","SDD Might Be the Answer - Once We Agree What It Means.","Tailor worktable in a contemporary studio.","Thought","thought","2026-08-23T06:33:00.000Z","Michal",3,"Spec-driven development is gaining attention as developers look for a more reliable way to build software with AI. The idea makes sense: describe clearly what should be built before asking AI to build it. I’m on board - but until we agree on what a good specification actually looks like, SDD risks becoming another label everyone uses differently.","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewssdd-full.jpg","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewssdd-sq.jpg","true","AI can produce software remarkably quickly. The slight problem is that “quickly” and “correctly” are not the same thing. Give an AI a vague request and it may confidently build something that looks impressive, works in a demo and quietly ignores half of what you actually needed. Spec-driven development, or SDD, offers a sensible response: decide and describe what should be built before asking AI to build it.  \nThis is hardly a revolutionary concept. Planning before doing the work has generally been considered a decent idea, whether you are building software, a house or a suspiciously complicated piece of flat-pack furniture. What changes with AI is the importance of that plan. When software can be produced in minutes, the quality of the instructions becomes more important than the speed of typing. A good specification gives people and AI a shared understanding of the goal.  \nI’m supportive of SDD, but its critics have valid concerns. Specifications can become bloated, outdated or so detailed that writing them takes longer than solving the original problem. They can also create a false sense of certainty. A beautifully organised document is still useless if it describes the wrong product. SDD does not remove the need for judgement, testing or conversations between people. It simply moves more of the important thinking to the beginning - and hopefully keeps it alive throughout the project.\nThe bigger issue is that SDD currently means different things to different people. One team may write a short description of what users need. Another may produce a small library of documents, rules and checklists. Both call it SDD, while the AI tools supporting them introduce their own formats and processes. If every tool speaks a different language, specifications risk becoming yet another thing teams must translate, rewrite and maintain.  \nThat is why the next step is not another shiny SDD tool. It is a practical, widely accepted standard: clear enough for people to read, structured enough for AI to follow and flexible enough for real projects. Reaching that standard will not be simple, and it should not be dictated by a single vendor. But if the development community can agree on the basics, SDD could become one of the most useful foundations for AI-powered software development. First, though, we may need a specification for the specifications 😉  ","false","Midjourney","SDD Needs a Standard Before It Becomes the Standard","Spec-driven development could make AI-built software more reliable. First, the development community must agree on what good SDD looks like.",[84,85,42,7],"SDD","TDD","Sun Aug 23 2026 14:48:31 GMT+0800 (Singapore Standard Time)","Sat Aug 29 2026 17:29:30 GMT+0800 (Singapore Standard Time)","1c4ed38b-43ee-4569-9e42-9eb862936484","https:\u002F\u002Fmsatbsx.sgp1.digitaloceanspaces.com\u002Fnewssdd.jpg",[91],"ai-visibility",{"totalnoOfPosts":93,"page":93,"perPage":60,"noOfPostOnCurrentPage":93},1,{"enabled":95},true]