1. The collaboration and notation app for rock bands that I’d wished existed already: https://bandwith.rocks/about
2. A “runtime scheduler for humans” that I wished existed, too (think morning routines, travel checklists, and pomodoros in the same abstraction—but also a lot of support for ad-hoc rearrangement and addition of the task queue).
I agree that the font and emoji hops aren’t great for complexity or performance, but the problem in the post was in the rendering of a tiny SVG; serving it directly would not have avoided the problem.
Damn, wait: you mean the random HN commenter didn’t magically solve a difficult problem that has long-confounded experts, simply by bringing their unique insights and thirty seconds to bear?
“I’m going to go lay down and, uh, think about the problem with my eyes closed”
Oh good, mainstream coders finally catching up with the productivity of 2010s Clojurists and their “Hammock Driven Development”! (https://m.youtube.com/watch?v=f84n5oFoZBc)
This is an extremely uncharitable interpretation of the text. Objective anchors and examples are provided throughout, and the passage you excerpt is obviously and explicitly meant to reflect that any such list of them will incidentally and essentially be incomplete.
Uncharitable? It's a direct quote. I can agree with the examples cited, but if the underlying guiding philosophy is relativistic, then it is problematic in the long-run when you account for the infinite ways in which the product will be used by humanity.
The underlying guiding philosophy isn’t relativistic, though! It clearly considers some behaviors better than others. What the quoted passage rejects is not “the existence of objectively correct ethics”, but instead “the possibility of unambiguous, comprehensive specification of such an ethics”—or at least, the specification of such within the constraints of such a document.
You’re getting pissed at a product requirements doc for not being enforced by the type system.
reply