I suspect that my recent experience confirms this. Our daughter shipped two suitcases home from the UK, paying some local company for "door-to-door" delivery. They contracted with UPS who demanded an additional $32 when the first bag showed up. For the second she paid the same fee online so they wouldn't require a check at the door.
Like the author I've been in the process of archiving family memories since my parents passed away. In my Dad's case his early fascination with super 8mm film gave way to a lifelong quest to own more Kodak slide carousels than any other human. It's sort of an odd place to be, when you're in possession of so much that _seems_ emotionally, viscerally important, but that ordinary people living their everyday lives take very little actual interest in. I scanned all the slides with a Kodak thing I bought on Marketplace. There were more than 6500 of them and the archive has passed 20GB in size. Now I have a stack of plastic kodak carousels taller than I am and thousands of slides that I can't just put in the trash because it feels wrong.
I'm working on loose documents and photos now with a great Epson flatbed scanner that I've had for years. It's something of an obsession for me now: to finish the job and tie their lives and a good chunk of ours off neatly. When I'm done I'll pack it all onto thumb drives and send copies to my siblings and they will look at a few of them and then put the drives in a drawer and that will likely be the end of it. But I will have done my duty to the old folks, even though it took long enough that I became one. It has all reminded me of how I mourned when I lost a hard drive years ago, and then came to the realization that I hadn't looked at any of its contents in years and that if I lived to be 100 probably none of it would ever have been important again anyway. You can't really keep anything, so do your kids a favor and dispose of your stuff while you can :).
For people interested in the subject generally I highly recommend John McPhee's anthology "Annals of the Former World." Actually I highly recommend everything John McPhee has written but this is a good start :).
I just finished Annals of the Former World. It's essentially a 700 page-long ode to geology, using scientific terms for their prosody as much as their meaning. I once saw someone else remark that "Rising from the Plains" was the greatest western ever written.
I used to think geology was a dumb science, but this book single-handedly made me obsessed with the topic. Geology is really more like "earth history" and it's a startlingly young field, a dynamic which plays out across the volumes.
I would pay good money for a field guide/itinerary to accompany "Assembling California".
More directly related to the Green River, I found Wayne Ranney's "Carving Grand Canyon: Evidence, Theories, and Mystery" an accessible/engaging intro to deep geological mysteries.
I would not say your list is anything like complete, although those topics are often discussed here. Apple is a huge player in the general computing ecosystem, and probably a majority of front- and back-end developers these days work on macbooks, so it isn't surprising that the things they do resonate in this community.
I think the dangers that LLMs pose to the ability of engineers to earn a living is overstated, while at the same time the superpowers that they hand us don't seem to get much discussion. When I was starting out in the 80's I had to prowl dial-up BBSs or order expensive books and manuals to find out how to do something. I once paid IBM $140 for a manual on the VGA interface so I could answer a question. The turn around time on that answer was a week or two. The other day I asked claude something similar to this: "when using github as an OIDC provider for authentication and assumption of an AWS IAM role the JWT token presented during role assumption may have a "context" field. Please list the possible values of this field and the repository events associated with them." I got back a multi-page answer complete with examples.
I'm sure github has documents out there somewhere that explain this, but typing that prompt took me two minutes. I'm able daily to get fast answers to complex questions that in years past would have taken me potentially hours of research. Most of the time these answers are correct, and when they are wrong it still takes less time to generate the correct answer than all that research would have taken before. So I guess my advice is: if you're starting out in this business worry less about LLMs replacing you and more about how to efficiently use that global expert on everything that is sitting on your shoulder. And also realize that code, and the ability to write working code, is a small part of what we do every day.
I’m glad you listed the manual example. Usually when people are solving problems, they’re not asking the kind of super targeted question in you second example. Instead it’s an exploration. You read and target the next concept you need to understand. And if you do have this specific question, you want the surrounding context because you’ll likely have more questions after the first.
So what people do is collecting documentations. Give them a glance (or at least the TOC), the start the process to understand the concepts. Sure you can ask the escape code for setting a terminal title, but will it says that not all terminals support that code? Or that piping does not strip out escape codes? That’s the kind of gotchas you can learn from proper manuals.
> So I guess my advice is: if you're starting out in this business worry less about LLMs replacing you and more about how to efficiently use that global expert on everything that is sitting on your shoulder.
There's a real danger in that they use so many resources though. Both in the physical world (electricity, raw materials, water etc.) as well as in a financial sense.
All the money spent on AI will not go to your other promising idea. There's a real opportunity cost there. I can't imagine that, at this point, good ideas go without funding because they're not AI.
I don't agree. LLMs don't have to completly replace software developers, it is enough to reduce the need for them by 30% or so and the salaries will nosedive making this particular career path unattractive.
Ditto, self-hosted for over eight years at my last job. SCM server and 2-4 runners depending on what we needed. Very impressive stability and when we had to upgrade their "upgrade path" tooling was a huge help.
I once found a bug in code that was read to me over the phone while I sat in an airport waiting for a flight. So I agree that constructing a model of the program in your head is the key, and you can use various interfaces for that. Some are more optimal than others. When I first started learning to write programs we very often debugged from printed listings for example. They rolled up nicely but random access was very slow.
A type system lets different parts of a program agree on how to interpret a pattern of bits in memory and then enforce that interpretation. I don't think electronic circuits built from discrete components that have immutable physical properties are analogous in the way that the author apparently thinks they are.
> crossing the ocean on a boat felt absolutely epic and dangerous
Given the way death was implemented ("LFG @ EC tunnel for a corpse run to Guk!") and the fact that you could fall off the ships in the middle of the ocean when the game lagged, it _was_ epic and dangerous. I remember the first time it happened to me and players in public chat coached me through a 20 or 30 minute swim to get my wizard and stuff to an island with a portal.
reply