HNHacker News
TopNewBestAskShowJobs

wduquette

604 karma · joined July 17, 2022

submissionscomments
wduquette··on Choosing a language based on its syntax?
I don't have any real problem with words that are reserved absolutely and words that are reserved just in particular places. My point was more that in Algol-derived languages control structures look like control structures. And even in languages that implement `map()` and other higher-order functions, you can tell that it's a method/function call and that these things are being passed to it and those other things are not without going and looking up what `map()` does.
wduquette··on Choosing a language based on its syntax?
Semantics are where the rubber meets the road, certainly; but syntax determines how readable the code is for someone meeting it the first time.

Contrast an Algol-descendant like C, Pascal, Java, or even Python with a pure functional language like Haskell. In the former, control structure names are reserved words and control structures have a distinct syntax. In the latter, if you see `foo` in the body of a function definition you have no idea if it's a simple computation or some sophisticated and complex control structure just from what it looks like. The former provides more clues, which makes it easier to decipher at a glance. (Not knocking Haskell, here; it's an interesting language. But it's absolutely more challenging to read.)

To put it another way, syntax is the notation you use to think. Consider standard math notation. I could define my own idiosyncratic notation for standard algebra and calculus, and there might even be a worthwhile reason for me to do that. But newcomers are going to find it much harder to engage with my work.

