hollasch

17 ms·

61.
by hollasch 5y ago
Very cool. I co-edit Peter Shirley's _Ray Tracing in One Weekend_ ( https://raytracing.github.io/ ) and have taken a similar approach, though with a different toolset. At some point if I find the time, I'll write up
62.
by hollasch 5y ago
That would work if all candidates are interchangeable if they assert the same plank. In practice, however, candidates X and Y may both have identical planks but wildly different levels of efficacy. People aren't machines.
63.
by hollasch 5y ago
I highly recommend Bill Hill's _The Magic of Reading_, and excellent document on the art of typesetting and why we have various typographic conventions (hundreds of years old now) and why they work. I had so many profound realization
64.
by hollasch 5y ago
So naturally, my knee-jerk reaction is to create some kind of checklist language and interpreter. Which is almost wrong, of course. I say "almost", because it occurs to me that many steps are shared individually across many differ
65.
by hollasch 5y ago
In my work, we have develop on Linux, MacOS and Windows. Another advantage to this approach is that it allows you not just to incrementally automate steps in the process, but _steps on platform X_. It eliminates yet another barrier to start
66.
by hollasch 5y ago
That would make sense if your intent to was to remain a checklist forever.
67.
by hollasch 5y ago
It addresses the false dichotomy between checklist and full automation. Documentation loves to spawn future copies and variants, while scripts tend to remain single-source.
68.
by hollasch 5y ago
> All the "do-nothing scripts" diverges from the reality as time goes by. Not sure I follow. In my experience, we have _tons_ of process that's written up in random pages in our company wiki. I assure you, nothing diverges
69.
by hollasch 5y ago
I think this would be a great idea if the intent was a checklist that would never be automated. If the idea is to create a scaffold for future incremental automation where tasks start falling off the checklist (until ideally none are left),
70.
by hollasch 5y ago
Not to weigh in on this particular issue, but I think your objection here is another piece of evidence weighing in the favor of this overall approach. It's perfect to have this debate immediately and so early in the process, before any
71.
by hollasch 5y ago
He didn't "refuse to add" them. JSON had comments, and then he removed them.
72.
by hollasch 5y ago
> You're not meant to delete commits like that. Couldn't disagree more. To me, one of the massive advantages of Git over other VCS tools is the support and completeness of its ability to edit time. You are the editor not just o
73.
by hollasch 5y ago
Well, if it's any comfort, history shows that plenty of short poppies get mowed down collaterally in these events. You'll find a wonderful equity in the mass graves.
74.
by hollasch 5y ago
Something that started out as a gate, but now is smoke and a little burnt ember of sadness.
75.
by hollasch 5y ago
> In ideal conditions, where the wind is at its strongest, one wind catcher unit could produce up to 400 gigawatt-hours of energy. By comparison, the largest, most powerful wind turbine on the market right now produces up to 80 gigawatt-
76.
by hollasch 5y ago
That's my approach. Autohotkey plus sequences starting with "qq", like qqdeg (degree), qq>- (right arrow), and so forth.
77.
by hollasch 5y ago
ISPs have shown increasing comfort with delisting sites they deem bad. I'm a huge proponent of commoditizing data hosting, but the culture today leans heavily toward "filtering" information.
78.
by hollasch 5y ago
If you're interested in this, I'd encourage you to look at MarkDeep ( https://casual-effects.com/markdeep/ ). This allows you to write Markdown-style documents, including ASCII-art diagrams, but which render be
79.
by hollasch 5y ago
Yeah, blast from the past. Early days of the web. The image interpolation/extrapolation blew me away, particularly extrapolating away from a blurred image as a way to sharpen.
80.
by hollasch 5y ago
Digital Negatives
81.
by hollasch 5y ago
I use my real name precisely _because_ everything I say is being recorded. It's a guard against the foolish belief that any "anonymity" is real and can be relied on.
82.
by hollasch 6y ago
I became a multi-millionaire by knowing data structures and algorithms.
83.
by hollasch 6y ago
Curious. I have to come to exactly the opposite conclusion — that we should drop the idea of a fixed-length character type, and instead _only_ have (Unicode) string types. Actually, I'd prefer something like `std::text` to finally be f
84.
by hollasch 6y ago
Speaking for myself, two items I often find missing: the overall summary and the rationale. Many times I've gone to a set of documentation wondering what exactly the thing _is_. Let's take the JavaScript language, for example. The
85.
by hollasch 7y ago
Try this one weird trick for a flatter ~belly~ curve!
86.
by hollasch 7y ago
This may be a model to consider: https://github.com/sponsorware/docs Also, this may help you: https://opensource.guide/getting-paid/
87.
by hollasch 7y ago
It's not really a problem of dark vs. light, it's the fact that transparency in a generic logo is a pretty bad idea. I'm not sure what transparency is supposed to solve that an explicitly designed color wouldn't.
88.
by hollasch 7y ago
One of the points of the article is that the environment is a huge factor to productivity. In the environment you talk about (startup program), you have zero code review, full comprehension across the entire system (because you've writ
89.
by hollasch 7y ago
See http://steve.hollasch.net/cgindex/coding/ieeefloat.html for another explanation of the details of IEEE 754.
90.
by hollasch 7y ago
A lot of folks don't appreciate the black & white nature of a DNR. At my mother's group home, the head nurse told me a story of a man who started choking on his breakfast. They were unable to clear his airway, called 911, and

More ›