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
-
Well it finally happened… I deleted the production DB 🤦🏼♂️
Rollback successful but lost over 3 hours of production data8 -
dev communities can be the most toxic as well as the most welcoming at the same time.
just depends on what your timing is. You can get a bunch of links to help debug your issue or you can get told to "kill yourself".
You never know.9 -
If ChatGPT calls my problem a "classic" or it's solution a "subtle quirk of <framework>" one more fuckin time I'm gonna be the first human to murder an AI9
-
We just hit the 1 million mark on the Stop Killing Games EU initiative! 🥳
https://www.stopkillinggames.com/53 -
In my latest installment of "Swift, WTF?", we look at the "if" conditional in terms of the Swift convention of:
if let x = y { /* ... */ }
so what this does :
1. declares x in the scope of the braced code
2. sets x to y (an ahem, "optional")
3. decides if x is not *nil*, then executes the braced code.
This is very similar in both the visual and the operation to the C code of:
if (int x = y) { /* ... */ }
1. declares x in the scope of the braced code
2. sets x to the value of y
3. if x is not zero, then executes the braced code
which is considered *exceptionally* poor style.
Neither the C nor the Swift construct result in a legitimate boolean value of "true" or "false", although C comes closer than Swift.
In the Swift case the *imaginary* "nil" value has to be interpreted as "false" and thus there must be extra code is for the conditional to check on whatever constitutes the **actual** value of nil in Swift and then set the condition to "false".
(remember boys and girls, "optionals" are not real, they are an imaginary language construct of Swift and have no legitimate counterpart in the CPU operations with memory and registers)
At least in the case of C, if the value of x is zero or NULL (which is 0) then it is technically a "false" which in C is 0. Regardless, it is really poor programming and anyone doing that on my team gets an ear full.
But in Swift this obfuscation of code is common and condoned! Well, why not put more of the program in the condition of the if? In fact, stuff the whole thing in there.. why not? 🙄
This just reenforces my opinion that Swift is not a bird but the stuff that comes out of the underside of the bird. 🐦💩30 -
when you end up in the ER with excruciating pain early on a Saturday morning from persistent inflammation from chronic job stress and getting sick more than normally, you gotta change jobs.
no amount of money is worth your health.
(the drugs they gave me were pretty fun though, but not something I ever want to go through again)6 -
Devrant not loading again... hit refresh... still nothing... is today the day it finally snuffs it?
Sigh with relief as the UI starts to load...
And there it is: a lengthy ode to the best pest control service in Hockaloogie, Alabama.
The natural balance of the universe has been restored.2 -
First name: Null
Last name: Null
Birthday: 1/1/1970
Email: one time email/ temp mail
Password: the email itself
This is how I register myself everywhere, usually works everywhere except for X (twitter).7 -
What kind of music are you listening to while coding?
Is it instrumental or lyrical?
Sometimes songs with lyrics districts me17 -
I hate deprecations! Adopted a web project that was actively maintained until 2023, how can it already be so "legacy" that none of its npm scripts work anymore?7
-
Am I in a toxic work environment or not?
1. I suggested implementing some code guidelines for our team so we can all work the same way. Lead architect sends me a DM telling me to stop talking about it until after projectX is done because it might stress out other devs. Friday he talks about how important it is to use standardised tools and ways of doing things.
2. Spent a week working on a bug fix and they said solution is good, but then invalidated all of my work by DM-ing me saying it's unusable because i worked on wrong branch and he quickly fixed it over the weekend and I should just copy his (inefficient) code.
3. I ask him a basic question of what version the backend software is using and he doesn't even respond. I ask another team member who quickly helps me check. it would have taken 1 fucking integer to answer that question. i wanted to learn the backend stack, but not so much anymore.
4. Lead doesn't respond to project management software ticket mentions.
5. Lead randomly makes hotfixes to the QA server without prior notice so the backend randomly goes down at times during work hours and then my local copy of the front end stops working for no reason at all when I am trying to focus on bug fixes
6. UX/UI designer's screen designs look completely different than the actual app, so I spent weeks implementing a feature looking like his nice designs, then having to change it again, taking another week.
7. Generally poor comms
8. Leadership mentioned jobs are safe, then 2 months later retrenched a bunch of people.
9. People getting sick all of the time.
10. Nobody gives a shit about technical debt22 -
Yeah turns out writing a shell is a whole lot more work than I thought
Fuck man, why can't I just find a cool project that is actually doable in a normal lifetime6 -
What‘s the purpose of separating your code into "independent" modules if each module contains everything anyways?6
-
Finally got paid (apparently they sent my money to the wrong account lmao).
So I bought:
- A Guitar Rig Kontrol 3. It's an old hardware designed for some specific soft, but it contains a soundcard, 8 foot switches, one expression pedals (continuus), 2 other expression pedals input, 2 audio input, 2 audio output. So I'll be able to plug my guitar and control FX from there. All of this for 50 euros at the pawn shop
Being a programmer helped me tremendously for electronic music because I can write actual drivers for old hardware.
- I also found an old bike on the street. Brakes and transmission, seat and tyres are fucked, but the frame and wheels seems healthy enough. I can get a decent bike for the price of parts and labour.5 -
spent the whole week working on a bug fix last week.
implemented a method to filter some data to make it easier to use in the HTML template.
friday's session with other programmers to review code went well, they said the method is pretty good and works nice. (I must admit there was an elusive bug that prevented the component to render and none of us could figure it out)
i get back on monday to a message from the lead saying the code is unusable and they reverted to the previous (convoluted) way of doing things and i should do the same in the future. just copy their work.
i check the typescript class. fucking method that was used (which he told me not to use and I should copy and work off of), he went and just changed the method's name, and the body is EXACTLY the same as his existing method.
this code base is ridden with re-used methods (I managed to extract two reused ones into a service some time ago), the use of any for 90% of method return types and variables...
WTF. I am losing all of my respect for seniors and faith in this company.
This is why I am burned out. You are farting against a hurricane and everyone else's shit is coming back onto you. This is fucking insane. Or am I insane?13 -
Sometimes, Google's solutions are worse than the problem they intend to solve.
For example, Google ReCaptchas are worse than spam, especially those with the pictures that fade extremely slowly on purpose. Unlike bots, humans are likely to not finish deliberately annoying captchas to save their precious time. (see http://archive.today/2022.06.25-110... )
In Chrome (mobile version), pull-to-refresh saves the one second it takes to reach for the refresh button in the submenu, but poses a threat of accidental refreshes each time you swipe down intending to scroll up. Over two thousand people have complained about this. ( http://archive.today/2025.02.26-153... )
With Android 4.4, Google blocked write access to memory cards (MicroSD) from all user-installed apps with the exception of app-specific folders so apps can not leave files behind when uninstalling. Google provided no option to change this. (source: http://web.archive.org/web/... )
But for unwanted files, there is already a delete button! Why take away the freedom to use the MicroSD card properly?
Google crippled the usefulness of memory cards for this nonsensical reason.
Google solved these problems with solutions that are worse than the problem.3 -