10,591 karma · joined March 16, 2015
"Did you see that game last night" replied to with "The Visitors are my favorite team" is something you could say instead of "hi" as a family.
Would have come in handy when our niece was traveling in Asia and asked for money a few times, but in this case it wasn't a scam.
I got no traction with it, which I was a bit surprised by because one of the family members works at the Puzzle Palace.
People are applying that label to anything that has the taint of AI on it. I get why.
I realize there are a lot of reasons why people hate AI, but one that is frequently cited is that it's dehumanizing. It's kind of ridiculous to see those same sort of people call something "slop" when I've put tens of hours into guiding the AI tooling. Talk about dehumanizing!
A friend of mine and I go out to lunch every 3 months and talk about, among other things, investing. We've made a trope of it, calling out the people who are predicting an imminent market crash every time we have lunch.
I'm not saying that it doesn't look like it's going to crash, but I'll also say that there's also a very sizeable downside potential for getting out of the market.
It's a lot like how when you read you almost never read every letter, you look at the entire word and that turns into an idea in your mind.
Rally-X: https://linsomniac.github.io/rally-xy/
Tempest: https://linsomniac.github.io/teapot/
Dig-Dug: https://linsomniac.github.io/digger/
And not an arcade game, but a multi-player throwback to a multiplayer shooter game my team used to play called nSnipes: https://github.com/linsomniac/isnipes
iSnipes does require downloading and running a server, the others you just play on the web.
As that DDoS was going on I realized that some of our dev and staging processes were impacted by it, and that apt-cacher-ng was doing nothing to help us.
apt-cacher-ultra snapshots the repo meta-data after verifying it, and only promotes it if the metadata all checks out. Additionally, it can optionally keep a list of "hot" packages, and can include those in the snapshot calculation.
Additionally, apt-cacher-ng would regularly choke and require some handholding. I'm hoping -ultra resolves that as well.
Unpopular answer that the author seems to be dismissing: Maybe the thing that 30 years has taught this guy is that the LLMs can answer the question better than he can. Or that he can't give a substantive answer without doing research into it with an LLM.
>LMGTFY
I mostly saw LMGTFY used when the question was the sort of thing that a person would have to research but that google results had a high chance of getting with "I'm feeling lucky".
If you've already done a bunch of research, and already asked the LLMs, when someone says "Honestly, ask Claude", you should be able to come back with what results you got to your question and what you need clarification on.
I've been doing programming and sys admin for 40 years. When I run a coworkers question through the AI tooling and talk through the answer with them, it's because my 40 years of experience tells me that's the next step.
I have Sol 5.6 ultra working on Thrust right now.
But then around 2 months ago I decided to switch to NixOS and there wasn't a Nix way I could find to use Astro. So I had Opus build me a vim setup for NixOS that included the batteries I wanted in my setup. I gave it a paragraph description and it built something that has been a joy to use.
"vimdiff" is a really great way to review code changes side-by-side.
I'm trying Codex as my primary the last day or so, because I'm at 98% use and reset in 3 days on Claude. I'm worried about a lot of our skills and CLAUDE.mds and the like getting lost unless I migrate them, but otherwise codex seems to be working great.
It would have been WAY more useful for them to announce the extension, you know, yesterday. This is basically the worst time for them to announce it. Bunch of goobers, who thought this would be a good idea?
So I will start a workspace for each different thing I'm working on, label it "Studio Shed Packet", "Teapot game", "Mux experiment". Then in each one I run a Claude Code. Then I can see the status of my Claude Codes just by glancing at the sidebar, rather than having to switch between screens to see what is waiting next.
I've been using it around a week so far.
A few small downsides: I can't copy/paste in wezterm using the keyboard/vim keys because it is constantly drawing the screen and unselects my selection. The mouse drag in herdr works very well though. It'd also be nice if you could rebind key mappings in the UI, because I still haven't rebound the keys and am using the mouse.
I need to see if it can build me a fabulous todo app.
4-5 years ago I spent around a year refining a paper-and-pen daily planner, and I went 100% into it and liked it. The paper planner though had a non-ideal workflow, and so I wanted to look into some automation of it. I got a Kindle Scribe hoping they might grow its capabilities. It had a great "it's like paper" experience, but no automation or tools or apps seemed to come along. So then I tried a fairly high end Boox, I got it and then used it only a couple weeks and then stopped doing that daily planner process entirely.
But if Fable could build a Boox or reMarkable app, that might be a big win.
I've tried task warrior, and todoist, and in the end I just keep going back to a straight text file I edit.
Despite this, I could expect 3-5 people to hunt me down at PyCon when I was running the wireless to tell me that I had misconfigured the wifi because it was set to low power. More reports of that than reports of wifi not working, IIRC. ;-)
(I was running the wireless because the people we paid do to the wifi would just set up one or two APs and crank the power)
You say that, and that's a possibility, and maybe in your experience that is true. But I'd say I've found actual humans will frequently use existing internal models of something unless they have a reason to believe something has changed to invalidate that. We even have a well worn joke about what happens when you assume.
>you could for example be involved with multiple teams of different sizes that are subject to different rules
Just to clarify, my experience with the memory of these tools doesn't provide any data (for or against) how well/poorly the memory may work with someone who is involved with multiple teams.
So my guess is that what is driving the need is that (speculated) 100x the next major models.
Now, I'll agree that this is probably the sort of thing I should put in the CLAUDE.md, but in this case it wasn't on my radar to put that in my CLAUDE.md, so it was nice that it surfaced that.
It does sometimes go awry though. Today I was asking about a problem I was having authenticating, and it said "you may be running into this trusted proxy setting because you put your apps behind an haproxy". That is true of 95% of our apps, so it was worth mentioning, but in this case it was not so I had to correct it. But, I'm glad it mentioned it because if we did have it proxied it could have saved me a lot of time.