๐ฃ๐ผ๐๐ ๐ฑ The Cake SDK advantage (November 2025):
Single-file executables, smooth .NET ecosystem integration, leverages .NET 10's file-based applications. Full Visual Studio Code support out of the box.
Listen: dotnetcore.show/season-8/fro...
๐ฃ๐ผ๐๐ ๐ฐ Platform abstractions handle complexity:
Cake handles file path differences between Windows and Linux. Forward slash versus backslash? Handled. Environment variable separators? Handled.
Write once, run anywhere. Heavy lifting for cross-platform compatibility done for you.
๐ฃ๐ผ๐๐ ๐ฏ The debugging advantage that changes everything:
Unlike YAML pipelines requiring push-to-runner cycles to identify issues, Cake allows loading scripts into Visual Studio or Code, setting breakpoints, stepping through the build process locally.
Test everything locally before pushing.
๐ฃ๐ผ๐๐ ๐ฎ What Cake actually does:
Doesn't replace MSBuild, .NET CLI, or CI/CD systems. It orchestrates them, simplifying complex workflows.
Write workflows in C# instead of YAML, PowerShell, or Bash. Cross-platform. Works identically on Mac, Windows, Linux, or in containers.
๐ฃ๐ผ๐๐ ๐ญ New episode: Mattias Karlsson on Cake Buildโescaping YAML chaos for C# clarity ๐ฏ
Cake (C# Make) is a build orchestration framework offering an alternative to traditional YAML-based pipelines. Strongly-typed C# for build definition provides clarity and debuggability ๐งต
You've no excuse. Install the updates, restart the app, and be cool to one another.
๐ฃ๐ผ๐๐ ๐ฑ Backend validation is non-negotiable:
Anyone can bypass front-end JavaScript with tools like Burp Suite or ZAP. Front-end security measures are valuable but never sufficient.
All data must be validated and sanitised server-side.
Full exploration: rjj-software.co.uk/blog/continu...
๐ฃ๐ผ๐๐ ๐ฐ User-friendly security matters:
Allow password pasting. Seriously. Blocking password managers forces users toward shorter, less complex passwords, making accounts less secure.
Security measures shouldn't burden users or force them into insecure behaviours.
๐ฃ๐ผ๐๐ ๐ฏ Buy, borrow, buildโin that order:
Leveraging well-established, security-audited systems is more efficient and often safer than building in-house. Pre-built systems and framework features generally have more security attention.
Consider long-term security implications.
๐ฃ๐ผ๐๐ ๐ฎ Make the secure path the path of least resistance:
"When we make the path of least resistance the secure path, everyone wins." Secure defaults. Streamlined secure coding practices within frameworks. Pre-selected secure options.
Developers instinctively take the quickest route.
๐ฃ๐ผ๐๐ ๐ญ Security isn't just a nice-to-have; it's a fundamental pillar of software development ๐ฏ
After re-reading Tanya Janca's "Alice & Bob Learn Secure Coding," I'm reminded why building a culture of security from the ground up matters for every tech organisation ๐งต
๐ฃ๐ผ๐๐ ๐ฑ The organisations that thrive use AI to build more capable, more confident, more thoughtful engineers who happen to be more productive.
That's amplification worth aiming for. Understanding, judgment, and accountability remain distinctly human.
๐ฃ๐ผ๐๐ ๐ฐ What to measure instead:
Code review feedback patterns on AI-assisted PRs. Maintenance burden six months after shipping. Engineer growth trajectories. Knowledge distribution across teams. Technical debt trends.
These tell you if you're building capability or dependency.
๐ฃ๐ผ๐๐ ๐ฏ What actually matters:
Are engineers developing new skills and deeper understanding, or becoming more dependent over time? Can they handle increasingly complex tasks independently? Is knowledge spreading across the team? Is technical debt manageable?
๐ฃ๐ผ๐๐ ๐ฎ The temptation with AI tools: measure output. Lines of code written. Features shipped. Velocity increased. These are easy to quantify and look impressive on dashboards.
But they miss the point entirely. Output without understanding is technical debt waiting to happen.
๐ฃ๐ผ๐๐ ๐ญ Saturday reflection: measure capability growth, not just velocity.
From Part 2 of the AI Amplification Paradox: "The question shouldn't be 'are we shipping faster?' It should be 'are we building more capable engineers who happen to ship faster?'" ๐งต
My mood right now, as supplied by a song by my friend Jim:
www.youtube.com/watch?v=oDh4...
๐ฃ๐ผ๐๐ ๐ฑ:
This model demonstrates how small businesses can have outsized impact on regional talent development through sustained commitment to sharing expertise.
Students don't need to look beyond the region for world-class opportunities.
Read: members.wnychamber.co.uk/magazine/win...
๐ฃ๐ผ๐๐ ๐ฐ:
The impact: Students learn teamwork, problem-solving, and communication skills alongside technical capabilities.
They see what innovative work looks like in practice, not just theory. They realise innovative, internationally-recognised work happens in Yorkshire.
๐ฃ๐ผ๐๐ ๐ฏ:
Our solution: Since 2022, sustained partnerships with Yorkshire colleges. Not one-off careers talks, but ongoing collaboration providing placements and delivering sessions on technologies colleges cannot cover.
Students gain hands-on experience with industry-standard tools.
๐ฃ๐ผ๐๐ ๐ฎ:
The challenge: Traditional education struggles to keep pace with rapid technological advancement. AI tools and modern development practices can't find space in curricula. Students graduate with knowledge gaps that employers must fill.
This costs the region talent.
๐ฃ๐ผ๐๐ ๐ญ:
Keeping Yorkshire's tech talent local whilst providing global-standard education.
Featured in the Winter 2026 West and North Yorkshire Chamber of Commerce magazine: how educational partnerships address a critical challenge for Yorkshire's economy ๐งต
๐ฃ๐ผ๐๐ ๐ฑ Key insight: organisations that thrive won't be those generating the most AI-assisted code. They'll be those using AI to build more capable engineers who happen to be more productive.
Listen: dotnetcore.show/season-8/the...
Read: rjj-software.co.uk/blog/the-ai-...
๐ฃ๐ผ๐๐ ๐ฐ AI Amplification Paradox Part 2:
Practical frameworks for ensuring AI amplifies capability rather than erodes it. Warning signs of over-reliance versus productive use patterns. Four-level verification framework. Creating psychological safety around AI usage.
๐ฃ๐ผ๐๐ ๐ฏ The philosophy: fix paper cuts that make developers pause and search for solutions. Small frustrations don't break systems but drain productivity. Systematic removal compounds into significant developer experience improvements.
STS extended to 24 months now.
๐ฃ๐ผ๐๐ ๐ฎ .NET 10 with Mark J Price:
Microsoft's systematic approach to removing developer friction. Extension members (15 years in development), file-based apps eliminating project files, automatic model validation via source generators, WebApplicationFactory improvements.
๐ฃ๐ผ๐๐ ๐ญ Weekend learning: .NET 10's developer experience improvements and building AIresponsible teams ๐ฏ
This week covered both technical advances and frameworks for using AI tools responsibly in engineering organisations. Two pieces worth your time ๐งต
S08E14 - From YAML Chaos to C# Clarity: Mattias Karlsson on Cake Build
We interview Mattias Karlsson about Cake, a powerful C# build orchestration framework for .NET. Mattias discusses the frustrations of YAML-based CI/CD pipelines, how Cake simplifies builds, and the incredible benefit of being
Full framework: rjj-software.co.uk/blog/the-ai-...
๐ฃ๐ผ๐๐ ๐ฑ Level 4: What could go wrong?
Security implications? Performance at scale? What happens when assumptions are violated? System interaction?
This is expert-level verification requiring deep contextual understanding.
AI can't reliably perform this analysis.
