Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Christie Cosky
Stoppability in Code Design
The Small Change That Isn't You've been asked to add a new refund status: NO_REFUND_REQUIRED. When it's set, no money should be returned to the customer. It sounds like a small change. You start where the status is set. You search for Refund.setStatus() and find one call site. The value comes from the front end, and it's saved correctly. That part is straightforward. Then the next question shows up: Where is this status actually used? You search for Refund.getStatus(). Twelve results.
Why Some Codebases Are Hard to Understand: Cognitive Surface Area and the Hidden Cost of System Navigation
Information Foraging: How Developers Navigate Systems Developers rarely read code from top to bottom. They navigate it. When debugging or extending a system, developers follow cues that suggest where relevant behavior might live, such as: Directory structure and package names Class names Method names Enums and constant values Each cue helps answer a constant question during exploration: "Where should I look next?" This behavior resembles patterns studied in human-computer interaction research.
Why AI Makes Readability More Important, Not Less
Software development has always had an asymmetry: code can be written faster than it can be understood. Code is written once but read repeatedly during reviews, debugging sessions, refactors, and production incidents. The real constraint has always been understanding code rather than typing it. AI dramatically widens that asymmetry. Tools like GitHub Copilot and Claude Code can generate thousands of lines of code in minutes, but the speed at which humans understand code hasn't changed.
Code Got Cheaper. Our Rituals Didn’t Notice.
Much of the modern software development lifecycle was built around code being expensive and hard to change. So we built ceremonies, rituals, and whole philosophies around deciding what to build before anyone built it. We planned every story long before an engineer started writing any code. Product managers would curate an extensive backlog of work just waiting for engineering resources. Designers would build mockups because doing so was so much quicker than implementation.
Why the Single Responsibility Principle Protects Working Memory
In my previous article, Mystery Meat vs. Breadcrumb Systems, I argued that organizing code by feature reduces unnecessary exploration. Feature-based packages make it easier to navigate to the right place in the system. But navigation alone doesn't produce comprehension. You can open service.pricing immediately and still have no idea what you're looking at. Finding the file only solves the location problem. Understanding it requires something else.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Christie
Contact Christie, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack