TehShrike

Not that I disagree with the folks terrified of so much code being generated within Loops, but as far as it goes, this is a good reminder that if you're getting a LLM to do something, you should probably give it access to your feedback mechanisms.

Yes, a lot of software shops have produced equivalent slop, but I've worked on teams that aimed higher, and they were much more productive over the long haul – not just in fewer bugs, but also in straight up ability to add more features as the software got complicated.

I suspect many developers know the truth, at least to some degree. Their boss said "it's only one [more] popup, add it anyway."

Repeat ad infinitum

There have been plenty of libraries/tools that got people from "I would like to do foo" to "oh, this tool makes foo possible in under 10 hours, I should start working on foo" in the past. LLMs have done this for many foos, which is great.

But I'm with hansvm - I haven't actually seen anyone plausibly maintain 10x. 10x is different from getting people past their activation cost.

There are two types of CS fundamentals: the ones that help in making useful software, and the rest of them.

AI tools still don't care about the former most of the time (e.g. maybe we shouldn't do a loop inside of loop every time we need to find a matching record, maybe we should just build a hashmap once).

And I don't care if they care about the latter.

I agree to a certain point, but I think about it in different terms – some people want to avoid any form of disagreement in order to maintain a kind of politeness, but I want to work on a team where people care enough to disagree with each other if something is wrong: https://joshduff.com/2024-07-18-communication-culture.html

I found the source code Jade was referring to, and it looks like the author just noticed this thread: https://github.com/nkuntz1934/matrix-workers/commit/0823b47c...

My ability to recall and express things that I have learned is different when writing versus speaking. I suspect this is true for others as well.

I would prefer to write responses to textual questions rather than respond verbally to spoken questions in most cases.

Correct, all the filtering is done locally in the browser, and the deploy is purely static.

If PSA had let me use affiliate links, I was planning to do the work to SSR in a Cloudflare Worker, but they declined and I decided to call the project where it was.

I made a fast usable product page recently https://www.buyadagger.com/

hey, haven't seen that one in the wild for a little bit :-D https://www.smbc-comics.com/comic/aaaah

If the college would accept someone like that, they probably don't aim to take their students to a very high level.

I'm feeling generous tonight, I'm willing to consider 0.99986 to round to 99.99%

I worked on a business app made with lit web components and all properties being stringly typed was a real drag. It didn't compare to a realtime-first component library.

One of the reasons I value SetApp so much for Mac apps is that it's curated and I don't have to worry about filtering a bunch of shady or low-quality apps.

You can divide by zero, but you mayn't.

I had the same reaction – his list includes washingtonpost.com, amazon.com, alternativeto.net, medium.com, twitter.com, msn.com, etc.

He dumped his entire blocklist, which must include a bunch of sites that he finds personally annoying.

Here is the list of domains owned by the 16 companies discussed in the post that he linked to: https://codeberg.org/bbbhltz/16CompaniesFilters/src/branch/m...

Here is a similar article primarily about middle-aged adults: https://www.rollingstone.com/culture/culture-features/ai-spi...

I was excited for that proposal, but it veered off course some years ago – some TC39 members have stuck to the position that without member property support or async/await support, they will not let the feature move forward.

It seems like most people are just asking for the simple function piping everyone expects from the |> syntax, but that doesn't look likely to happen.

My mental model for diswashers got a lot better after watching some Technology Connections: https://youtu.be/jHP942Livy0

Any plans to add an option to render the tablature for bass guitar?

I agree with you, I think you're describing the same sort of person I was thinking of in the second paragraph of this post: https://joshduff.com/2022-02-07-eschatology-of-software.html

I don't think anyone has ever thought that best practices will always benefit you.

Whenever a "best practice" or "convention" has been presented to me, that is how it has been framed. (...it is best practice, therefore, it will definitely benefit you to follow it)

I think it is best to strongly reject the idea "best practices will always benefit you".

Most best practices that I have been told about were low local maxima at best, and very harmful at worst.

If someone quotes a best practice to you and can't cite a convincing "why", you should immediately reject it.

It might still be a good idea, but you shouldn't seriously consider it until you hear an actually convincing reason (not a "just so" explanation that skips several steps).

It depends on the office culture. The last time I worked in an office, I used a red/green busy signal like this, and people would generally respect it.

an incident that requires immediate developer intervention, rather than waiting until tomorrow? It seems like you would have to go out of your way to create a system so fragile that this happened once a month

I've never worked at a megacorp, but if megacorp employees believe that it is more acceptable for them to cause issues for customers than a 3-dev company, that really seems like a skill issue for the megacorp.

If it is unacceptable to cause that downtime, you write code that makes the downtime much less likely

Yeah, probably.

What I mean to imply is that it is an issue that is naturally fixed by improved development, and that fixing does require development skill, but the organization can hamstring their developers to prevent them fixing the issue even if they could.

Another way to say: for most software jobs, customer-facing downtime is downstream of a development skill issue that can+should be fixed.

Some (many?) employers make this difficult, and you should try to leave them.

If you work a job where having one of these incidents once a year or more is "normal" then the dev team needs to devote most of its time to fixing that, or you need to change employers.