- Lucky strike with missing bytes
How limited hardware led to an
invention causing increased fire detection security
|
- "Correct sign is found experimentally"
Summertime blues: move the
clock spring-ahead and fall-back - so when was half a year since?
|
- Don't reuse that int
100% accurate with an int
then - why not now?
|
- Fail
to error first. Then, fail to safe
Wrappings may hide crucial details
|
- A name should carry the meaning
If you sleep, are you then
not up?
|
- The '2/3'
bug in Dilbert
Don't close your eyes to the
screen's blind spot!
|
- Too_little_else_to_do
Watchdog restart because 'the others' were idle when 'I' was too busy
|
- Asynchronous_io_and_critical_regions
Some easy editing rules to help you off your own toes
|
- ANSI_C_static_vs_malloc
No handle to hold these statics
|
- Mental_grasp_vs_file_size
Does file size matter?
|
- Wishes for a folding editor
More out of token-based folding
|
- Anonymous plug-in of code in ANSI C
Making ready for future code
|
- Wishes for a code tracking system
Line level track-tags
|
- Process_objects
Let them be black
|
- Process_file_fan_out
Functions out there need not destroy black-box encapsulation
|
- Discovering
what's independent
Functional "factoring out" to stop the stream of new errors
|
- Innovating_in_a_window
("winnovating")
Always present '?' is for help, but why isn't '!' also always there?
|
- A scheduler
is not as transparent as I thought
Why CSP-type blocking channel state machines were visible, and how to
make them disappear
|