Brainstorm Hub
Where creativity meets words and innovation thrives.
Client-rendered apps often serve bots an empty body. The one-minute test, what AI crawlers actually do, why I skipped llms.txt, and what moving my portfolio to static prerendering took.
The EU rules are live and Canada and the US have dates. A developer-side plan: what the law covers, what to automate for free, and what no tool will catch.
An audit I ran on my own repo found four lists tracking rows by position. A style review would approve that code. Catching that kind of bug is a bigger part of the job now.
A coverage gate can look strict and enforce nothing. AI raises the volume of code, so proving that each check can fail matters more than adding new ones.
How I structured a talk on AI guardrails and enterprise code quality for 47 engineers at BMO, the objections worth preparing for, and the one thing I would do differently. Written from memory and notes, not from a transcript.
Applying Atomic Design literally to an Angular codebase reveals its limits fast. Here is the pragmatic hybrid that actually survives a real project.
After working with micro-frontends on an enterprise Angular project at BMO and evaluating the tradeoffs honestly, here is my verdict on when Module Federation is worth the complexity and when it absolutely is not.
I am building an AI-powered SaaS solo, and I laid the foundation while I was on a demanding contract role at BMO. This is the honest account of the tech decisions, architecture choices, and early mistakes I made.
I started my Godot project knowing nothing about shaders and ended up writing 28 of them. Here is the honest journey from zero shader knowledge to weather effects, destructible environments, and a full day/night cycle.
Angular Material gives you a solid, accessible foundation. The hard part is the token system, the governance, and the component API decisions that keep a design system alive as the product and the team grow.
Building a tactical RPG in Godot taught me more about Angular architecture in about a year than years of reading documentation ever did.
Lazy loading is the single highest-impact performance change I make on every Angular app I work on, and with standalone components it takes minutes per feature route.
A financial dashboard that displays data is not the same as one that supports decisions. Here is how I approach information hierarchy, chart selection, and progressive disclosure in complex financial interfaces.
Building EN/FR bilingual applications in Canada goes far beyond translation. Here are the technical patterns and UX decisions that actually matter when you are building for both official languages.
Building multi-step loan applications taught me that Angular Reactive Forms are far more powerful than most tutorials show. Here are the patterns I use in production financial applications.
After years in startups and consulting firms, joining BMO taught me that enterprise front-end development operates on a completely different set of rules. And some of those rules are actually worth respecting.
An honest assessment of Angular 19 and beyond, filtered through years of enterprise Angular in regulated industries and the SaaS I build solo. What I adopted immediately, what I'm still watching, and what the real tradeoffs are.
From Brazil to a Senior Software Developer (Angular) role at one of Canada's Big Five banks. Here's the practical, unglamorous story of how I built a profile that the Canadian tech market would recognize.
I've spent more than a decade straddling the line between UX/UI design and front-end development, and I want to be honest about both the real advantages and the real frustrations of that position.
Using AI tools inside a Big Five Canadian bank is nothing like using them on a personal project. What the constraints actually are, how to work inside them, and why the tool you run yourself beats the subscription you do not control.
The prompts you write are as important as the code you review. Here's how I engineer AI prompts specifically for Angular to get production-ready output.
An honest breakdown of where AI coding tools genuinely accelerate development and where they fail, based on 12 months of deliberate delegation practice as a senior Angular developer.
How I approach guardrails for an AI coding assistant on an enterprise Angular codebase in a regulated bank: the layers, an illustrative GitHub Copilot instructions file, and the kinds of rules that prevent security and quality issues.
Mobile-first is an information architecture and content prioritization decision long before it is a CSS breakpoint, and designers who treat it as purely a technical concern produce broken experiences on both platforms.
A practical guide to the UX metrics that actually matter, how to instrument designs for measurement, and how to make the business case for UX investment using real numbers from Wonderlabs and Strongest Families, plus one lesson from a BNP Paribas Cardif portal I built as a developer.
Most game developers skip unit tests entirely. I write them obsessively, and here is what 334+ tests in a Godot C# project actually looks like and why it changed how fast I can ship features.
A practical guide to WCAG 2.2 AA compliance covering color contrast, keyboard navigation, ARIA labels, and screen reader testing, from establishing a design system at Strongest Families to shipping accessibility-compliant features at BMO.
What makes a Figma file actually developer-ready. Component naming, auto layout, variants, design tokens, and how my dual role as designer and developer changed how I design for handoff.
Trust, compliance, and error handling as UX pillars in financial products. Lessons from building financial products at GFT, BNP Paribas Cardif, Wonderlabs, and BMO.
A solo developer scaling a tactical RPG to 123+ scripts and 334+ tests needs deliberate architectural choices. Here is the folder structure, patterns, and C# practices I use to keep the codebase manageable.
I have audited a lot of Angular apps and the same gaps appear every time. This is what I fix first, why, and in what order.
Most UX briefs are written for designers reviewing other designers' work. They miss the things developers actually need to build the feature correctly the first time.
NgRx is not a best practice you apply to every Angular app. It is a solution to a specific set of problems, and reaching for it by default is how a small team ends up with a painful, over-engineered quarter.
After months of research and prototyping, I committed to Godot 4 with C# for my tactical RPG. Here is the full reasoning behind the engine and language choice, and what surprised me once I was deep into development.
The gap between a pipeline that runs and one that actually catches problems is enormous. Here is an illustrative Azure Pipelines setup for an Angular app, and what separates gates that matter from gates that get ignored.
French text is 20-30% longer than English, and that alone will break your layouts if you do not design for both languages from day one.
I use AI coding assistants every day in Angular development, but the way I used Copilot Business at BMO was very different from how I use Claude Code on my own projects, and both are different from how I used them when I first started.
The structure I reach for came from failing with two previous structures at GFT and Wonderlabs. Here is what actually holds up as a single Angular application grows past a few dozen features and a handful of developers.
Using throttle on a search input and debounce on a scroll handler are both bugs. Here is how to never confuse them again.
NgModules added a layer of indirection that cost Angular developers years of confusion. Standalone components remove it, and the difference in day-to-day work is significant.
RxJS has 100+ operators. Working in production Angular since 2017, I reach for the same ten, and knowing why each one exists matters more than knowing all of them.
I ran NgRx on a credit card platform with 50,000+ users. The division of responsibility is clear once you stop treating this as an either-or question.
A complete workflow for defining design tokens in Figma Variables, exporting them to CSS custom properties, and consuming them in Angular components with full theming support.
A decision framework for choosing wireframe fidelity, with real examples from fintech and mental health projects showing when lo-fi saves weeks and when it causes expensive rework.
Most teams start a design system by building components. That is the wrong place to start, and getting the order wrong costs months of rework.
The space between 'vanilla Postgres handles it' and 'switch to a distributed system' is bigger than most advice lets on. Here is how to stay in the ecosystem with Citus, TimescaleDB, and the right pooler choices.
I've gone from jQuery and AngularJS to React to Angular and beyond. Here's what I've learned about when to invest in a new technology and what actually transfers across every stack change.
Tools inside Postgres that each replace a small amount of your infrastructure, and which nobody puts in the usual feature tour because they are not dramatic enough to headline a conference talk.
Most 'just use Postgres' posts are right about the features and wrong about the operational reality. Here is the concrete adoption ladder: four tiers, each with the numbers that tell you when to stop.
Most of the "AI agent" presentations circulating right now are repackaging a pattern published by Yao et al. in 2022. The pattern is sound. The hype layered on top is what you should push back on.
Anyone who sells you a vector database as "agent memory" is selling you one layer of a five-layer cake. Here is how I think about the stack, and why pgvector wins for most teams.
Copilot makes you faster at producing code. SonarQube flags the problems Copilot just shipped. Nobody closes the loop. An agent in the middle fixes the gap, and it is the first automation I would build for a small team.
I cut CI test time on my SaaS product's Angular front end to a fraction of what it was by switching from Jest to Vitest, and the migration took one afternoon.
A small team cannot afford to build six agents at once. You get one shot to pick the first automation, and most teams pick wrong. Here is the order I would do it in, and the seductive one I would skip.
If you start each agent as a standalone script, you will have a graveyard of repos by Q3. Here is the Angular + Python + Docker monorepo layout I would use, with a shared base agent that every new agent inherits from.
You do not need Pinecone, Notion API credits, or a Confluence license to give your agents a knowledge base. A markdown folder, pgvector, and an embedding model running inside your own Docker do the job. Zero API, zero key, zero per-request cost.
I implemented Google, Facebook, and Bluesky social login plus magic link passwordless auth in a Flask/Angular side project I am building locally, and the lessons were harder-earned than I expected.
After more than a decade operating across the design-development boundary, here is my honest assessment of the market for hybrid roles, how to build the dual skillset intentionally, and whether it's actually worth it.
Whiteboard interviews test more than problem-solving speed. They evaluate communication, clarity, and approach methodology. Let's break down the Pair Sum problem step by step using the REACTO method.
I stopped writing redundant type definitions after I started actually using the built-in utility types. This is what they look like in real Angular code.
The sliding window pattern covers a whole category of array and string problems. Once it clicks, you stop reinventing the solution and start applying a template.