2 ms·
Tell me about it, but this is nothing new. I am constantly being asked to make "just a little" change. In most cases, the cost is easy to see, but every now and
by ChrisMarshallNY 5y ago
Tell me about it, but this is nothing new. I am constantly being asked to make "just a little" change. In most cases, the cost is easy to see, but every now and then, I get a sneaky one, like the first example.
This is the biggest issue that I encounter:
> We run in to a complicated bug associated with what we're trying to do - so then we have to deal with the bug to get it done
Very often the "little tweak" executes a line of code that has always had a bug (AKA "Tech Debt"), but was never found, as there was no code path.
That's why code coverage tools are important (but they tend to be hard to find).
A lot of what I write are reusable tools, SDKs and APIs. I tend to write a lot of code paths that will only be of interest to certain clients. It's incumbent upon me to test them all, but I often miss one or two.
- castratikron 5y agoI'm embarrassed to admit that I didn't know about code coverage tools until about Year 10 of my career, mostly embedded C and C++ where things seem to move slowly with regards to adapting modern best practices. There is actually code coverage support built into GCC, called gcov. It works really well for C and C++ projects (and theoretically any language with a GCC frontend?)
- ChrisMarshallNY 5y agoI work in Swift (mostly). I think some tools are starting to coalesce (LLVM helps).