Every one of those is also an example of how people have written and spoken since before AI existed. But then, I don't 'Claude', so I'm not sensitised by exposure.
> That doesn't actually answer my question, it just makes me want to repeat it: if you have that attitude, why be there at all? The existence of a forum instead of an IRC chat or some other immediately-forgotten medium means that someone considers the discussion worth preserving.
At first I thought the complaint was that long threads can have numerous irrelevant fluff posts, outdated posts, and off-topic posts getting in the way of reading the useful bits. But treating a forum thread as a live conversation was somewhat surprising to me. And specifically excluding that a thread could be reference material perhaps reflects a difference between the sorts of places GP and I prefer to browse.
But about long threads: stepping through a 30-page or 300-page thread, where rarely is a post an update about the project, while the rest add nothing substantial, discourages looking through the whole the whole thread is not always practical. And search often doesn't return anything useful.
Droidify sometimes does a weird thing when installing apps:
1. Ensure Droidify is not running.
2. Launch it.
3. Tell it to install or update to an app.
4. Receive an Android system prompt to approve the install/update.
5. Approve it.
6. Tell Droidify to install or update another app.
7. Reveive a system prompt to approve the action of step #3 again.
8. Approve it.
9. Receive system prompt to approve step #6.
10. Repeat #6 through #9 for more apps.
Workaround: Do steps #1 through #5.
Foxy Droid doesn't have this problem, but won't auto-download updates for you.
Disagree. If this VP is delegating to direct reports things they should be capable of handling, that's normal. If a direct report informs this VP of intended action, it both keeps the VP informed and acknowledges that the VP might have other information that should alter the intended course.
I'm assuming a trusted, competent direct report, and that the DR has chosen a timeframe that is reasonable give the situation.
For example:
Customer has a problem that will cause them to miss payroll on Friday. We've known about it since Tuesday morning. VP, DR & team spent Tuesday understanding the underlying problems.
VP has found one of the issues is in a third-party product, who are notably resistant to believing they have a bug, and are prone to not deploying a fix until either the next major update or three months after first report. VP is working on a software fix that makes use of another esoteric behaviour of the third-party product to potentially prevent the current problem from recurring, but now expects to not be done before Thursday.
DR & team spent Wednesday testing, and believe they can ensure payroll will be ontime by deploying a workaround Wednesday night, during the customer's existing maintenance window, where customer's I.T. group are known to be available for this issue. DP sends email to VP with intended course of action and known caveats.
VP knows he can keep working on the longterm fix without the customer's ability to make payroll hinging on it.
. o O ( The above actually happened, approximately thrice, due to different vendors committing shenanigans. It is abstracted from different customers. )
I resorted to telling people "Click/touch the funny little group of three horizontal lines.", and if they still hesitated, "…Looks like an air vent.".
On occasions where I told them it's really called a hamburger menu, they all either looked like they thought the idea was nonsesical, or said as much.
…Don't get me started on apps that have multiple air vent (or elipsis) menus visible simultaneously.
Or apps that abuse the symbol further by changing the meaning from "menu" to "toggle a sidebar that may or may not have portions that act like a menu."
The walls are getting below dew point when they cool and/or the humidity is too high for extended periods. And the walls have dust or other surface accumulations conducive to mold. Insulating the exterior and keeping the interior humidity low will help. Thoroughly clean and dry the interior walls, removing all mold and all other surface accumulations. Keep the interior above dew point.
Aging or damaged batteries can have dramatic'ly different output curves than the system expects. What looks like x% to the system can be at the edge of a cliff on the curve, causing sudden shutdowns or power loss.
Quite often when I use a 1990s system, I encounter several things that are instantaneous, while modern machines take several seconds.
Like, sending an empty folder to the bin:
Win 10 this afternoon took seconds to display a dialog box with no content, the a couple seconds to add a progressbar, then a second to add the cancel button, then multiple seconds to finish showing progress.
But at home a 1991s system with System 7 completes the same task instantly without needing a progressbar.
I do not hold with the detractors. I've personally known people who write like this since before LLMs were a thing. I rarely use LLMs, and come from the days of "expert systems" and the tail end of when universities had hundreds of typewriters in a room.
So perhaps, that's my bias: towards a former reality.
I often find myself wondering at a random HN commenter's flaming of a post for being full of AI slop, when the accused reads like normalspeak to my half-old eyes.
> Moore law did its thing, now you can do it with a lot less computer power.
s/power/time/ maybe? Or on second thought: so energy-efficicient that it actually uses less power in the same-or-shorter time… which brings me back to "less compute power".
You can, but then "The cake is a lie.", because linecount and bug rate, when concieved as proxies for productivity[1] or quality rarely match up with reality in a way that allows you to make predictions or reason about past outcomes.
You can reason about frequency of particular types bugs, such as null pointers or overflow, or whether those bugs can occur at all.