wduquette··on Show HN: I wrote a technical history book on Lisp
Sounds very cool. I've dabbled with Lisp on and off since the mid-80's, starting with a text adventure in LISP-80 on a Kaypro 4, and though I've never written a serious project in Lisp I've learned a great deal from it. (Wrote a lot of TCL code once upon a time; I've always thought of TCL as a Lisp in which you do a lot of things backwards.)
wduquette··on A Programmer's Loss of Identity
I'm on a similar arc to the OP, except that it looks like I started about rather earlier, in the late 70's. My job title is "software engineer"; but I long ago chose to regard myself as not so much an engineer but as a master craftsman, similar to a highly skilled cabinet maker (I'm talking high-end hand-built heirloom cabinetry, here, not a quick kitchen remodel). I take pride in every facet of my work, and like the OP try to be always learning new and better techniques.

By that metaphor, AI-controlled code-generation is more like large-scale automated manufacturing: the sort of thing that produces Ikea flat packs. I'm not knocking that; I own my share of Billy bookcases. But it's not what I do. It's not what I'm going to do in the future. There's a place for large-scale manufacturing and there's a place for hand-crafting, and this is even more true for software than it is for physical goods.

Final note: throughout my career I've know a few people with an outlook similar to mine. I'm always delighted to run into them, but they've never been common.

wduquette··on Never Work with Bad People
Many years ago I was fortunate to hear management consultant Peter Drucker give a talk aimed at budding management consultants. At one point he said, "Never work for someone you do not respect." The crowd laughed. He said, in a stern voice, "You laugh. You are wrong to do so." And went on to explain that he had only twice worked for clients he did not respect, and had regretted it bitterly each time.
wduquette··on Nobody knows how the whole system works
It's certainly the case that I don't always know how the layer below works, i.e., how the compiled code executes in detail. But I have a mental model that's good enough that I can use the compiler, and I trust that the compiler authors know what they are doing and that the result is well-tested. Over forty years and a slew of different languages I've found that to be an excellent bet.

But I understand how my code works. There's a huge difference between not understanding the layer below and not understanding the layer that I am responsible for.

wduquette··on Systems Thinking
Grady Booch said that any large system that works is invariably found to have evolved from a smaller system that worked. I've seen this cited as Gall's Law, from John Gall's 2012 book Systemantics, but I read it in a book by Booch back in the late 80's/early 90's. At that time the "waterfall model" was the conventional wisdom: to the extent possible, gather all the requirements, then do all the design, then do all the coding, then do all the testing, doing the minimum of rework at each step.

It didn't work, even for the "large" systems of that time: and Booch had worked on more than a few. The kind of "system" the OP is describing is vastly larger, and vastly more complex. Even if you could successfully apply the waterfall model to a system built over two or three years, you certainly can't for a system of systems built over 50 years: the needs of the enterprise are evolving, the software environment is evolving, the hardware platform is evolving.

What you can do, if you're willing to pay for it, is ruthlessly attack technical debt across your system of systems as a disciplined, on-going activity. Good luck with that.

wduquette··on 1 kilobyte is precisely 1000 bytes?
Memory has always been measured in binary units. Storage vendors have always measured capacity in decimal units, going back at least to the 80 MB (!) hard drive I paid about $800 for back in the late '80s. It was the first time I ran into a megabyte of storage as 1 million bytes, and gosh I felt cheated.

As a programmer, I think in the binary units.

wduquette··on The Universal Pattern Popping Up in Math, Physics and Biology (2013)
The article has a graphic contrasting a "Random" distribution vs. a "Universal" distribution vs. a "Periodic" distribution. I'm guessing the "Random" distribution is actually a Poisson distribution, as that arises naturally in several cases.

But the big question is, does this "Universal" distribution match up to any well known probability distribution? Or could it be described by a relatively simple probability distribution function?

wduquette··on Beowulf's opening "What" is no interjection (2013)
It's a whole lot of fun.
wduquette··on Crafting Interpreters
Simply my favorite programming text of all time.
wduquette··on Crafting Interpreters
Been there, did that, very much enjoy the result.
wduquette··on Games Workshop bans staff from using AI
I took him to mean "deep" in the sense of "strongly felt", not as a comment on how sensible or well-informed the opinion is.
wduquette··on Cold-blooded software (2023)
“Cold-blooded software” concisely expresses something I’ve thought about for years. Modern software based on HTML/CSS and frameworks works great so long as maintenance is ongoing. But for software I write for myself, I much prefer cold-blooded software. I want to write it today and have it still work in five years, even if I haven’t done any maintenance. Professionally I work in an area with similar needs. Gonna be adding this term to my vocabulary.
wduquette··on You can't design software you don't work on
You’re speaking of implementing yet another system of a familiar kind, I.e. a new project. The OP says that generic design works for new projects. He’s mostly talking about designing new features to be added to an existing system, in which case the design has to be contingent on the existing system.
wduquette··on Are the Three Musketeers allergic to muskets? (2014)
Fans might also look at Steven Brust's fantasy Dumas pastiches, especially The Phoenix Guards, set in the same world as his Vlad Taltos novels. Truly a hoot.
wduquette··on Are the Three Musketeers allergic to muskets? (2014)
No; muskets were a battlefield weapon, and little of the book takes place on the battlefield. You wouldn’t carry them around Paris.
wduquette··on Programming peaked
And in fact, professionally, I still live in the good old days. I code in Java 21, I minimize dependencies, and I use an IDE that can do the heavy lifting when I want to refactor something…which is often. I produce a .jar that gets installed with a loader script rather than in the cloud. And it all works, and it’s *stable*.
wduquette··on XY Problem
This is something I have known (but not by this name) since the early 90’s. A proposed feature a customer brings to you is almost never what they need. You must iterate with them to discover their real problem and move on from there.

I left a project once because the sponsor wasn’t letting us interact with the real customer to find the real need. That path only leads to doom and despair.

wduquette··on Atlas Shrugged (2024)
The rubber rollers were degrading on mine, or I’d have done something similar.
wduquette··on Atlas Shrugged (2024)
I watched this happen from the outside. I bought a Laserjet IV when it was first released; by the time it started to fail, many years later, USB had killed the older printer interfaces. It was a workhorse. I wouldn’t even look at an HP printer today.
wduquette··on Racket v9.0
The tooling.
wduquette··on Racket v9.0
I first experimented with Lisp back in the mid-80’s, and have returned to it time and again—not as a language for serious projects, but just as a way of learning new techniques and new ways to think about writing software. I’ve tried using Racket on a number of occasions going back to way before it was called that, and something about the software just puts me off. Perhaps I could get past that if I stuck with it, but I just can’t see myself writing a large project using Racket.
wduquette··on What Killed Perl?
What killed Perl for me was readability, long before Perl 6/Raku. I was an Awk programmer from way back, so took to Perl quickly once it was available. Then in the late 90's I wrote a utility program in Perl that generated some nice HTML documentation for me from some kind of input format I no longer recall.

A year later I tried to use that script on another project, but had to make some changes; and couldn't make heads or tails of it. Shortly thereafter I had occasion to look at some Tcl/Tk I'd written at about the same time...and it made perfect sense to me.

Had I used Perl on a daily basis, rather than occasionally, I might have stuck with it. Instead I switched to Tcl/Tk, and never regretted it.

wduquette··on Things I don't like in configuration languages
This is true. I did a lot of this once upon a time, with great success.
wduquette··on Google Antigravity
Reminds me of the pre-GitHub days, when I had to use CM tools designed to appeal to project and CM managers, not to the poor developers who had to use them every day. Anybody else remember Harvest?
wduquette··on IDEs we had 30 years ago and lost (2023)
I've been doing development using JavaFX, Swing's successor, for many years. It's got its quirks, and places where the dev team stopped iterating on the API a little too soon; but it works and does some really nice stuff.
wduquette··on AI will never be your friend
AI of this kind is nothing more than AI-generated companionship porn. It's destructive of users and of real relationships, as we're already seeing with earlier generations of chatbots (including non-LLM chatbots).
wduquette··on Servo v0.0.1
I'd like to see this succeed, but I'm skeptical that a small team can keep up with the major players in this area. Many years ago Dan Kennedy (of the SQLite team) wrote a lovely HTML widget for TCL/TK. It rendered CSS 1.0 quite nicely, and was a pleasure to use, modulo a few font-related bugs; but was soon rendered obsolete and out of date. Not blaming Dan, here; it simply wasn't a one-person job. Meanwhile, I'd rewritten an app to make use of it. Got burned once, don't want to get burned again.
wduquette··on How has mathematics gotten so abstract?
I once walked around Westwood with my future wife telling her all about Karp-reductions of NP-complete problems. Somehow we now have four kids.
← PreviousPage 4 of 11Next →