HNHacker News
TopNewBestAskShowJobs

wduquette

604 karma · joined July 17, 2022

submissionscomments
wduquette··on Ask HN: How Do You Journal?
Leuchtturm 1917 dot grid journal, Uniball Jetstream pen, and a minimalist version of Ryder Carroll's bullet journaling advice. (https://bulletjournal.com)

I like the Leuchtturm journals because they have page numbers and they don't fall apart.

I record todos, appointments, significant events, and detailed notes on anything I'm studying or thinking about in detail. Each successive journal gets a number, so that so I can easily and unequivocally reference any page in any journal.

Knowledge-base-stuff goes in Obsidian.

wduquette··on Write the damn code
Unless you're solving the same old problem for the Nth time for a new customer, you don't really understand the problem fully until you write the code.

If it's a new problem, you need to write the code so that you discover all the peculiar corner cases and understand them.

If it's the (N+M)th time, and you've been using AI to write the code for the last M times, you may find you no longer understand the problem.

Fair warning. Write the damn code.

wduquette··on A shift in developer culture is impacting innovation and creativity
Dunno. I’ve been at this since the late ‘80’s, and have run into precious few developers who were interested in software and programming for its own sake. For most of them it was just a job.
wduquette··on GNU Midnight Commander
I'm sure it has evolved, but Midnight Command began as a recreation of Norton Commander for DOS PCs. I've not used Midnight Commander in particular, but back in my DOS programming days Norton Commander was my best friend.
wduquette··on Famous cognitive psychology experiments that failed to replicate
"they are AWFUL at stats."

SF author Michael Flynn was a process control engineer as his day job; he wrote about how designing statistically valid experiments is incredibly difficult, and the potential for fooling yourself is high, even when you really do know what you are doing and you have nearly perfect control over the measurement setup.

And on top of it you're trying to measure the behavior of people not widgets; and people change their behavior based on the context and what they think you're measuring.

There was a lab set up to do "experimental economics" at Caltech back in the late 80's/early 90's. Trouble is, people make different economic decisions when they are working with play money rather than real money.

wduquette··on We can’t circumvent the work needed to train our minds
Yes. And so's my code, so to speak.
wduquette··on We can’t circumvent the work needed to train our minds
I did not say that my brain uses linguistic representations internally when I think; I said that the process of turning my ideas into words helps me think.
wduquette··on We can’t circumvent the work needed to train our minds
I remember the dotCom bubble. After the bubble burst, people got on with putting storefronts and other kinds of business on-line in a more sober fashion.

I predict the same thing will happen with the current AI tools: the bubble will burst, a bunch of folks will lose their shirts, and the world in general will come to a more realistic and sober understanding of what they are good for. We will figure out how to provide the useful parts without massive data centers and it will become natural. (I remember when things a graphics card can do trivially required a supercomputer with supporting staff.)

wduquette··on We can’t circumvent the work needed to train our minds
But taking notes and writing ideas out requires that we think them through...which we usually don't do otherwise. This has been a commonplace of the intellectual life for centuries.
wduquette··on We can’t circumvent the work needed to train our minds
I arrange my code to follow a certain order, so that I can get my head back into a given module quickly. I don't remember everything; there's too much over the weeks, months, and years. But I can remember enough to find what I need to know if I structure it properly. Not unlike, you know, a Zettlekasten.
wduquette··on We can’t circumvent the work needed to train our minds
In my experience, a lot of the hard thinking gets done in my back-brain while I'm doing other things, and emerges when I take up the problem again. Doing the regular work gives my back-brain time to percolate; doing hard thing after hard thing doesn't.
wduquette··on Building a DOOM-like multiplayer shooter in pure SQL
Not knocking your history, but I gotta say that Wolfenstein-3D was like nothing I'd ever seen...and I played the original Wolfenstein on the Apple II--and the original Wizardry as well, which is a lot more to the point than Rogue IMHO. The Wizardry map grid and the Wolfenstein-3D map grid are really similar, now that I think about it.
wduquette··on Look Out for Bugs
I do what the author does all the time, every day. But then, I work mostly on my own; and I've spent decades learning how to structure my code so as to minimize the amount that has to be "live" in my head at any give moment, and so that I can quickly rebuild that mental model on re-reading.
wduquette··on Blogs used to be different
There were lots of blogs that were personal diaries back in the early days; but there were always many blogs the weren't. The first "web log", in my opinion, was the page at NCSA, home of the Mosaic browser, that was literally a log of new web servers coming on-line. I used to go there daily to see what was new. (Later I used Yahoo for that purpose; and not much later than that I gave up. :-)

Another big site for early blogging was Dave Winer's "Scripting News", in which he talked about Frontier and Radio Userland, two early web platforms. Winer was also responsible for "EditThisPage", the first web site I ever saw that allowed editing a website on another server through the browser. It was followed by Weblogs.com, which hosted some of the earliest blogs. I had one there, briefly.

And then, of course, there was GeoCities, where you explicitly picked your "city" based on the kinds of things you were going to be writing about. Blogging was always extremely hetergeneous.

What we didn't have in the early days was monetization or, naturally, an intense focus on monetization.

wduquette··on Blogs used to be different
I was the first person I knew to learn HTML; that was in the mid-90’s. I had a personal website from December of 1996, where I posted mostly book reviews; later it evolved into a hand-coded blog, followed by MovableType, followed by WordPress, which I still use.
wduquette··on Blogs used to be different
It’s true. I remember the glory days of the “Blogosphere”: the Truth-Laid Bear’s blog ecosystem (I was a finny fish at one point, IIRC), USS Clueless, 2Blowhards, servers going down under the weight of an Instalanche, and many many others. Some are still around; I see posts from Iowahawk once in a while. But it wasn’t all personal diaries. There were pundits, essayists about every topic, diarists; me, I reviewed books. It was a heady time, and great fun.
wduquette··on Action was the best 8-bit programming language
And in fact I eventually went from Apple Pascal to Turbo Pascal on a Kaypro 4 running CP/M-80. It was like coming home.
wduquette··on Action was the best 8-bit programming language
The OP says that 8-bit CPUs couldn't handle Pascal well, and that Action! (release in 1983) was the first IDE for 8-bit machines.

