Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Feed
All
Post Types
- Rants
- Jokes/Memes
- Questions
- Collabs
- devRant
- Random
- Undefined
Cancel
All
-
So I get a message from my ex-colleague today, and it’s déjà vu all over again.
Apparently, the CTO at my old company went full Hulk in the office this morning, demanding to know who used the ops@ email to subscribe to something called "custom purring ASMR." If that sounds familiar, buckle up - this one’s even better.
For context, this is the same company where I once had to explain to the CFO why our tech@ email got invoiced for "panties juice, extra virgin." If you don’t remember… Yeah, I left, but the shenanigans clearly stayed. Here’s a spot-the-difference picture: https://devrant.com/rants/6213132/...
Turns out, one of the devs was testing an API integration for some niche subscription platform. Nothing new there — sandbox environments, dummy accounts, €5 test payments. Except genius over here decides to jazz it up and names the testing account: "Cat Daddy Deluxe, meow to pay." Obviously not meant for production, right?
Fast forward to yesterday (yes, Friday): the platform goes live without clearing the sandbox database. Dev’s test account? Now the default subscription for every new creator. Not only that, but every 1k subscribers it "wins" a discount for the next most popular account. What are the top 5 other popular accounts?
5. "Leather Daddy Lullabies" – soothing bedtime stories narrated by a guy in full BDSM gear.
4. "ASMR For Adult Toys" – exactly what it sounds like, but HR will still ask.
3. "Moaning Meditation Mondays" – very NSFW guided mindfulness exercises... weekly!
2. "Kinksploration 101" – a podcast exploring bizarre fetishes you wish you didn’t know about.
1. And last but not least, "Spicy Grandma Diaries" – erotic stories written and narrated by a sweet old lady from the local senior centre, apparently depicting real-life escapades from her 70s. In great detail.
Here’s the kicker. Friday, ops@ gets two discount emails. The same guy who roasted the “panties” girl the hardest, the very one who caused this mess, is now sure they’ve finally sent him more accounts to test - because clearly, those can’t be meant for production. Right?
Long story short: he spent €118 of real-life company funds, and IT is now on the hook for lifetime memberships to “Purring Dominance 101” and “Whisker Tickler Masterclass.” How satisfying is it to see the universe balance all his not-so-funny comments?
Also, I’m definitely getting them to forward me those whisker-tickler classes. No matter how good you think you are, some areas of life always have room for improvement.4 -
I'm not one of those people who can just buy a phone and use it. I have to unlock it, flash it, de-google it and customize it before first use. I don't changes phones often, but my 2019 phone is slowly dying.
Here's my whole new setup with a Sony Xperia 1 V:
https://battlepenguin.com/tech/...9 -
My phone screen died very suddenly so I had to power on an extremely old phone to serve as an alarm clock.
What is it with Android and completely dying after a couple years' downtime?
Anyway, I think the only reason I replaced this phone was that it was insufferably slow and the immediate excuse to get rid of it was that the charging port corroded. So glad I keep these things around, even after moving house 4 times.15 -
Yearly angular rant.
I am doing since 2023
https://devrant.com/rants/10263715/...
and yep, angular is still shit in 2025
And still maintaining a high level, business critical, giant angular set of web portals, and some more projects with an angular UI that has to do with AI projects.
Of course not my choice, I'm forced to use this pile of steaming shit.
Year by year they keep releasing a new version and I always hope they get their shit togheter.
Every year is worse.
Instead of fixing this half-baked, ill-fated, broken clot of hacks rigged togheter, they keep adding cosmetic shit and useless no-one-asked ever features.
They added signals when there are not 1, but 2 mature, battle-tested frameworks (rxjs, ngrx) that already do it better.
They added @if @else etc etc. syntax after 10 years people were telling them that using that shit *ngIf and ng-container and templates was a shitty hot mess.
The whole change detection system is still the worst, clunky designed, cake of shit, requiring for real world applications to juggle with change detection services, change detection policies and control value accessors, which basically forces you to reinvent the most complicated wheel ever for what a ton of other frameworks already do out of the box without getting you bald from hair-pulling late-night hours.
Even AI can't fathom it. Give it to Copilot, GPT, Claude or whatever, and as soon as you get something more complicated than a form that sends a class to the backend or some mapping classes they will flip up, get all worked up and write completely utter shit that doesn't work.
I won't get into the projects details but I had to build some complicated UI and it has baffled me what fucking triple backflips I had to write to make some UI elements work smooth.
Jesus, why the fuck people keeps unleashing this pile of shit on me?
Why is it even used? There are a TON of healtier alternatives.
As of 2025, my christmas wish is still to have an 1v1 with angular devs in an octagon to shove my fist in their skull to check out what kind of twisted donkey shit is in there.
Seriously some improductive dumbass framework here, and if you like it, you're a shit programmer.16 -
Did devrant's backend downsize or something? I came back after a while and the whole app is like, 10 times less responsive, taking ages to load and respond etc18
-
"While a spectrum is defined as a function of frequency, a cepstrum is defined as a function of 'quefrency'. Quefrency is measured in 'time' and can be interpreted as a measure for time offsets of patterns in the time domain."
What in the actual fuck did I just read14 -
Lady next door was visiting me. She is 67. She is a kinda psychologist and she needed a new site. With her just sitting here, i generated one with gpt and explained her html a bit. The instructions are as follow:
- if you add a page, duplicate the other page and remove the text you don't want. Do not remove html unless it's around content what you don't use anymore.
- learned her how to copy a href and change the link.
So, first, she asked me for a website. The last thing I want is somebody's website in maintenance or even work on it. Making "beautiful"/commercial sites is not my hobby.
Now, for 1,80 per month she has a domain name (i asked if it will have SSL, that's still bit unclear) and 1,- hosting per month. I think it can be even cheaper. It doesn't support php/python and stuff.
TLDR; i gave someone a HTML site generated in 5 minutes, tried a few style sheets and she was happy with it. Bye bye designers :P No one cares! Also full responsive.16 -
Most expensive thing you ever bought?
I think I just bought about 20 seconds of relevant audio recordings for over 300€ 🙃
But hey, the virtual car has to sound good or whatever... totally not a painful investment...9 -
i dream of having a working dev and test environment
or being good enough to have my own stuff working
i don't go out of my way to fuck around with any of it, i just want to do my work, clock in, clock out8 -
Here is my idea for a time machine which can only send one bit of information back in time.
@Wisecrack has asked me about it and I didn’t want to write it in comments because of the character limit.
So here we go.
The DCQE (delayed-choice quantum eraser) is an experiment that has been successfully performed by many people in small scale.
You can read about it on wikipedia but I'll try to explain it here.
https://en.wikipedia.org/wiki/...
First I need to quickly explain the double slit experiment because DCQE is based on that.
The double slit experiment shows that a particle, like a photon, seems to go through both slits at the same time and interfere with itself as a wave to finally contribute to an interference pattern when hit on a screen. Many photons will result in a visible interference pattern.
However, if we install a detector somewhere between the particle emitter an the screen, so that we know which path the particle must have taken (which slit it has passed through), then there will be no interference pattern on the screen because the particle will not behave as a wave.
For the time machine, we will interpret the interference pattern as bit 1 and no interference pattern as bit 0.
Now the DCQE:
This device lets us choose if we know the path of the particle or if we want wo erase this knowledge. And we can make this decision after the particle hit the screen (that is the "delayed" part), with the help of quantum entanglement.
How does it work?
Each particle send out by the emitter will pass through a crystal which will split it into an entangled pair of particles. This pair shares the same quantum state in space and time. If we know the path of one of the particle "halves", we also know the path of the other one. Remember the knowledge about the path determines if we will see the interference pattern. Now one of the particle "halves" goes directly into the screen by a short path. The other one takes a longer path.
The longer path has a switch that we can operate (this is the "choice" part). The switch changes the path that the particle takes so that it either goes through a detector or it doesn't, determining if it will contribute to the intererence pattern on the screen or not. And this choice will be done for the short path particle-half because their are entangeld.
The path of the first half particle is short, so it will hit the screen earlier.
After that happened, we still have time to make the choice for the second half, since its path is longer. But making the choice also affects the first half, which has already hit the screen. So we can retroactively change what we will see (or have seen) on the screen.
Remember this has already been tested and verified. It works.
The time machine:
We need enough photons to distinguish the patterns on the screen for one single bit of information.
And the insanely difficult part is to make the path for the second half long enough to have something practical.
Also, those photons need to stay coherent during their journey on that path and are not allowed to interact with each other.
We could use two mirrors, to let the photons bounce between them to extend the path (or the travel duration), but those need to be insanely pricise for reasonable amounts of time.
Just as an example, for 1 second of time travel, we would need a path length about the distance of the moon to the earth. And 1 second isn't very practical. To win the lottery we would need at least many hours.
Also, we would need to build the whole thing multiple times, one for each bit of information.
How to operate the time machine:
Turn on the particle emitter and look at the screen. If you see an interference pattern, write down a 1, otherwise a 0.
This is the information that your future you has sent you.
Repeat this process with the other time machines for more bits of information.
Then wait the time which corresponds to the path length (maybe send in your lottery numbers) and then (this part is very important) make sure to flip the switch corresponsing to the bit that you wrote down, so that your past you receives that info in the past.
I hope that helps :)4 -
I am SOOOO tired of outdated, easily circumvented, methods of attempting to find rule breaking culprits...
especially when they can't even come up with anything more specific than 'suspecting' "unusual activity".13