I am Graham Mitchell, a software engineer in Austin, TX. I am also the author of the books "Learn Java the Hard Way" and "Learn Object-Oriented Java the Hard Way".
https://keybase.io/grahammitchell
Prior to becoming a developer, I spent twenty years (1997-2017) teaching Computer Science at Leander High School.
It is (or was, at least -- I haven't looked since I left) a pretty good school; consistently ranked near the top 5% of public schools nationally. I had a lot of students who were exceptional but most of my students were regular kids with no particular aptitude for programming. I taught over 2000 students.
[ my public key: https://keybase.io/grahammitchell; my proof: https://keybase.io/grahammitchell/sigs/fFa_yO52UWi27swZ6hzR5gE-KWge1dNmSFxSgl5Jl10 ]
投稿
As a musician, I prefer illegal downloading over Spotify (2011)
derekwebb.tumblr.com
75 ポイント·投稿者 teach··41 コメント
Capital Factory CEO Joshua Baer killed in plane crash near Laredo, TX
cbsaustin.com
20 ポイント·投稿者 teach··7 コメント
Ask HN: How expensive are LLMs to query, really?
5 ポイント·投稿者 teach··3 コメント
Instagram showing me someone-else's recently-used emoji reactions
twitter.com
2 ポイント·投稿者 teach··0 コメント
Analogue Pocket: Classic Limited Editions
analogue.co
1 ポイント·投稿者 teach··0 コメント
How to Stay Productive All Day – Coding and Scheduling Tips for Programmers
freecodecamp.org
2 ポイント·投稿者 teach··1 コメント
Ask HN: How do you feel about TL;DRs on Hacker News?
5 ポイント·投稿者 teach··3 コメント
Float or double?
ilikebigbits.com
2 ポイント·投稿者 teach··1 コメント
What Colour are your bits? (2004)
ansuz.sooke.bc.ca
1 ポイント·投稿者 teach··0 コメント
You Keep Using That Word: Meritocracy
stet.editorially.com
2 ポイント·投稿者 teach··0 コメント
Seven Things I Did to Reboot My Life (by Wil Wheaton)
wilwheaton.net
9 ポイント·投稿者 teach··0 コメント
What happened to the "More" link on saved stories?
1 ポイント·投稿者 teach··0 コメント
"If you want to order it, use 'view source' to find the commented-out link."
prgmr.com
217 ポイント·投稿者 teach··92 コメント
This is why the American Dream is out of reach
thelastpsychiatrist.com
10 ポイント·投稿者 teach··3 コメント
Penny Arcade uses Dropbox and Tarsnap for backups
reddit.com
2 ポイント·投稿者 teach··1 コメント
Ask HN: How much should I charge for a talk?
10 ポイント·投稿者 teach··5 コメント
IPad: No product will improve your production if you're not already producing.
It could! An MCP would actually be great but Slack would prefer to sell us their own AI integration product so (1) they make it difficult and more importantly (2) it's against their terms of service
We pay them a LOT of money every year and they would absolutely notice the indexing at the level we'd need to do to make this work ourselves, so the answer is "because Slack is preventing us".
Slack's approach is NOT good enough, because the version of the Agent that lives in Slack cannot see the context of the Agent that lives inside Cursor on my developer laptop. They might be clones with identical brains, but they can't talk to each other or compare notes.
Just my two-cents as a very much boots-on-the-ground infrastructure engineer. We use LLMs heavily on my team -- to write code and review PRs. Our harnesses and guardrails are very very good so we get extremely high-quality output out of most models.
But getting the humans and agents to talk together is really fragmented right now. It's annoying that the agent with the context in my locally-installed Cursor can't really participate in a Slack conversation about a PR that 'it' principally authored (and which I've signed off on).
This is a real communication problem that we face every day, and eventually someone will solve it well and I will ask our leadership to give them a lot of money.
This is a good clarification but I think the core issue is that Spotify (and Apple Music and Amazon Music and probably others) have chosen a business model in which consumers can listen to basically everything and yet artists do not get paid. The rightsholders suffer too yet they are complicit.
This business model ALWAYS outcompetes any other, and can't be "fixed" imo, because no one will pay per-stream or pay $50 a month.
I think this is a false dichotomy. There's no reason "all music is paid only" is the only option besides the all-you-can-stream for one monthly fee popularized by Spotify.
For example, the other day I discovered a local artist on Instagram. I went to her Bandcamp page and was able to listen to some tracks for free with zero friction. I ended up purchasing the deluxe vinyl, and it was one of my favorite albums that came out last year.
I've done similar with the radio. I went from hearing a track on the radio to purchasing the album on Bandcamp in like ten minutes.
Spotify and the like CAN help with discovery, sure, but that doesn't have anything to do with their business model.
I agree with you that you are never "forced" to pirate; you can simply not listen to the missing album.
But many many many many excellent albums are not available for sale anywhere at any price. They essentially do not exist, except in the hands of a few collectors.
The bands themselves, the creators of said music, want their music to be heard.
The fact that they aren't available for sale or streaming is often because a rich bureaucrat can't be bothered, not for any legal reason.
I'm quite certain I formally verified that two processes were both able to get into the critical section WITH THE ALGORITHM I WAS VERIFYING, but this was 35 years ago, so details are fuzzy.
Remember that this is long before Wikipedia and even before Google, so I have no idea where I'd have gotten the alleged Baker's algorithm from.
Also you're right that this isn't much of an issue in practice, but that's not what formal verification is about, now is it? :)
I've been following Bob Cringely for nearly 30 years and he's always written like this.
This is almost certainly not AI-generated text, and he's not saying Claude is wrong.
He's saying something different that is probably true (that LLMs can't produce facts, no matter how much they are trained). It is also not that interesting (LLMs hallucinating sometimes doesn't mean they're not useful).
I'll grant you the self-aggrandizement, but he's come by it honestly.
I actually did take a formal verification course in college. Our final project was to use the techniques we'd been learning to verify some classic critical-section locking algorithm. I chose to verify an implementation of Lamport's bakery algorithm[0] in C (this was the 90s -- a lot of code was still being written in C).
The problem is that Lamport's algorithm makes an assumption that the "ticket number" is unbounded and any finite implementation in C will almost certainly use a value which is limited to 32 bits or so.
So I was able to formally verify that the algorithm fails to protect the critical section if enough processes are kept waiting to overflow the counter. :)
This probably just means that Lamport's algorithm isn't a great choice for such environments, but I'm still bummed that the professor gave me a B.
It's interesting that your experience/workflow is so much different than mine. This (claims to) solve a real problem that I deal with every day.
My company is remote-only, and my coworkers mostly don't live anywhere near me. We see each other a couple of times a day on video chat, but communicate mostly during the day via Slack.
We're also, uh, pretty far along the curve in adopting LLM agents to write good code for us. With a good model and the extremely good guardrails our of specific coding harness, LLMs are writing the majority of our code these days.
So on a typical day I'll grab a ticket off the top of the stack, point my LLM at it, and start working with it to solve the problem. We'll make architectural decisions, etc, create a plan and execute the plan. The feature I shipped most recently cost $19 in tokens and the LLM was churning without my input for like half an hour at one point in the thick of it.
MAYBE if there's a question I'm not sure which way is best I'll post a question in the team chat for my teammates to weigh in on. But a lot of my tickets are done completely autonomously.
Then I'll open a PR, and post a link to the PR in Slack, requesting their review and my teammates will see the implementation for the first time. They sometimes have questions! Often, they'll post these questions in the Slack thread rather than as PR comments, because we're having a fast real-time conversation and GitHub comments aren't a great fit for that.
These questions have answers in the chat log with the LLM that lives on my laptop, but I can't trivially show it to them.
So I end up playing telephone with the LLM -- copying my teammate's questions from Slack to the LLM chat, pasting the answers back, etc
The idea that my coworkers and the LLM and I can all be more easily a part of the same conversation appeals to me greatly
None of this means the Zed team is on the right track. Nor that my team might work better in a different way! But we're too "successful" with this approach for there to be much institutional pressure to change our ways at the moment.
In my case it's exactly that. I have a Linux gaming workstation, a work-issued (and managed) MacOS laptop and a Google-branded (Pixel) Android phone.
Bitwarden just works in all those places and the tech was, by all accounts, rock solid. AND I can pay for it instead of trying to leech off some privacy-ambiguous free tier.
https://keybase.io/grahammitchell
Prior to becoming a developer, I spent twenty years (1997-2017) teaching Computer Science at Leander High School.
It is (or was, at least -- I haven't looked since I left) a pretty good school; consistently ranked near the top 5% of public schools nationally. I had a lot of students who were exceptional but most of my students were regular kids with no particular aptitude for programming. I taught over 2000 students.
[ my public key: https://keybase.io/grahammitchell; my proof: https://keybase.io/grahammitchell/sigs/fFa_yO52UWi27swZ6hzR5gE-KWge1dNmSFxSgl5Jl10 ]