Details
-
AboutOld Git. Remembers when "keep it simple, stupid" was a thing.
Joined devRant on 3/16/2023
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
-
At my new job I'm allowed to goof around more while at the same time less. Im no longer limited to tech and can just choose the best tool for the job and fuck around trying out new interesting stuff that might work. But at the same time IF I FUCK UP, you will definetly read about it in the news!12
-
Fucking hell! Why is it so hard to just create a simple websocket!
C#: Yeah, you should use ASP.Net with SignalR! But heres a totally undocumented mess of a lib to get it to work. J.k. Deadlock!
Rust: async while let OK((some)) = ws.create.unwrap_or_else().suckadick()
Why the fuck is Rust so fucking dense! I want one line that means one thing! If I would compress my code with gzip it would be less information dense than this!
Zig: Yeah, Its in Beta and shits semi stable. Atleast i got it to work? Nope!
I've ben fussing aound with these three Languages for more than a week now and can say: Just use an established way to webdev. Its not worth it to try and make it as simple as possible!19 -
Sleeping well cleans our mind and let us approach a problem in a different way and help us find the solution. For some days I was worried about how to solve a couple of bugs, but this morning after a good sleep I magically realized how easy the solution was:
WON'T FIX -
A fancy position opened up in a good spot, which I should be applying for. I want to. But this soul sucking place I currently work for has crushed me and I really don't see it in me anymore. The robots have more soul in this corridor than people.10
-
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 -
Trust your guts!
Just remember that your gut is designed to take the most tastey things and turn it into shit.2 -
apparently the ability to want to try something new is creativity...
the what. that bar seems too low?4 -
I didn't become a developer to be legacy's bitch. But we're all legacy's bitch.
I want to roam free. I want to piss in the rain and sing at strlen. I don't want to be in corporate meetings anymore.
I don't want to contort my ideas and good intentions to fit legacy's ugly painting.
I want to be free.
Please let coding be fun again.
I process more tickets than a brothel car park ticket machine10 -
Github Copilot is a dumb little shitstain
For the past years I've been trying to periodically give a go to various copilots every time they made an announcement like "our next version will replace programmers, it will make singularity look like child toys"
Unfortunately and unpleasantly, in 2025 copilot is the dumbest shit ever and even junior coworkers can produce better code.
I can make it do only bovine code like class mapping and simpleton tasks.
Delusional32 -
It's a new year. so everything stops working because tables don't exist for year 2025 in the database.10
-
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 -
The downsides of coding drunk: Implementing the same thing you've already implemented but forget you did13
-
you ever habituate yourself to reflexively do something and then forget you ever did that and don't even notice you're doing it therefore can't turn it off because you're too oblivious to understand the problem
and for amusement what is it?8 -
lesson of alcohol:
it doesn't matter how well you do just do and fix it later, if that even becomes relevant which strangely it somehow doesn't
it's like, full-frontal idiocracy but because you engaged in it you got smarter somehow
I'm slow at doing my sudokus now though so maybe when I recover more I'll figure it out more. think I found ballmer's peak last night and I'm gonna hopefully remember to successful steal this mindset
unfortunately turns out if I even so much as sip a low alcoholic beer my spleen inflames so that fucking sucks, so re-visiting the mindset to make sure I transferred it over to my sober state might end up tricky but hopefully I'll still keep this quest outstanding until the whole thing sorts itself out3 -
I am against the idea of outsourcing dev jobs.
Every software company should hire in-house devs, that live in the same country/region the company is in.11 -
Needed an application that generates data very fast for a networking application i'm writing but I did notice that /dev/urandom and /dev/random are not very consistent in speed.
Still, i needed something fairly random with more consistent speed. Now, I made an application that caches 1000 randoms upfront and use them for calculation. Now I have my own randomization algorithm backed by the uniqueness of the original rand(). For fun I added data in the set like some phone numbers. I can watch ages to the data to find smth in common or interesting combinations of the data.
I did verify with GPT is the algorithm is unique and it's fail. It generated a complete ML script for itself to check it. Very awesome.
You use urandom, i use retoordom. We are not the same.15 -
For the past 3 months I’ve been working on the frontend until recently the project was completed. Now I’m doing some backend stuff in dotnet, everytime I come back to dotnet I start to hate JavaScript2
-
Suddenly remembered that, at one point in time, every few rants here I would read something about wordpress, and how nightmarish working on this or that blazing dumpster funeral pyre was.
So, hot take: you deserve it.
I'm sorry wordpress devs, but you do. If the whole point is getting a site up and running "without extensive coding knowledge", then the whole point is not needing to hire a developer. You get that, right? These folks straight up tried to take your job, realized they couldn't, then came back crawling, and you accepted the offer right after getting spat in the face.
Mother fucker, have some self-respect. On both sides of the equation.
This foray into needlessly antagonizing my fellow programmers has been brought to you by RectSpace. Need to flip off Bertrand Wanker-Fuckfaceberg here and his dumbass fullstack chops? Just fire him! Bring your amateur pornovlog online TODAY with NO programming knowledge whatsoever -- you'll be sucking off webdeving limp-ass DICK in no time!
Use my promo code NEEDGULAG for 300% OFF your next romantic colonoscopy. That's cuadruple triple-double-long-u-int double-double-you dot dot dot nodecency-comma.io.com.ai to get PAID in CASH for 24/7 free parking inside your ASSHOLE. Big thanks to RectSpace for sponsoring this rant!14