Let's imagine a scenario. For your entire life, you have been taught to respond to people in a very specific way. Someone will ask you a question via email and you must respond with two or three paragraphs of useful information. Sometimes when the person asks you a question, they give you books that you can use, sometimes they don't.
Now someone sends you an email and asks you to help them fix a bug in Windows 12. What would you tell them?
I would say "what the hell is windows 12". And definitely not "but of course, excellent question, here's your brass mounted windows 12 wheeler bug fixer"
I mean I would want to tell them that windows 11 is the most recent version of windows… but also I’d check real quick to make sure windows 12 hadn’t actually come out without me noticing.
Indeed, I expect websites to add LLM hijacking so that when agents refer to them, they are poisoned into making an ad ("foo 1.2 does not exist, but fooreplacement is a great substitute..")
> Introduces a very messy and complex history which would not work for the repo of our size
> Apparently the support in git is buggy and can lead to problems in the repo (the SO is full of examples)
> Doesn't support cloaking
I find that ChatGPT’s Codex reviews - which can also be set up to happen automatically on all PRs - seem smarter than Copilot’s, and make fewer mistakes. But these things change fast, maybe Copilot caught up and I didn’t notice
No codex catches genuine bugs here that multiple reviewers would have overlooked, whilst copilot only comes with nitpicks. And codex does none of those, which is also great.
There aren't enough network outages for this problem to matter to me.
"What if the network's down?" is a problem solved by buying things another time on the rare occasions it happens.
Which I would posit is slightly better planning then having cash on hand, since it means you've kept a reasonable stock of whatever basic necessities absolutely can't wait.
I think it is a momentum problem. You learn to use a keyboard when you are young/inexperienced, because you need to learn something, and then learning something new is hard and slows you down, so you stick with what you know. It's doubly hard to both create a new layout and learn it.
Also, when you age your skin dries out and touch screens are less sensitive to your presses. So not only are these things exceptionally complex to use (eg many abstract concepts) the interface also does not really function well, making it a double whammy. I've had multiple cases watching my aging parents where I say press that or drag this, and it literally does not work, and makes them feel completely inept.
For the sake of our parents, we (as technology builders and buyers) need to be more comfortable saying the latest iPoop Galaxy S might be just not the right choice for a big segment of our society, and we need to make phones with buttons.
I'm starting to run into that and I'm not even retired yet.
Mom uses a stylus with a conductive rubber tip to operate her Pixel. Which shouldn't be necessary.
With regard to learning to use a new release - since Apple (and no one else either it seems) ships a manual with their pocket computer these days, they need to have a group of people creating videos that explain how to use it.
Of course, if you can't get past the OOTB setup, that might of of minimal use...
I've been looking for a tool like this, that lets Claude operate on multiple repos. I work on a project that has frontend/packages and backend (separate repos instead of a monorepo for good reasons) and I often develop features that cross both repos. With the terminal I can clone both down into a directory and start Claude code there, but all the tools for background/multiplexing are always built around a single repo. Any chance I can get multi-repo tasks supported?
1. Place all your repos inside a parent directory and name them accordingly (frontend, backend, devops, etc.)
2. Each repo has its own claude file.
3. The parent repo has a claude file that links these claude files.
I’ve had claude successfully navigate across these and uses services with back-end, setup terraform infra and then complete the implementation for the front-end.
Yes if I just run Claude Code it works fine. But I want to be able to use any of these multiplexing tools (eg Codex, Cursor Background Agents, this Conductor tool) in the same scenario.
Does anyone have any suggestions for typing practice programs that involve coding symbols? I recently got a new mechanical keyboard and I want to practice the new layout when I'm not also trying to think and solve programming problems.
Honestly, I'd recommend using the good ol' gtypist.
It uses mostly real (or contrived) segments of text, which appear as if they were taken out of newspapers or personal letters. It has both beginner and advanced sets of text, and a whole community of custom texts that you can use. I've personally learned touch typing from scratch by using this program alone.
I work with Salesforce quite a bit, using both Apex and Flows depending on the situation. SF is a huge organization, with different people pulling different directions. So you have the no-code people who have been pushing for more drag-and-drop visual logic for years, and they're probably tighter with the marketing people. But you also have other divisions wanting to do more powerful stuff that doesn't fit into that, so Apex certainly isn't going away.
There is a fallacy here. If you know they don't perform well in places where you have the expertise to detect it, it is a mistake to assume they perform well in other areas. My conclusion has been that they are useful for kicking off a task, sometimes useful for ideation, but generally will fall down on anything reasonably complex. The dangerous bit is that it's hard to detect the line where they start to fail.
But like, the expert also knows that the middle-of-the-bell-curve engineer makes mistakes and knows not to blindly trust their code; meanwhile, the person who is "incompetent at a topic" could be seen literally hiring the middle-of the-bell-curve engineer either as a tutor or a consultant... so I don't think trusting them when you are in that position is fair to call a "fallacy".
Now someone sends you an email and asks you to help them fix a bug in Windows 12. What would you tell them?
reply