Thrall
Joined 14 years ago
Joined 14 years ago
- Home, end, pgup, pgdown
- Delete
- Function keys that are just F-keys, not volume/brightness controls that act as F-keys when you press a 'function' modifier key.
When I'm not using the mouse, I change the focus with the keyboard (In my setup, focus follows mouse only when the mouse moves).
Now, I would miss git's more advanced features if they weren't there, but when I started, I distinctly remember thinking, "For now, I just want to be able to change my code non-destructively, so I can easily revert it if I make mistakes". Git did that, and did it well.
That's the trouble with this article; With the dependence on buying everything in bulk (and somehow using it all up before it goes off), it appears to be more of a fun theoretical calculation than a practical weekly diet.
I believe Newton said, "If I have seen further it is by standing on the shoulders of giants.", not, "I have rediscovered everything in a slightly different way because no-one gave me more than a vague method to go on"
It is no bad thing to have several independent implementations of an algorithm. If there is a problem with one, then the others are likely to show that there is a problem. However, without open source code, all you can do is say, "Mmm, something's wrong somewhere" and write another version. You may end up with several papers that agree and one that doesn't, but you still can't draw any conclusions without looking at the code. Ultimately, you get a situation where everyone has to repeat the same work and see what they get, when what they should be doing is poring over the original soources and discussing which bits could/should have been implemented differently and how that affects the result.
The code is part of the method. If you can't show us the code, don't expect me to believe your 'results'. That is science.
In terms of semantics: "Say I write a book but nobody purchases a copy."
In more meaningful terms: If people do not value your book highly enough to pay you for it, then without the thousands of unauthorized copies, you are an unknown writer languishing in obscurity. With the copies, you have at least started to publicise your name and your message.
It is perhaps part of a larger trend to try and solve UI problems for tablets and phones, then push the solutions back to the desktop, despite the fact the desktop didn't suffer from the problem they attempted to solve.
"used in my example above where we decided that us meant “unsafe string” and s meant “safe string.” They’re both of type string. The compiler won’t help you if you assign one to the other"
Assuming you have the luxury of a language with a good type system (either because it's designed for the task in hand or it's extensible), the compiler can help you, and you would be much better off having unsafe and safe strings as separate types. Then the encode function simply becomes a function of type unsafe -> safe. I believe Michael Snoymann touches on this in his presentation, "Designing Type-Safe Haskell APIs"[1].
I'm not arguing that Joel's method isn't a good idea. However, if you can it's better to leave hints for the compiler, not just the programmers.
[1] https://docs.google.com/presentation/d/1K7smIeqmca-fY8qgQUKr...