4 ms·
C’mon man! A blog post just to link to a twitter thread? Should be the other way around ;p For those like me, averse to twitter threads, a more readable form.
by 40four 6y ago
C’mon man! A blog post just to link to a twitter thread? Should be the other way around ;p
For those like me, averse to twitter threads, a more readable form.
https://threadreaderapp.com/thread/1274859897826488322.html?refreshed=yes https://threadreaderapp.com/thread/1274859897826488322.html?...
I’ll get over it. I am interested in the concepts, it’s something I’d like to think more about.
When/ what areas do prescriptions (or recipes, programs, protocols, and what have you) prove to be useful and successful, and where do they break down?
- gbasin 6y agoSorry, it wasn't my intention. Typically I think out loud on Twitter, and then try to summarize it succinctly in a blog post
- 40four 6y agoJust messing around, couldn’t help myself. I’ve ranted in the past about this, and had folks tell me they prefer a Twitter thread. So there’s that, and once I learned about thread reader, my life was changed! I’ll check the podcast out!
- gbasin 6y agoIndeed. Thanks for posting the link!
- sqrt17 6y ago> summarize it succinctly in a blog post as far as I can tell, that part was a failure. There's no content in the blog post.
- gbasin 6y agoPrescriptions seem to work well in "static" systems. The ones that don't involve competition or comparison with other humans. Single player games, basically. Fixing a car. Building a house. Open heart surgery.
- AstralStorm 6y agoThere are no static systems. Every prescription or practice should come with a use-by date. Otherwise some hapless new guy will take outdated practice for good money. It is also why people straight out of school are not that great unless they learn on their own - they generally know outdated practices. Instead of prescription, a guideline is better, especially a clear statement of goals to strive for. Examples or exact methods are secondary. Even something as bound to physics as say civil engineering changes all the time. New materials, new analysis tools, methods to save cost... Imagine trying to follow a few year old guides on programming practices. Even one year old stackoverflow post can be hopelessly outdated, not to mention low quality. I've hit current linters recommending old, now wrong practice. (Java: replacing concatenation with format strings or string builder. Concatenation used to be slow before Java 1.7, now it's fastest.)