←back to thread

Software Engineering Body of Knowledge (SWEBOK) v4.0 is out [pdf]

(ieeecs-media.computer.org)
180 points beryilma | 1 comments | 21 Oct 24 19:16 UTC | HN request time: 0.202s | source
Show context
ctz ◴[21 Oct 24 20:19 UTC] No.41908126[source]▶

  Runtime errors surface when a program
  runs into an unexpected condition or situation
  such as dividing by zero, memory overflow, or
  addressing a wrong or unauthorized memory
  location or device, or when a program tries to
  perform an illegitimate or unauthorized operation
  or tries to access a library, for example.
  The programs must be thoroughly tested for
  various types of inputs (valid data sets, invalid
  data sets and boundary value data sets) and
  conditions to identify these errors. Once identified,
  runtime errors are easy to fix.
Embarrassing horseshit.
replies(4): >>41908241 #>>41909426 #>>41909473 #>>41910499 #
1. prewett ◴[21 Oct 24 22:57 UTC] No.41909426[source]▶
I suppose, yeah, when I figure out the exact reason why the error occurred, fixing it is often easy. The finding, however, can often take a long time, which leaves me feeling "once you have driven across the continent, finding your desired endpoint is a quick process". "Once constructed, installing the door on your new house is a simple and easy task". Well, sure, if you take out the time-consuming parts, it's quick and easy.

Except for all those runtime errors where the fix required major refactoring, or the problem is in a third party library, the OS, or some other unchangeable component.