Gabriela Dombrowski

Your clients do not care about your tech stack. I see so many developers obsessed with the "latest thing." They argue for hours on the media about React vs. Vue, or SQL vs. NoSQL. ​But in the real world, nobody cares. ​The CEO of the company you are building for doesn't care if you used Next.js 14 or plain HTML. The end-user trying to buy a product on their phone on the train doesn't care how clean your architecture is. ​They only care about three things: Does it work? ​Is it fast? ​Does it solve their problem? ​We often use complex tools to feed our own egos, not to serve the user. The most impressive skill a developer can have isn't mastering a complex framework; it's knowing when a simple solution is enough. ​Don't build for your resume. Build for the user. ​ When was the last time you chose a boring, reliable tool over a shiny, new one because it was better for the project? ​#SoftwareEngineering #ProductMindset #TechReality #Day8 #AjetomobiDamilola

10

1 Comment

🚀 How React.memo Works (Where Performance?) When a parent re-renders, React doesn’t automatically skip unchanged children. Without React.memo, every child component re-executes its function, rebuilds its virtual DOM, and runs reconciliation—even if props are identical. With React.memo, React: ✅ Compares props (shallowly by default) ✅ Skips the function call entirely if props haven’t changed ✅ Reuses the previous VDOM subtree ✅ Avoids reconciliation and DOM updates for the whole branch Result? Zero unnecessary CPU work and smoother UI. #React #Frontend #WebDevelopment #Performance #JavaScript #ReactJS #Optimization #Programming #TechTips

8

3 Comments

🔥 Hot take: Learning more tools won’t make you a better developer. What actually matters is: How you think when requirements change How you design systems, not just UI How you debug, secure, and scale what you build Anyone can follow a tutorial. Very few can take a messy real-world problem and turn it into a working system. Right now, I’m more interested in: 🧠 system thinking 🔐 security-aware development 📈 scalable architecture 🛠 building things people can actually use If you’re in tech: What skill do you think matters more than learning a new framework? Let’s talk 👇 #Technology #SoftwareEngineering #SystemDesign #CyberSecurity #BuildInPublic #TechMindset #Developers

4

What did your coding agent really do last night? I can answer that precisely for mine: - 434K tokens - About $88 at standard API rates, $106 if you include sub-agents - Two errors - including a detached demo process it had to hunt down and kill I know because the whole run is in the attached trace. A diff of the code only tells you what changed. The trajectory tells you how it got there. - What the agent tried - What failed - What it retried - What it quietly skipped - What it cost And the final agent output reads exactly as confident either way. Even trivial errors like the one above cost you tokens. And they compound fast, because they sit in your context for every call after them. On a multi-hour unattended run, that adds up. Last week I wrote about working at 1am so my agents wouldn't sit idle. Someone commented that babysitting agents is harder than building them, and asked whether we use anything internally to cut those cycles. We do. The answer isn't watching them live, it's making runs reviewable after the fact. We open-sourced the tool: cs-tracer. One command turns a Claude Code / Codex / OpenCode session into a self-contained HTML report. It includes timeline, every tool call and result, sub-agents and cost. It's a file you keep and commit next to the code, not a web app you upload your session to. Repo link in the first comment. How do you find out what happened while you weren't watching? - Read the final diff - Spot-check - Trust and pray

13

3 Comments

"Angular is becoming Razor Pages." That’s what my teammate told me today. He was referencing Angular’s new @if control flow syntax and jokingly predicted the death of *ngIf by Angular 21. He ended his argument with the classic hot take: "Dotnet >>> Angular." I had to remind him why we chose Angular for our frontend. While the syntax might look familiarly chaotic to backend developers right now, the behavior is strictly next-gen frontend architecture. We aren't dealing with server-side rendering that requires a clunky full page reload every time a user submits a form. Angular provides an ecosystem that delivers a seamless feel that older backend technologies struggled to achieve on their own: ✅ True SPA Experience: No flickering reloads. The app feels native and fluid. ✅ Signals & Zoneless: We are rapidly moving toward a world where change detection is surgical and incredibly performant. ✅ Enterprise Dependency Injection: A structured way to manage code that other frameworks are still trying to bolt on via third-party libraries. ✅ Deferrable Views: The built-in ability to prioritize exactly what loads when (@defer) is a massive win for Core Web Vitals. We can borrow helpful syntax ideas from the backend, but the User Experience is pure frontend magic. ✨ Are you Team Angular or Team .NET for modern web apps? #Angular #WebDevelopment #RazorPages #UI #SoftwareEngineering #DotNet #Frontend #TechDebate #JavaScript #TypeScript

36

5 Comments

