Knowing when you've tested enough depends on whether you can see the edges of your input space.
Most library maintainers have no way to test against their dependents before releasing.
AI agents can generate code 100x faster, but for companies stuck in the "Unhappy Middle" — with legacy debt, bespoke frameworks, and zero slack — the bottleneck has shifted from writing code to verifying it. Here's how engineering leaders can cross the chasm by becoming gardeners, not janitors.
just testing
After a mere ten years of writing code professionally, I have finally attempted to start a project by writing out tests for its core functionality first. Apparently this is a whole thing. Who knew? I tend to fall into the Grug school of thought on testing. A lot of the time I don't think it's super worthwhile to start writing tests before I really understand the problem space of a project, especially since historically I've switched frameworks and tools so often that the first few weeks of work
The history of color bars, the most common television test pattern out there, and what they actually do. (Also, Netflix has some weird test programming.)
P2P systems are not always easy to test. Due to their nature, there's a lot of constraints and network scenarios that might happen. Testground can help!
I set up a CI/CD pipeline to test my website for markup and rendering issues. It proved to be so useful that I can not imagine going back.
During the last weeks, I’ve been writing a lot of code while commuting. Since I was working on an application that uses Facebook’s and Amazon’s APIs and I was working offline, I often found myself una...