Post #2235306
2026-02-01 19:03 UTC
@athas@freeradical.zone @suetanvil@freeradical.zone "refusing to solve the difficult problem and realising you can get away with it" is exactly what software engineering is about. a lot of "difficult problems" turn out to be seventeen simple problems in a trenchcoat, and you only need to solve the one that applies to you; conversely, sometimes *over*generalising a difficult problem turns it into a simpler one - there's a couple of examples of that in Thinking Forth
the point isn't to shy away from the difficult problem, but not to take it at face value - to prod at it until you're absolutely certain you need to solve exactly all of it.
Replies (1)
-
@athas@freeradical.zone 2026-02-01 20:25
@millihertz@oldbytes.space @suetanvil@freeradical.zone I think the main lesson is to say "no, that problem is not worth solving 'properly'". Especially if the cost of solving it is high. That doesn't require computer genius; it mostly requires stubbornness and ego. Saying no to features is hard.