- 4 Posts
- 55 Comments
// TODO: Leave the code cleaner than you found
In recent git versions (>2.23),
git restoreandgit restore --stagedare the preferred ways to discard changes in the working tree (git checkout -- .) and staged changes (git reset --) respectively.
15·3 months agoMy point today is that, if we wish to count lines of code, we should not regard them as “lines produced” but as “lines spent”: the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.
——On the cruelty of really teaching computing science - E.W. Djikstra
If you are looking at learning CS in a more holistic manner, there’s Path to a free self-taught education in Computer Science!. It’s a list of courses, categorized by topics, which are exactly what a CS undergraduate would learn. It might feel daunting at first, but you can pick any interesting topic and dive in.
I especially recommend CS50P for beginners.
One problem with exceptions is composability.
You have to rely on good and up-to-date documentation or you have to dig into the source code to figure out what exceptions are possible. For a lot of third party dependencies (which constitute a huge part of modern software), both can be missing.
Error type is a mitigation, but you are free to e.g. panic in Rust if you think the error is unrecoverable.
A third option is to have effect types like Koka, so that all possible exceptions (or effects) can be checked at type level. A similar approach can be observed in practical (read: non-academic) languages like Zig. It remains to be seen whether this style can be adopted by the mainstream.
3·4 months agoBingo!
70·5 months agoWell, that already happened for Reagan and Arnold Schwarzenegger.
Philip K. Dick’s early novella The Gun describes this, but instead of chat bots, they were auto nuclear weapons.
They are also band names.
3·5 months agoAnd he died anyway
Sean k strikes it again.
3·6 months agoYes for OCaml. Haskell’s inequality is defined as
/=(for ≠).<>is usually the Monoidmappendoperator (i.e. generalized binary concatenation).
Let me simplify it: proceeds to print the same expression
Deprecation warnings should contain suggestions for alternatives.
Reminds me of a hilarious bug in early GHC: https://gitlab.haskell.org/ghc/ghc/-/issues/163
The compiler will delete your source file if there’s any compile error. And the user complained only by sending a very polite email to report this bug. Simon Peyton Jones mentioned it in one of his talks and I still find it quite hilarious till this day.