Networking Issues is probably Cache Invalidation in Disguise.

Distributed systems.

OP might be suffering from cache misses. (Or maybe hasn't yet learnt about it.)

Human-human interface configuration falls under networking issues. And naming things, now that I think about it.

And occasionally off-by-one issues :(

It's possible your coworkers are the ones dealing with those issues, and you just never notice.

yeah i agree ... many people can write good software, but to make it stick around, you need a good name for it

Tell that to the array out of bounds exception!

Off-by-one errors are real errors. A common mistake rookie developers make (or used to make, anyway) is forgetting that arrays are zero-indexed when creating an array, then seeing the value that should be in array[n-1] when they read array[n].

Another common off-by-one error is double counting: Some accumulators don't do all their processing in the same function, and occasionally one thing will be checked for inclusion twice, causing the accumulator to have one more element than it should.

it's not just zero-based indexing though. i've had situations like these a couple of times: write a for ... of loop to iterate through the elements of an iterable. a lot of the times, there's an unwanted first / last element in the list (that doesn't actually belong there) and i forget to remove it, then end up with garbage data in the result set.

The more you move through the networking stack, the more you start seeing OB1 error potentials.

Many protocols have packet ids starting from (and wrapping back to) 1. Modbus registers start from 1, but stored in memory offset 0.

Packet lengths can either include or exclude the length itself. E.g. packet length 200 in a protocol could either mean the length is followed by 200 bytes of data; or 1 byte containing the length + 199 data; or even 4 bytes length + 196 data (off by four!)

It's a wild world out there.