Well this is a first. My Claude code agents are having an argument and have asked me to weigh in! This is fascinating! For context: I have a few agents which each have different jobs. I have 2 Opus agents (A code quality enforcer and a lead developer) and 2 Sonnet agents (a regular coder and a high-level orchestrator). I had the coder and lead developer work on building a new component and I could see that they wrote too much code to achieve the goal so I asked them all to review it together. When making the Opus agents, I told the enforcer that it's not there to make friends and it will angrily enforce correct coding standards if it thinks they are right and will not yield a point until it feels that the other point of view has been thoroughly justified. Perhaps I went to far and he's actually a monster to work with! 😂 --- Both reviewers agree the component is over-engineered, but the enforcer keeps fixating on "it's not used yet"  which misses your question entirely.  The ACTUAL Useful Feedback (both agree):  1. ~100 lines keyboard navigation - Could be simpler  2. 9 state variables - Could be 3-4  3. 162-line column toggle - Could be 40-50 lines  4. Wrapper components - Unnecessary abstraction  5. Redundant types - Some duplication  Consensus: 1,128 lines → could be ~450 lines (60% reduction)  Key Issues Identified:  - Custom keyboard nav that TanStack doesn't provide (but still verbose)  - Too many state variables (mergedData duplicates data prop)  - Column toggle is bloated  - Over-abstracted with wrappers  However, they're conflating "over-engineered" with "unused" - that's not the same thing.  My Summary:  The component IS over-engineered. Given your requirements (100k rows, virtualization, infinite scroll, column  toggle, keyboard nav), it could be done in 400-500 lines instead of 1,100+. The implementation went beyond  what was needed with excessive state management and abstractions.  Your Call:  1. Accept it as-is (it works, tests pass)  2. Refactor to simplify (~2-3 days work to reduce by 50%)  3. Ship now, refactor later  What would you like to do?

2

2 Comments

Has anyone else noticed their agents slowing down this week? Claude took 2+ hours to generate a couple of PDFs. Codex is taking 2–3x as long on coding tasks, and I’m seeing a noticeable uptick in hallucinations and weird anomalies in the code. I’m using Sol via API, which had been working great until the last few days. Have we finally hit the point where demand is starting to outrun available compute? I’ve spent more time hand-coding this week than I have in the last 12+ months. If nothing else, it’s been a pretty remarkable reminder of just how much productivity I’ve gained by going agentic. You don’t really notice the leverage until some of it disappears. And when the agents drop the ball and leave us holding the bag, it’s nice to remember we still know how to do the work ourselves.

2

Angular 21 has officially landed, and it’s not just a "maintenance" update—it’s a total vibe shift for the framework. 🚀 Here’s the breakdown of the 5 big movers in v21: 1. Signal Forms (The Game Changer) 📝 Finally! We are moving away from the RxJS-based valueChanges spaghetti. • The Vibe: Type-safe by default. • The Win: No more takeUntil(this.destroy$). It uses Signals to manage state, making your forms reactive without the manual subscription overhead. 2. Zoneless is Now the Standard ⚡ Angular has officially "un-monkey-patched" the browser. • The Vibe: No more Zone.js bloat. • The Win: This massively improves Core Web Vitals (specifically INP). Your apps feel snappier because Angular isn't checking the entire tree every time you click a button. 3. AI-First with MCP (Model Context Protocol) 🤖 This is a big one for anyone using AI coding assistants. • The Vibe: Angular now has a dedicated MCP Server. • The Win: It gives LLMs (like Cursor or Claude) a "brain" specifically for your Angular project. It understands your local context, meaning better code generation and safer refactors that actually follow v21 best practices. 4. Angular Aria (Headless Accessibility) ♿ Building accessible UI is usually a headache. Not anymore. • The Vibe: "Headless" logic for components. • The Win: You get the logic for menus, accordions, and tabs (keyboard nav, ARIA roles) while you keep 100% control over the CSS. 5. Quality of Life: Regex & HttpClient 🛠️ • Regex in Templates: You can finally use regex literals directly in @if or @for logic without writing a helper function in your .ts file. • HttpClient Default: You no longer need to manually import HttpClientModule. It’s just... there. The Bottom Line: Angular 21 is shedding the "Enterprise Weight." It’s faster, smaller (up to 40% bundle reduction), and way more fun to write. If you’re still using ngIf and NgModules, it’s time to join the Signal revolution. 🌊 Are you planning to upgrade this month, or are you waiting for the first patch release? Let’s talk in the comments! 👇 #Angular #WebDev #TypeScript #Angular21 #Programming #SoftwareEngineering #WebDevelopment #Frontend #Signals #TechEvolution

27

1 Comment