But Apple Pascal was released for the Apple II in 1979. Based on UCSD Pascal, the Apple Pascal system was basically an OS that simply was an IDE; and it worked perfectly well on 8-bit hardware. I had quite a lot of fun with it back in the day.

wduquette··on The forgotten meaning of "jerk"
I was born in the early 60’s, and I don’t recall my elders ever using “jerk” in what the OP calls the original sense. I have always understood it in the “modern” sense.
wduquette··on Show HN: Mathpad – Physical keypad for typing math symbols
I do use an Elgato stream deck for entering Unicode symbols, and I think what's really needed in this space is a cross between a stream deck and the Mathpad: programmable keys with LCD key caps, and some shift keys to increase the number of available symbols. Then it could support configurable symbol sets.
wduquette··on Mill: A better build tool for Java, Scala, and Kotlin
Re: ant, make that two of us.

I use Gradle these days since IntelliJ doesn't work well with ant; but when I want to precisely control how a build is done and produce exactly the build products I want, I use ant. It's stable, it's well-documented, and I never need to guess what it's doing because it's doing what I told it to do.

I like the idea of an opinionated build tool; but I'm not happy with any of the ones I've tried.

wduquette··on Programming Language Theory has a public relations problem
A pet peeve of mine is theory-oriented texts that present code in a specific programming language...replacing the actual syntax with mathematical symbols. This is unhelpful for practitioners.

Another peeve is when authors present algorithm pseudo-code in terms of mathematical symbols, where it isn't at all obvious how to compute the value of the symbols in practice. You've shown that there is an algorithm, but not in a useful way.

I mean, I see the value of mathematical notation; I have a math degree. But still....

wduquette··on Desktop Publishing Tools That Didn't Make It (2022)
The "Sirius microcomputer" pictured as "The Book Machine" is in fact a Victor 9000, as you can see in the picture. The same unit was branded as "Sirius" in Europe and as "Victor 9000" in the U.S.

I spent quite a lot of time with the Victor 9000 in 1983-1985, as my college bought a bunch of them, and I was the student computer lab guy who supported them. It was a fascinating machine with some really cool specs: built-in 800x600 pixel monochrome graphics, redefinable keyboard and character set layouts, built-in serial and parallel ports, high-density floppy drives, and an 8086 processor. It ran CP/M-86 and MS-DOS. Its closest competitor was the original IBM PC, which at that time had low-density floppies, no graphics, no built-in ports, etc.

The downfall of the Victor 9000 was that it pre-dated the rise of the "PC-clone": third-party PCs that could run exactly the same shrink-wrapped software as the IBM PC did. In the CP/M-80 8-bit world, every manufacturer had its own disk formats, screen sizes, and so on, and you had to buy shrink-wrapped software for your own specific hardware, and the Victor-9000 folks assumed that the 16-bit world would work the same way. As a result, they produced a much better machine than the IBM PC...that wasn't fully compatible.

wduquette··on Rules of good writing (2007)
That moment when you want to respond to an 18-year-old comment because the commenter was Wrong On The Internet, except that trying to correct it is even more absurdly futile than usual.
wduquette··on The Writehander
I was reminded of this by the recent post about "the Keyset". I read a review of one of these devices in a magazine ("Interface Age?" Byte?) back in the early days of microcomputers. It was a keyboard replacement that allowed the user to enter any ASCII code using binary chords. It had a button for each finger and eight for the thumb; if I remember correctly, the thumb buttons were effectively rocker switches. Set the four high bits with the thumb switches, enter characters via the four low bits entered with the finger buttons.

Somehow it didn't catch on.

wduquette··on Notes on the History of the Map Tile
I worked on supercomputer algorithms to render planetary terrain data (image plus digital elevation) using tiling back in the early 90’s. I’m not sure where my co-worker got the idea, but it seemed like an obvious thing to do.
wduquette··on Implementing Logic Programming
It’s all about the terms. As soon as rules can create an infinite sequence of new terms for a single relation, e.g. by addition, you’ve got non-termination.
wduquette··on What's a healthy amount of sleep? It differs from one country to another
Rather, I’d say they observe a difference between the populations of the different countries, and ascribe the difference to each country’s culture…which is, yes, a lazy conclusion. It omits climate, biological differences between the populations, and does not dig deeper to consider what it is about each culture that might have an effect on sleep and health (e.g. work-life balance, diet, etc.). It’s an interesting result if true, but it isn’t useful except as a starting point for more research.
wduquette··on Smalltalk, Haskell and Lisp
I learned BASIC with line numbers and GOTO statements when I was 14 or so. There were two fancy control structures: FOR/NEXT loops and functions that could take one argument and return a value based on a simple expression. Later we got ON GOTO and ON GOSUB, which jumped to one of N line numbers given a computed index. I first saw real control structures, functions, and procedures in Pascal, took to them immediately, and never looked back.

None of it felt that difficult or confusing at the time; but then the programs were vastly simpler too.

wduquette··on Not causal chains, but interactions and adaptations
Seems to me that the OP’s discussion presumes that the obvious managerial and institutional root causes have already been dealt with. I think he’s right about latent faults and fault tolerance; but an organization that doesn’t do good unit testing and remove technical debt is going to have lots more overt faults than one that does. Seems to me that a both/and approach is needed.
← PreviousPage 5 of 11Next →