My favorite framing, from Kent Beck: “first make the change easy, then make the easy change.”
Fix your tools
11–20 of 100 posts
Re: Fix your tools
#12Re: Fix your tools
#13Re: Fix your tools
#14Re: Fix your tools
#15Engineering is a continual lesson in axe-sharpening (if you have 6 hours to chop down a tree, spend the first 4 sharpening your axe). My favorite framing, from Kent Beck: “first make the change easy, then make the easy change.”
Re: Fix your tools
#16Re: Fix your tools
#17OP here, thanks for submitting!
How'd you get the notice that this was submitted so quickly?
Re: Fix your tools
#18OP here, thanks for submitting!
hey, the idea of Krossover is actually dope! my sole question is, why does it exist? I understand that one might call Rust from Kotlin for performance reasons (I do that often, Mozilla does, some others too), but Kotlin from Rust? where would it be useful? no snark or subtext here, I'm genuinely curious
Re: Fix your tools
#19The caveat is that you might end up shaving a yak. More often than not I end up three or four tasks deep while trying to fix a tiny issue. https://m.youtube.com/watch?v=_UZFI-8D5uA
Relevant XKCD: https://xkcd.com/349
Not that you can't get one into a non-working state, that is, of course, trivial but with the lone exception of deleting data, you can always restore a computer, the only tool being needed is some kind of boot disk.
(Compare that to breaking a literal hammer, you'd need a pretty specialized set of tools handy if you wanted to actually restore it)