Troels

@suetanvil@freeradical.zone A lot of those examples were all about refusing to solve the difficult problem and realising you could get away with it, however. Forth and Unix in particular. Even today, Forth tends towards radical iconoclasm.

@giuseppebilotta@fediscience.org I think that measure is normally just called "throughput". I teach it as the counterpart to "latency" in my systems course. I am also happy I am not the only one uncomfortable with using memory bandwidth or FLOP/s as the main measure of performance.

@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.

@giuseppebilotta@fediscience.org Teaching situations (especially at university level) are all about identifying common patterns, and then this is no problem. I merely dislike the social dynamics that occur when only the person who has studied the most abstract mathematics knows what is *actually* going on, because my experience is that the observations are not very useful to solving the problem at hand.

I don't mind recasting some programming problem in a more abstract setting, but call it a "model" or a "generalisation", or maybe say "this is an instance of...".

@oblomov@sociale.network they are just hedgehogs, you can find them in nature, I'm told.

@oblomov@sociale.network this happens to any hedgehog moving at sufficient velocity relative to the observer.

@argv_minus_one@mastodon.sdf.org I'm a bit of a hypocrite because I don't disable autocorrect on my own phone either.

@dj2@mastodon.gamedev.place It turned out to be a known issue: https://github.com/gfx-rs/wgpu/issues/5786