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
Search - "99 problems"
-
If you’re having SQL injection problems, I feel bad for you son, I got 99 tables but… fffffuck. Now i only have one ☹️4
-
Do you reckon there could be other rant boards out there? Developers can't be the only people with problems... AccountantRant? TruckieRant? PainterRant?
...PresidentRant? Oh wait, that's his Twitter...8 -
Social let's-help-female-programmers warriors piss me off.
The other day a massive email thread at work on how women are misrepresented in tech and how we need to help them and how using words such as "guys" is intimidating and generally patronising shit like "let's advertise jobs on websites like femaleprogrammers.com instead stackoverflow because there's too many white males on stackoverflow."
99% participants in this topic were guys.
One girl sent a message saying she doesn't want to be helped and she wants to know she has been picked for her skill and not filling in diversity numbers.
...would you believe she has been schooled on problems women in tech face by those lads too.
Like "woman, please... we speak diversity here"
So annoying....!!24 -
If you let me use your WiFi, I feel bad for you son.
I can see your 99 problems, and porn is definitely one!
😉😂😂😂😂7 -
Tunes throughout the work day...
Someone's interrupting:
Queen, Don't Stop Me Now
Working on same bug for hours:
Muse, Supermassive Black Hole
Merge Conflicts:
Jay Z, 99 problems
In the zone coding:
xzibit, Concentrate
All bugs squashed, deployed, going home:
Louis Armstrong, What a Wonderful World1 -
If you're having CSS problems, I feel bad for you son,
I got 99 problems that I fixed with 'z-index: 100;' -
A good boss gives you a few clear instructions and then doesn't meddle in your work.
A great boss does that, and also spends most of their time protecting the team from corporate fuckery.
99% of all bosses, though? You can't make heads or tails of their blabber, and the only way they can handle problems is throwing their team under the bus.4 -
Our project at work goes live in 3 weeks.
The code base has no automated tests, breaks very often, has never had any level of manual testing
will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.
We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.
Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.
We have no testing team, or qa team of any sort.
Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.
We don't use any file streams so everything is just shoved in the buffer on the server.
Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.
No one looks at the pull requests, they just click approve so they may as well push directly to master.
Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.
I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.
Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.
No one there understands css properly. Or javascript.
Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.
Our customer facing fe app is not dry because no tests so it was decided it was better this way.
Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.
Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.
Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.5 -
I got 99 problems and they are all bugs in my code. Then I apply a patch, and I have 112 problems. #devLife
-
So I live in the middle of nowhere and therefore I have a very limited choice of different ISPs. The short version of the choices is a fast but very limited in data size or one that works 99% of the time (I'll talk about the 1% later) but doesn't have limits on downloads. So I obviously chose the second one.
It works pretty great most of the time and I don't have any problems usually... The problem with "usually" is that the 1% of the time it doesn't work is all it needs to frustrate me. I could be downloading a massive file and around 70% the Internet decides to disconnect. It wouldn't really be a big deal if it wouldn't cause the file to get corrupted.
My point is that if you're going to share a big file, don't upload it to mega, mediafire, dropbox or anything like that. Just use torrents. They work way better for big files.2 -
If you're having merge problems I feel bad for you son, you've got 99 problems but my branch ain't one!1
-
Spent the last few days trying to solve a weird issue with our CI/CD pipeline for a project. Yesterday i finally gave up and told my coworker that i need a fresh set of eyes to look at this.
I leave for lunch, an hour later I'm back and brought fire and fury to the mix.. Then, 2 hours later i raised my hands and my mouth uttered the glorious words of victory: Fuck yeah, it works.
Mood was still shit though... 1 bug down, 99 life problems remain 😢 -
I never thought how hard it would be to write cross platform software. If statements and try/excepts are everywheeere. And I still need to reformat the strings for different aspect ratios.
I wish I had the balls to use this awesome sentence "Works on my machine" 😂 -
[CONCEITED RANT]
I'm frustrated than I'm better tha 99% programmers I ever worked with.
Yes, it might sound so conceited.
I Work mainly with C#/.NET Ecosystem as fullstack dev (so also sql, backend, frontend etc), but I'm also forced to use that abhorrent horror that is js and angular.
I write readable code, I write easy code that works and rarely, RARELY causes any problem, The only fancy stuff I do is using new language features that come up with new C# versions, that in latest version were mostly syntactic sugar to make code shorter/more readable/easier.
People I have ever worked with (lot of) mostly try to overdo, overengineer, overcomplicate code, subdivide into methods when not needed fragmenting code and putting tons of variables.
People only needed me to explain my code when the codebase was huge (200K+ lines mostly written by me) of big so they don't have to spend hours to understand what's going on, or, if the customer requested a new technology to explain such new technology so they don't have to study it (which is perfectly understandable). (for example it happened that I was forced to use Devexpress package because they wanted to port a huge application from .NET 4.5 to .NET 8 and rewriting the whole devexpress logic had a HUGE impact on costs so I explained thoroughly and supported during developement because they didn't knew devexpress).
I don't write genius code or clevel tricks and patterns. My code works, doesn't create memory leaks or slowness and mostly works when doing unit tests at first run. Of course I also put bugs and everything, but that's part of the process.
THe point is that other people makes unreadable code, and when they pass code around you hear rising chaos, people cursing "WTF this even means, why he put that here, what the heck this is even supposed to do", you got the drill. And this happens when I read everyone code too.
But it doesn't happens the opposite. My code is often readable because I do code triple backflips only on personal projects because I don't have to explain anyone and I can learn new things and new coding styles.
Instead, people want to impress at work, and this results in unintelligible, chaotic code, full of bugs and that people can't read. They want to mix in the coolest technologies because they feel their virtual penis growing to showoff that they are latest bleeding edge technology experts and all.
They want to experiment on business code at the expense of all the other poor devils who will have to manage it.
Heck, I even worked with a few Microsoft MVPs.
Those are deadly. They're superfast code throughput people that combine lot of stuff.
THen they leave at you the problems once they leave.
This MVP guy on a big project for paperworks digital acquisiton for a big company did this huge project I got called to work in, which consited in a backend and a frontend web portal, and pushed at all costs to put in the middle another CDN web project and another Identity Server project to both do Caching with the cdn "to make it faster" and identity server for SSO (Single sign on).
We had to deal with gruesome work to deal with browser poor caching management and when he left, the SSO server started to loop after authentication at random intervals and I had to solve that stuff he put in with days of debugging that nasty stuff he did.
People definitely can't code, except me.
They have this "first of the class syndrome" which goes to the extent that their skill allows them to and try to do code backflips when they can't even do code pushups, to put them in a physical exercise parallelism.
And most people is like this. They will deny and won't admit, they believe they're good at it, but in reality they aren't.
There is some genius out there that does revoluitionary code and maybe needs to do horrible code to do amazing stuff, and that's ok. And there is also few people like me, with which you can work and produce great stuff.
I found one colleague like this and we had a $800.000 (yes, 800k) project in .NET Technology, which consisted in the renewal of 56 webservices and 3 web portals and 2 Winforms applications for our country main railway transport system. We worked in 2 on it, with a PM from the railway company.
It was estimated 14 months of work and we took 11 and all was working wonders. We had ton of fun doing it because also their PM was a cool guy and we did an awesome project and codebase was a jewel. The difficult thing you couldn't grasp if you read the code is if you don't know how railway systems work and that's the only difficult thing.
Sight, there people is macking me sick of this job11 -
In our middle schools' science-type after school program we got a client from a hospital. We interviewed her on what kinds of problems she had in her workplace. She talked a lot about impaired vision and such. Most people were doing stuff like button extensions for people who can't feel well. I'm creating a NN for recognizing numbers. I trained the model to 99% accuracy and got to teach my friend about GitHub! Win win!2
-
Seeing just how well ansible works to set up Arch is kinda scary, i wrote my playbook almost a year ago and it still works perfectly (after i renamed some packages)
And this is not even how you are *supposed* to use ansible, i am kinda abusing the system by only running it locally...
This is just reinforcing my Bash-hating bias even more: bash scripts are a terrible solution to 99% of problems, and the language is frankly shit.
Back to Ansible.
The fact that operations are idempotent is *such* a game changer, too: I can just write some extra roles to automate other stuff i can never remember, like setting up those darned wine/Lutris dependencies