![cory Profile](https://pbs.twimg.com/profile_images/1830322384408072192/R_QKhqEC_x96.jpg)
cory
@th1nkp0l
Followers
524
Following
87K
Statuses
6K
Math Academy Foundations II - Complete! 56 XP/day avg. 113 days to complete (7 days off for a hurricane and 5 more for Starship IFT-6, otherwise consistent) At this rate, I'm looking at one year for MF I thru M4ML. (I placed about halfway into MF I) MA continues to be amazing. Trust the system! Some thoughts...
12
6
152
@thrillhouse_van Yea, it’s better to take your foot off the gas when you notice performance falling off!
0
0
2
Money is good. It’s a signal and a symbol and a useful scoreboard. Incentives matter. The invisible hand is a superior coordinating force to central planning. Creating wealth is admirable and should be supported, not obstructed. My point is a pragmatic one. Adam Smith is incredible, but truly absorbing that book is a 1/10000 person kinda thing at best. Also if you want a good distillation of Econ, Economics in One Lesson by Hazlitt is awesome and I’d bet it also hit many of Smith’s points. I need to revisit Wealth for Nations though. I only read parts of it in the context of a great podcast series by @EconTalker years ago
2
0
5
@GrowAllYourFood @cremieuxrecueil Firing an employee for their stated opinions is an action of varying degrees of bullshit depending on where the person states them, but it should be legal
1
0
0
The Art of Doing Science and Engineering Richard Hamming Chapter 4: History of Computers – Software Progress The previous generation (of programmers) always resents the ways of the new generation - "anything but writing machine code/assembly is for sissies." This despite the fact that, for example, writing the old way takes more time to debug. New ways, even if improved, are often slow to be taken up by the professionals. Even those who invent or discover something new often don't understand its implications, leaving it up to subsequent generations to make something of it. Adopt new methods, if they work well, before others - then outwork them. Makes me think of the constant Battle of the Programming Languages on x. Just find what works for you and build. Don't get stuck on what's "for sissies". To see the obvious and make progress, it sometimes takes an outsider - or a thoughtful insider - looping these questions: - What am I doing? - Why is this necessary? Philosophy Psychological v Logical programming/design: To what extent is it appropriate to buffer the user from the machine? Is the language easy for the expert only, or also the non-expert? It is likely that non-experts (those with closer connection to the problem/user will do the bulk of programming in the future. (Prescient comment in the age of AI) Is programming closer to novel writing or classical engineering? Novel writing, he says, because given the same prompt, there are often many sufficient solutions. You can/should/do/will define the problem as you solve it. Build with this in mind. But to the greatest extent possible, think before you write to get it right the first time.
0
0
5