Software Development on Coderrob

Trust but Verify: The Math of Rigorous Software Development

Fri, 10 Apr 2026 10:00:00 -0500

Between Satire and Ridicule

It started, as these things often do, with a comparison nobody asked for.

I made a post saying that, with AI-assisted workflows, I can contribute anywhere from 20 to 300,000 lines of change in a day.

That number was not meant to say, “Look at me, I make ALL the tokens go brrrrrrrt…”

It was me counting additions plus deletions across real work: feature creation, refactoring, documentation, automation, test updates, generated assets, project scaffolding, cleanup, and the supporting files needed to make the work sustainable.

Rethinking Enterprise Software Development: Embracing Automation Over Outdated Hierarchies

Sat, 22 Feb 2025 17:04:43 -0600

For too long, legacy enterprise development has been constrained by a top-down model that stifles innovation and impedes progress. The conventional emphasis on individual developers paired with rigid managerial oversight is not only inefficient; it is counterproductive in today’s fast-paced, ever-evolving tech landscape.

Drawing from my experience building automated code-review agents for enterprise applications, I have witnessed firsthand that current corporate development structures are fundamentally flawed. Rather than investing in isolated training programs or centralizing AI initiatives within a single division, the future lies in leveraging automation to transform enterprise software development into an agile, collaborative, and efficient process.

Unit Testing: Rules and Best Practices

Fri, 21 Feb 2025 22:37:19 -0600

Rules to Follow

FIRST Principles

Fast – Tests should run quickly to allow frequent execution.
Independent – Tests must not depend on each other.
Repeatable – A test should always yield the same result.
Self-Checking – Tests should automatically verify correctness.
Timely – Write tests before or alongside implementation.

Coverage & Quality

Target 85%+ meaningful test coverage, prioritizing critical paths.
Cover happy paths, edge cases, and failure scenarios.
Async tests should be properly awaited or return promises.
Mock dependencies to isolate the unit under test.
Ensure all branches and conditions are tested.

Self-Describing Tests

Descriptive Naming – it('should return X when Y happens').
Truth Tables (it.each) – Cover multiple cases in one statement.
Mock Naming Convention – Differentiate real and mock objects.
describe Blocks – Group related tests logically.
Named Constants – Avoid magic values in test cases.

SEE Pattern (made this one up)

Setup – Initialize inputs and dependencies.
Execute – Run the function under test.
Expect – Assert the expected outcome.

NOTE: I call it “SEE” because you see immediately what it did or didn’t do.

Breaking Up the Big Bottom Library: Streamlining Your Code for Long-Term Health

Wed, 11 Sep 2024 21:58:05 -0500

Over time, code libraries have a habit of expanding like that one “utility” drawer in your kitchen. At first, it’s helpful—everything in its right place, ready for use. But before long, that drawer becomes a catch-all for every stray function, random helper, and one-off module you couldn’t quite categorize. Eventually, it’s too bloated to find anything efficiently.

When that happens, it’s time to consider not just a cleanup, but a deeper restructuring. Because left unchecked, your code library could evolve into something far more dangerous—a monolith.

Not all dots are created equal... especially in your Gmail address

Tue, 03 Sep 2024 21:26:01 -0500

Here’s a quick heads-up that might save you some serious headaches.

Gmail doesn’t treat dots in email addresses as unique. Whether your address is john.smith@gmail.com or jo.hn.smith@gmail.com, if it has a dot a copy of ALL your email gets sent to johnsmith@gmail.com too.

A very close family member learned this the hard way when their identity was stolen. Someone registered a non-dotted version of their email, and it went unnoticed for a while. The result? Credit card fraud…

Clean Up Your Conditionals: Refactoring If-Else with Switch Statements

Sun, 18 Aug 2024 13:17:48 -0500

If you’re like me, you’ve probably dealt with your fair share of long, messy deeply nested if-else chains. They can get out of hand pretty fast, right?

One minute you’re making a simple decision, the next you’re wading through a maze of conditions and deeply nested logic. But guess what?

There’s a trick that can help clean this up: using switch and switch(true).

In this post, we’ll take a closer look at how you can use switch statements to break free from the chaos and make your code more readable, more maintainable, and without overloading to your brain juggling the contextual outcomes of each branching statement.

Technology Choice Matters

Thu, 25 Aug 2022 11:34:00 -0500

Developers need consistency in the tools they use, as well as a clear understanding of what is expected of them to be productive and successful in their roles. These tools not only impact productivity but also play a pivotal role in shaping the professional and personal well-being of developers.

As team sizes grow, restructures occur, or new team members are added, it becomes crucial to have a consistent set of tools and technologies that everyone is expected to use.

Contributing to the .NET Runtime

Fri, 16 Apr 2021 18:25:55 -0500

My First .Net Contribution

Today a feature enhancement I proposed and implemented was merged into the .Net runtime main branch for .Net 6 release!

The Background

At the time I was working for a company called, WatchGuard Video. WatchGuard built body cameras and the evidence management software for them. I was hired originally to come in to help launch Evidence Library.

The site, when I started, was several independent SPA sites in a mono-repository. Myself and the other engineers were working on upgrading ASP.Net Framework to .Net Core. One of the biggest concerns, beyond authentication, was configuration.

Being a Programmer

Wed, 30 Oct 2013 21:00:00 -0500

What does that even mean?

I love creating something that didn’t exist before, and then ‘bam’—it’s a thing that others can use. It’s thrilling if it’s something people need to use, and the best feeling by far if it’s something someone genuinely wants to use.

At least until someone turns the power off. Then it all becomes a tiny magnetic dance frozen in place or microscopic scratches on a disk. It’s peculiar to think of software as both existing and not existing simultaneously.