> uvex init my_new_slop_project —-describe “make me the bestest saas that will make $1M ARR per day” —-disable_thinking —-disable_slop_scaffolded_feature

> uvex add other_slop_project —-disable_peddled_package_recommendations

> implicitly phoning home your project, all source code, its metadata, and inferring whether your idea/use-case is worth steamrolling with their own version.

This is the future of “development”. Congrats to the team.

Is this whole concept essentially a fundamental misunderstanding of the difference between "encryption" and "encoding"? I don't mean to be pedantic and don't want to make assumptions due to my respect for the source, but I don't understand how you can meaningfully manipulate the data that has been _actually_ encrypted? Doesn't the ability to accurately manipulate it imply that you have some understanding of its underlying meaning? The article is light on algorithmic details:

> "...a mathematical transformation, sort of like the Fourier transform. It encrypts data using a quantum-computer-proof algorithm..."

I am assuming there is some deep learning at play here i.e. it is manipulating the data within the latent space. If this is true, then would the embedding process really be considered "encryption"? You could argue it is security through obscurity (in the sense that the latent space basis is arbitrary/learned), but it feels like two different things to me.

(Disclaimer: I am not a cryptographer and this is a heavily simplified explanation). Homomorphic encryption is built on the foundation of 'hard problems' (e.g. the Learning with Errors Problem) - loosely, computational problems that are thought to be impossible to reverse without being in the possession of a secret key.

The crux of HE is that it provides a _homomorphism_: you map from the space of plaintext to the space of cipher texts, but the mapping preserves arithmetic properties such as addition and multiplication. To be clear - this means that the server can add and multiply the cipher texts, but the plaintext result of that operation is still irreversible without the private key. To the server, it looks like random noise.

I don't think it's helpful to think about this as connected to deep learning or embedding spaces. An excellent resource I'd recommend is Jeremy Kun's guide: https://www.jeremykun.com/2024/05/04/fhe-overview/

Is it really oss death if SO many projects are created and shared by individuals that indie dev seems commonplace?

This reminds me of a gag voting simulation website from the early 2000s when BushJr was running for president against Al Gore. The (maybe flash?) game simulated voting, but when you tried to click, the buttons would “run away” from the cursor, or change size to avoid being clicked… dark patterns… always fun to “play against”.

More recently though, I must say, YouTube has really jumped the shark in terms of perfecting their dark patterns/algo stickiness. I can’t even go to the site without immediately forgetting my original intent.

Also see The Simpsons, Treehouse of Horror XIX, where Homer tries to vote for Obama using an electronic voting machine:

https://youtu.be/47QZ6PoHl44

Yesterday I scrolled down the front page of my Youtube, and saw the "shorts" shelf. I clicked "Show me fewer shorts" like I have a hundred other times.

I did something else for a few minutes, then I scrolled down another page or so.

The shorts were right there again.

Google is evil. Anyone still working for them is enabling this.

i'm old too and remember that, i believe it was javascript, not flash

I feel I could write a long response to every comment in this thread as notekeeping is something I consider critical. Knowing when to commit to “The capital-N Notebook” is something I’ve struggled with as well. What has been effective for me is to scribble daily on a marker/chalk/dry erase board and then transpose the final thought into “The Notebook” at the end of each day. This lets me format, err, mull, etc. and the final (sic clean) notebook still has enough granularity to retrace my thoughts in the med-to-long term.

But this is the way of computer science at large for the last 15-20 years… most new CS students I’ve encountered have spent so much time grinding algorithms and OS classes that they don’t have life experience or awareness to build anything that doesn’t solve the problems of other CS practitioners.

The problem is two-fold… abstract thinking begets more abstract thinking, and the common advice to young, aspiring entrepreneurs of “scratch your own itch” ie dogfooding has gone wrong in a big way.

> Slopacolypse Really… REALLY not looking forward to getting this word spammed at me the next 6-12 months… even less so seeing the actual manifestation.

> TLDR This should be at the start?

I actually have been thinking of trying out ClaudeCode/OpenCode over this past week… can anyone provide experience, tips, tricks, ref docs?

My normal workflow is using Free-tier ChatGPT to help me interrogate or plan my solution/ approach or to understand some docs/syntax/best practice of which I’m not familiar. then doing the implementation myself.

Claude code official docs are quite nice - that's where I started.

To use anecdotes of specific influencers or even to cultural short/med-term memes misses the OP’s fundamental point in saying

> “this is the future of culture”.

The point is that the future of “culture” is increasingly decentralized; that the ability or more aptly, the opportunity, to accumulate “cultural influence” will tend towards higher entropy as a direct repercussion to the proliferation of the means to accumulate it.

Put differently, as the hardware and software used to record, store, and share content become more widely accessible, anyone with the access and motivation to use the tools truly has the opportunity to become famous.

What an incredible read.

Seriously the way it slowly goes from totally coherent, to slightly coherent, to flat earth, is as another commenter said; “absolute cinema”.

It really is a masterpiece.