Post #2675568
2026-04-22 14:56 UTC
@raiderrobert@mastodon.social
Code is good if it is fit for purpose. Without knowing the purpose, one is left to make assumptions about the purpose, and ask if the code is fit to that assumed purpose.
An example of buggy code is a good example only if it has the specific bugs being demonstrated. A candidate busy beaver program is good only if it is in fact very slow.
1/
Replies (1)
-
@david42@mastodon.online 2026-04-22 14:59
@raiderrobert@mastodon.social Different solutions to an algorithmic problem may have different time, space, code size, maintenance complexity, etc. tradeoffs, and be better for different scenarios. A storage system that supports downtime-free upgrades is going to have more complexity than one that requires downtime. Which is better depends on your needs. 2/