8,442 karma · joined February 1, 2017
Conterfeit Consciousness is gonna be the name of my new post-liquid analog modular synth IDM project.
I feel like these text spinners could actually be an untapped gold mine for creatively naming things.
It works best with pieces with a lot of ostinato (repetition/vamp) and Bach's Little Fugue in G minor was and is one of my favorites. Really fun to play too, though i get tripped up as soon as the feet get involved. Also, Utopia by Astral Projection (that whole album Trust in Trance 3 is great for this).
Bonus points to mentally visualizing something in time with the music (I like orbs whirling around like atomic orbitals). You can really tie up much of your mental processing this way and I find it much easier than traditional zen meditation, trying to bring focus back to eg. breathing.
Little fugue: https://youtu.be/ddbxFi3-UO4
Trust in trance 3 playlist: https://youtube.com/playlist?list=OLAK5uy_mHhgZDphEanJgP6zSz...
If a police department reuses to accept accountability, and dig in their heels by refusing to work, "just" dissolve it. And while at it, half the calls could be handled by folks without guns.
In practice that obviously would not go over well, people are too attached to the status quo. We just lack the political will to rethink and retool the system (despite most Americans favoring police reform).
> The HTTP SEARCH method was first formally proposed in November 2008 within RFC 5323.
> Before it became a full RFC, the proposal progressed through the IETF under the working group draft name draft-ietf-httpbis-safe-method-w-body. Its formal journey began in March 2021 as an adaptation of the older SEARCH method (from WebDAV's RFC 5323), before being renamed explicitly to QUERY in later draft revisions.
There's no "pretending" this is a good idea, a ton of very smart people have spent a tremendous amount of effort refining this solution. It's incredibly well thought out.
My understanding is too shallow to get why we don't just go straight for EA/Clifford Algebra when the "lower" systems like cross product are insufficient.
I share the author's intuition that there ought to exist some mathematical object that begets Clifford Algebras and multivectors and GA and all the like that we have yet to discover.
> They're spending their precious time on this Earth learning a dead language instead of learning about the law or bugs
I know this is hyperbole, but it's my opinion Latin/Greek emerged so dominantly in law/bio/medical fields is that it allows at the same time semantic bleaching and composition. "Jargon is a DSL" if you will. Sure, you could say "heart muscle no worky cause insufficient oxygen" but "myocardial infarction" is a) more concise b) comprises reusable composable pieces of meaning (myo + card + -ial, in + farcire + -ion) c) most importantly, is extremely precise. It's like the trouble of using English + LLM to define a program, vs just writing damn code. Sure you can do the former, but it's lossy, and that lossiness causes issues.
Douwes F. Komplextherapie der chronischen Borreliose (Lyme disease) - Ein neuer Therapieansatz: die Antibiotika augmentierte Thermoeradikation (AAT). OM & Ernährung. 2018;164:F10.
Douwes F. The successful antibiotic augmented thermal eradication of chronic lyme disease. Paper presented at the 32nd ESHO Meeting, Berlin, 16–19 May 2018.
> Use -diff to completely hide the internal file content during a diff. Git will only report `Binary files differ` if the file changes.
Same like you would binary files. It's still good advice to actually review the lockfile changes at some point.
You can also apparently write transformers to make it more human readable.
One suggestion would be more convincing decoy choices, some were pretty silly. But I have no idea how they come up with them.
Psyches basically raise the "temperature" (in machine learning parlance) of the brain, increasing crosstalk. This can jostle folks out of a mental rut. But it can also create positive feedback loops of upheaval.
Soma would only work as it did in BNW if society controlled essentially all sources of information - which is essentially the whole premise.
https://www.pewresearch.org/internet/2025/12/09/teens-social...
Anecdotally, I've observed a robust correlation between the cost/quality of the model, and attitude towards it.
Most of the general public, young folks, and old folks (ie outside gen z, millennials, and some X) are using free models, usually what's immediately available (cough copilot cough), have really unreliable results, hear all the hype, experience dissonance, and chalk it up to just hype, and walk away thinking AI is a crock of junk.
The Z/Y/G cohort - the ones that grew up alongside the growth of the internet - seem to be the best adopters. They recognize a system which is powerful, albeit flaky, and know how to extract utility from it without over-reliance. Especially ones with paid flat-rate subscriptions.
The power users - the ones using API/paid (by usage) models, tricking out their claude with plugins, seem to have the least amount of hate, but rather a healthy respect for a powerful disruptor.
I also don't buy the whole "the young'ns have never dealt with barriers of entry to the internet and thus lack the tech skills the millennials developed." I think the internet cohort that adopted tech was always split between the powerusers/curious learners, and the "just get my goal accomplished and get out" folks. I think that's roughly the same percentage of folks in Z/alpha, and these kids are just as savvy and aware of limitations of the tech.
Software - this tech is ludicrously powerful and productive. But it's a force multiplier, not a "push button, receive software" system. Great devs that know how to wield it will become überdevs, becoming more productive and with lower defect rate (we have objective internal numbers backing this). But bad devs and non-devs will become high output slop factories. You basically need a dedicated platform team to keep things on the rails. I think this is very akin to the internet bubble. The process, institutional knowledge, and feedback systems developed at this time will grant the "survivors" massive edges after the pop.
I think media generation is or will be a solved problem. Animators, 3dfx, background/filler music composers, those jobs are in sorry shape based on current trends. But a cost explosion could easily level the playing field.
Everything else, where middle managers are aggressively pushing AI usage? Yeah maybe. At this time, other than for document retrieval (basically suped-up search), the "productivity" gains don't really map to value gains. Oh wow you can crank out powerpoint slide decks 50% faster. Write 50% more corporate emails employees barely read anyways. There's definitely a trust issue there with hallucinations. If the reliability gap can be solved (the bots don't even have to be correct, they just need to be less confidently incorrect, and I already see this somewhat with my own agents with tuning), then that could prove the turning point between "begrudging usage at the behest of higher ups" and "actual productivity enhancer."
Does no one remember in the dot com boom all the internet skepticism? "I don't trust it with high value orders, what if it crashes or loses data? Call me old-fashioned but I'd rather write it down." That attitude was quite prevalent for years, even into the 2000s.
The models may go out of date but the process and software are continuously improving.
is basically the premise of
https://en.wikipedia.org/wiki/If_Anyone_Builds_It,_Everyone_...
We are nowhere near the ceiling in terms of process either.
Re: flat rate going to by-usage, I believe this is largely a long tail problem. You have a small number of power users that capitalize on the flat rate to use the service orders of magnitude more than the average user.
In engineering, we can't raise token budgets fast enough. Devs are "routing around damage" when they hit caps, going from claude to opencode to copilot. Productivity is up (roughly) 100-300% in terms of story points and 75-200% in lines of code. And defect rate is down [0], more bugs are caught in review before QA or prod. Our teams are just starting to figure out our new workflows too, for design -> spec -> code -> review, it'll only get better as we refine the process.
It's looking like software industries will reap massive benefits, while most others which have some error tolerance will only see modest gains. It's unclear how it will impact high accuracy fields like legal (it might even be net negative).
Also which is it - a useless technology that has to be force-fed because it sucks, or a economy-shaking game changer that will put folks out of jobs en masse? Those seem like a contradiction.
0 - i think process here is extremely important. I think it would be very easy to create an unmaintainable slopocaplypse. We have an informal platform team of about three (including myself) that have been affectionately and informally dubbed the Tech Priests of Mechanicus Adeptus (warhammer reference) that ensure the prompts/skills and associated tooling are optimal, that code standards are enforced, and that solutions are converging at the system-wide level.
The downside is the ospx markdown specs sometimes end up too granular, focusing on the wrong or less important details, so reading the specs feels like a slog.
Also at times aspects of the english language spec end up way more verbose than just giving a code example would be.
Dunno if it's your exact use case but it's been amazing for keeping a polyrepo microservice ecosystem in sync.
I can't really take the article fully seriously when they are like "uv cant do this. Well actually it can but you gotta use an extra flag." It reads rather PEBKAC.
Sounds like an XY problem. What op wants is high barrier of entry and high curation. That exists already, but by virtue of high barrier of entry, they are hard to find :p. Discords, matrix, webrings, weird little websites.
Spelling it out when 99.9% of your audience doesn't need it actually is the opposite of in-group signaling, it makes it feel like it's aimed at a wider audience, when it's not.