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
-
Meeting with asshole partner company CEO at restaurant.
Me: "I'm a bit worried about the bugs in your API. There are some ways to retrieve privacy sensitive info from public endpoints"
CEO: "Well, we're a rapidly growing startup!"
Me: "Uh... so?"
CEO: "So... Move Fast and Break Things! Priority is to improve our API further, and we'll fix bugs as they show up"
Me: "Maybe you should stop trying to emulate Zuckerberg in your management style. You know that even Facebook themselves admitted that their slogan was a retarded mistake"
Waiter shows up at table. CEO orders some overly expensive fish salad.
CEO: "Well, they have done something right... they're worth billions"
Waiter asks me: "And you sir, have you made your choice?"
Me: "Do you serve popcorn?"
CEO: "Popcorn for lunch?"
Me: "No, for your congressional hearing"16 -
Boss: make this thing
Me: yeah no worries. Where is the spec?
Boss: We don't have enough one but we outsourced the design so call him
Designer: haven't started yet
Me: excellent
Boss: I'm going on holiday. I'll leave this to you.
Me: erm ok. I'm having a few problems getting stuff out of the designer though.
*2 weeks later and still no designs*
Boss: I'm back. Where is the progress?!
Me: indeed.
*1 week later i get half designs that sort of make sense*
Boss: hurry up!
*1 week later*
Me: designer you're busting my balls here
Designer: yeah lol
Me to boss: still having problems. No idea what I'm doing.
Boss: deal with it
*2 days later*
PM: we are demoing it to clients tomorrow
Me: brilliant. I'll become a magician then.
* Meeting goes well and no one notices the thing is a bit buggy*
*2 days later*
Me to boss and pm: you already know whats going on but I'll keep trying.
Boss: ok it's just a proof of concept anyway.
Designer: yeah here's the rest of the designs lol
*1 week later, the designs made no sense, no idea what they wanted but hey it's a proof of concept so I'll just do my best...*
*suddenly again, hey you have 1 week before we sell it. Lol. smashes a product together as fast as humanly possible, due to half designs and no time to do it right even html classes and CSS aren't right - didn't know things would be repeated at the time. No time to fix entire thing. Luckily just a proof of concept*
New senior developer: hey boss just said this is being sold tomorrow.
Me: wtf..It's a proof of concept and i was given longer...
New senior developer: no
Me: :(
Senior developer and all colleagues: it's full of bugs and doesn't work
Me: yes that will happen without specs, random tight deadlines, no designs that made sense and a total of about a week and a half to make an entire system for multiple user types to make applications, send messages, post jobs, handle all paperwork and move paperwork among different user types as they go through applications. I told everyone what was going on but i get no support...
*Silence*
Boss: wtf i gave you so long! All i know is my entire staff is working on a product that should be done ages ago
Me: ok, however i have said almost every day i need-
Boss: I'm not interested
*I finish my placement year and never get any promised work or the job offer*
Seems legit?16 -
I greeted my staff this morning with the phrase
"Morning, mind if I ruin your Friday?"
They laughed, but won't be soon enough. The task we've been working on for weeks, ripping apart the codebase changing it to work a different way, fixing a tonne of bugs, making it faster and simpler to add features too. Well business has decided they want us to stop, undo it, spend a month on something "with higher ROI" and then finish it off after that.
Business are expecting this to have no impact on any of the timelines and just to be like flipping a switch. Now obviously I won't let that happen and fight back for more time, but yet another session of compromises, arguments, and yelling. YIPEEE!!!!!!12 -
Dev: Ok issue fixed, you just need to log out and back in again on your end to receive the fix
User: It’s still not working
Dev: Did you log out and in again?
User: No why would I want to do that?
Dev: It’ll reset your locally saved login information which is causing the issue
User: I thought you said the issue was fixed?
Dev: On our end yes, we just need you to reset your end in order to receive the fixed version
User: Look I have been dealing with this issue for 6 months. Fixing bugs are your responsibility. I have too much to do, you have to get this fixed. *click*.
Dev: Yeah you submitted the bug ticket yesterday night though
Email from users manager later that day: <User> is saying you are refusing to fix this bug. This is unacceptable. Fix it or else I will escalate this. Also there are other bugs we noticed today too, fixing them is absolutely critical!
Dev: …
Dev: What other bugs did you notice?
*no response for 2 weeks and then:
User: Hey you can close this ticket, the issue seems to have resolved itself.
Dev: ….muppet.17 -
Mom : why were you late?
Me : Got lot of bugs in office.
Mom : Is everyone alright? Did you kill them?
Me : No mom we fix them.
Mom : I thought we kill them.
How humane are you guys.9 -
Newspaper: This CEO is one of the top entrepreneurs in the country, a true tech visionary shaping the future.
--- 3 months previous ---
Lead dev: O2 have said they are will pre-install the app on all their Androids but they need documentation from us.
CEO: documentation? on what?
Lead dev: Our unit test coverage, bugs found / fixed, security scan results, performance assessment, if and where its storing any data etc.
CEO: Ah were not doing any of that crap, bloody unit tests, its not necessary, tell them no.
lead dev: ..... eh ok
O2: *approved*
... true visionary, well done to everyone involved.3 -
So... I wanted to share something I made this weekend... 😁😁
Made an ls program which includes colors and icons! It is a work in progress and probably contains some bugs here and there, but I really wanted to share with you all.
The happiest thing to me about it is that I made it in pure C and had a blast creating it! It’s my first actual C project and it also made me realize that there is probably no language I can love more than C.
Take look if you are interested and tell me how it is 😊 suggestions and fixes are more than welcome 😁
https://github.com/Electrux/...
Just wanted to share the experience. Have a good day everyone! 😁
33 -
Seen on a lottery commercial:
Guy 1: That can't be right check it again.
Guy 2: Computers can't be wrong, they're programmed that way!2 -
I spent about 5 hours today coding and I was totally in the zone. I'm talking things were working properly, tests were passing, bugs were being squashed all over the place. It was completely amazing, I felt like a god ruling over my code kingdom.
After about 5 straight hours I realized that I needed food so I got up, stretched my legs and had some dinner. Well I sat back down about an hour ago and I am SO far out of the zone. Everything is breaking, I can't focus and I have no idea why. My kingdom was overrun with a plague of bugs in just the short time I paused to eat.
Moral of the story: when you get in the zone don't stop for anything even if it seems like basic human necessity. After all we aren't human when we're in the zone, we are coding gods.5 -
Me: Boss, your new project is ready, we've tested the technical aspect but we're waiting on your approval before deploying, will you test it?
Boss: yeah sure, I'll test it in 5
*2 weeks later*
Boss: why isn't that project deployed yet?
Me: you haven't tested it, and we haven't gotten approval
Boss: oh right, I'll go test it right now!
*2 weeks later*
Boss: I NEED that project to go live RIGHT THIS MOMENT!!!
Me: sure, have you tested it yet?
Boss: nope, but I need it
Me: well, I'll put it live, but me and my colleagues are shifting responsibility to you, since you haven't tested it. Are you sure?
Boss: yeah, yeah whatever...
*put product online*
*2 days later*
Angry call from boss, bugs have been found, tell him that he approved the state of the product and that the bugs will go on the to-do list...
Boss is extremely pissed, but recognized his mistake...
Now, the boss actually tests everything thoroughly at the moment we tell him to! No more bugs, complaints, and I got a raise!5 -
Most of the code I write nowadays is for GPUs using a dialect of C. Anyways, due to the hardware of GPUs there is no convenient debugger and you can't just print to console neither.
Most bugs are solved staring at the code and using pen and paper.
I guess one could call that a quirk.11 -
Answer from 3rd party software company: "we can't fix these bugs because it requires development on our side".. hehe, yeah, no shit 😂4
-
when you have to do this because the code looks correct but you're not sure what the heck is wrong because it doesn't make sense
12 -
Senior Dev: "-bleep- I hate Javascript. It is such a pain to have to debug in Chrome"
Mgr: "Why are you 'having to' debug in Chrome?"
-in an almost 'you didn't know?' condensing tone -
Senior Dev: "Because you can't debug Javascript in Visual Studio."
Me: "Umm...pretty sure you can."
Senior Dev: "No, its impossible. I have to make a simple change in Visual Studio, save it, deploy all the files to the server, restart IIS, open up Chrome and use it's developer tools to find bugs. -bleep- Javascript sucks sooo bad."
-I do a quick search on stackoverflow-
Me: "No, I'm looking right at it on stackoverflow. You can debug Javascript in visual studio just like anything else."
- Mgr looks over and smiles, not trying to laugh -
Senior Dev: "Hey, did you watch that scene in Stranger Things...man thats a good show ..."
- other devs jump in to comment about the show, completely dismissing the VS/Javascript conversation -
Not sure WTF just happened.9 -
Always the same story:
Marketing: hey I'm gonna do a demo to a customer. They were asking for feature XYZ. That's ready on thr staging server right? Do you think I could use the staging server for the demo?
Devs: well feature XYZ is not 100% done. Basically just feature X is done, and it still has a few bugs. The deadline ain't for another month, since we gotta finish ABC first. I guess you could use the staging, but it has a lot of bugs.
Marketing: perfect!
*after presentation*
Marketing: the staging had so many bugs! Why didn't you tell me?! It was so embarrassing showing it to new customers! Anyway, they loved the new feature. We need it to be ready ASAP.
Devs: What?! That's gonna mess up with our schedule. You know what? Fine, but feature ABC will have to wait another month.
Marketing: Well, it'd be ideal if we could do both...
Devs: Pay for more devs or dor extra hours.
Marketing: Just do XYZ. It's a pity that you'll have to push back ABC but it's fine, XYZ is more important.
(I might ask, if it was so important, why didn't you notice so in the meeting where we had decided that ABC would be prioritized?)
*tons of working hours later*
Devs: There, we finished XYZ.
Marketing: Yay! Wow, this month we'll have two major features done: ABC and XYZ!
Devs: No, ABC is not done yet.
Marketing: What? But the deadline was this week.
Devs: It was, but then you decided to prioritize XYZ and we said we had to push back ABC to get XYZ ready, and you agreed.
Marketing: Did we? Fine. But do it quick.
Marketing and their mood swings.6 -
Alright, the blog seems to be running again and its not breaking yet which is a good sign :P.
Although nothing has changed on the front end yet, the backend has been partly rewritten to be more efficient and of course, post sorting based on posting date!
I'm aware of most of the front end issues so no need to tell me all of them again, I'll look at that tomorrow as I need sleep right now :(
If you'd find any bugs/security issues, please, don't exploit them but report them instead! I take security very seriously and will try to patch any security bug as soon as I can :)13 -
- there is a bug in the code.
A: I have searched everywhere I can't find the bug
B: What was the last thing you wrote?
A: I called this function
B: did you check the function for bugs?
A: no, I just coded it, there can't be any bugs there3 -
Me: Can I have PhpStorm please.
Company: Is it free?
Me: No, but it's the best php IDE out there. It's a huge productivity boost and also helps avoiding bugs while refactoring.
Company: Nope. Use Zend Studio 9.
Me: Why?
Company: We paid money for it like two years ago.
Me: <contemplating life and my decision to ever work there>
To whomever it may concern: Zend Studio is the commercial brother of Eclipse PDT, which also is one of the most shittiest idea out there. Almost as bad as Netbeans for php.
You have all the problems you had with eclipse, and none of the features of phpstorm. Zend Studio does not help you to get work done. It is a constant hindrance, everything you achieve you achieve despite its usage.19 -
No boss... For the fucking millionth time: unit tests are not a waste of time.
You keep testing everything manually and hoping that you tested everything every time and praying that there are no bugs IS THE FUCKING TIME WASTE
My boss just can't fucking wrap his head around automated tests... I'm trying hard... Gonna try harder...6 -
Support: A customer complained about a nasty bug.
Senior Dev: There are no bugs in our software, just challenges that need to be solved.2 -
Today is a big day!
I have officially no bugs on my list for the last 40 minutes after 8 months!
.
.
Celebrating and drinking shall... Fucking thing crashed... -_-3 -
No matter how much product owners claim "bugs have priority over anything else", "we value high quality structured code", and "we do test driven development"...
...Once a big client wants a feature to be developed before they sign up, dirty code will be written from napkin specs, and that code will always be refractored "soon".4 -
The worst kind of bugs are logical ones, they go undetected, no error, no alert, and when you notice them, it's too late.3
-
Suddenly it hits me.
It’s 01:20 here but i get it.
It’s ALL a budget thing.
No dedicated tester means less expenses.
No personal parkspot?
No expenses!
And no good staging or testing environment? Less expenses!
Meanwhile every developer can setup, work on, and maintain about 20 websites on their shitty local Windows machine, that doesn’t even have a proper SSD installed, and we are setting impossible deadlines to figure out who will sink and who will swim.
Ow, here is a SSD.. Figure out the installation yourself because we have no IT knowledge or budget for people that do.
You want a challenge? How about 40 other people that are distracting you all day long.
Meanwhile everybody has to improve their skills in js, react, html5, ccs3, angular, .net and razor so money can made faster.
It would be nice if you could build apps as well.
You had a question? Sorry, no time. Expect some feedback 14 days later.
You finished the site?
Great!
But here are 101 bugs to solve before next week.
All hail their crazy company!2 -
I just had a rather stressful morning. I should've known something was up by the sounds of thunder as I walked into the office.
I sat down and checked my emails. There was an email from the boss who was away on a business trip. The subject read, "CRITICAL BUG" and my name was mentioned. "Great...No time for coffee", was my first thought.
I began searching commits to see when and how the bug came to be. "SHIT! It was my fault", I said aloud.
(A bit of backstory, I am Irish, working in Germany with a B2 level of the German language.)
I now had to communicate the problem quickly with a senior developer who is Russian. He can't speak English well and I would not expect him to speak it. We are in Germany after all. I tried my best to communicate the issue, but I found it so difficult to understand his German in a Russian accent. Normally, in the office I speak German except when it is urgent and I must explain a problem in greater detail through English. I got past that obstacle, however, the real challenge of fixing the bug awaited.
After 2 hours of coding, I had a solution and committed it to the master branch. All the while, I had been replying to the bosses emails with updates, probably with many grammer mistakes.
We have no dedicated testers here and the code is written in a way which makes it very difficult to test (i.e. it was written many years ago). When I had initially written the code, I tested rigorously and found no issues.
Just needed to rant. I need a coffee break now...4 -
Apple products are fucking trash, I don't give a shit if you have money to waste, but don't fucking brag about how superior your 3000$ excuse of a fucking laptop is the best laptop in the world when you could easily afford a desktop with 2 1080 GTX in SLI for that price.
"but mac has lyk no bugs, its so good"
NO FUCKING SHIT, THE OS IS BUILT WITH THE HARDWARE USED IN MIND. THEY DON'T BUILD 500000 MODELS OF MACBOOKS, THEY JUST HAVE TO MAKE ONE MODEL WORK, AND ALL OTHER LAPTOPS WHO HAVE THE SAME HARDWARE WILL.
This is fucking ridiculous.
That's like designing a site, but only for Firefox because that's the browser you use and you expect everybody to use that browser. Obviously it'll work fine on your machine.
I am so fucking sick of Apple fan boys.
I am fully aware some of you devranters are apple fans, but this has been something I've wanted to say for ages, albeit i'm a little late to the party.
Stop wasting money on overpriced trash.28 -
A year ago I posted on here that I had been working on a game using xamarin for 2 years as a hobby project. Back then you guys encouraged me to publish it.
A year later, I have done just that. I put it on play store for free. No ads. No monetization. Feel free to check it out:
https://play.google.com/store/apps/...
Feedback is always welcome.
It isn't a graphics heavy game. More of a strategy clicker.
Also, still some bugs I need to iron out.6 -
"As a team, we have the shared responsibility to ___".
(replace with ALL of the following: resolve bugs, do junior's code reviews, clean up dead code, keep the kitchen clean, improve test coverage, write documentation, order coffee beans, etc)
NO. JUST FUCKING STOP RIGHT THERE. Shared responsibilities do not exist. A single person is responsible, and can optionally delegate tasks.
EITHER I DO IT AND I'LL BE FUCKING AWESOME AT IT, OR SOMEONE ELSE DOES — BUT I'LL SLAP SLACKERS IN THE GENITALS WITH MY KEYBOARD.
Fucking startup hipsters with their community driven attitude, this way no shit gets done, ever.7 -
Just finished my internship.
I entered knowing nothing and spent the entire year on solo projects.
My company does not use any frameworks because "they don't want to run code on a server that they didn't write", they use waterfall, only use version control on half the projects, use notepad++, never once even glanced at my code to check I know what I'm doing - even when i asked.
Also have never heard of a code review, have absolutely no QA in place other than the devs making it and quickly testing it visually, no requirements gathering - just pictures and have never heard of tdd.
Recently was given a project with no designs, no specs other than a verbal half thought out explanation and was dumped with random deadlines like "this needs to be demoed tomorrow night" with no idea about the project progression or what it looks like. Apparently it's all my fault that it failed.
I am very grateful to them for teaching me so much and giving me opportunities to teach myself on nice projects but come on.
What boggles my mind is that the company is 6 years old and has big, big clients. I don't understand how. I once tested a project about to go out the next day that had been "tested" and found pages of bugs. They would have lost the contract for sure...8 -
Staring at cursed blinking cursors.
Repairing work of worst thinking workers
Reverse merges or it'll murder the servers, it nurtures despair
Amateur managers, dimwitted savages interrupt all of us janitors
Cleaning up damages, spills and experiments using skills in embarrassment
Explicit foulness, in a minute it's straight to the bowels with weapons of limitless vowels
A bittersweet hateful machete, eviscerates stateful spaghetti
The slow disease flowing from keys knowing it's going to please
The growing unease, no one agrees, there's no guarantees with your useless degrees
Need more drugs, keyboard's crawling with bugs, falling as I chug
A bottle of cognac gotta love all the hacks, no poise for code that lacks
All the noise, gotta relax, before I destroy the syntax.
Excuse me for not making sense.
Too gloomy, aching and tense.10 -
Out of all the bugs, the most annoying are the ones that come out and make me say "WTF?!?!? WHY THE FUCK HAS IT BEEN WORKING FOR THE LAST 2 YEARS??!!?!!??? THERE"S NO WAY IT COULD HAVE!"
When the bug surfaces, you investigate and see that it indeed IS a bug and there's no way it would ever work w/o a fix. But then SOMEHOW it's been working just fine for years....
It's like server elves went on strike and said "no more, it's enough covering that bug - it's time you fix it, lazy-ass idiot!"11 -
Recruiter:
... the bank purchased a 3rd party tool and hired a 3rd party development team to add some features to the tool. That external team hired their own 3rd party team, and now there are 400+ bugs in the system. Would you like to work as a test-automation lead on this project?
Me: Fuuuucck no.5 -
Another real-world argument for why I always say git is worth learning properly.
Had to track a really weird bug down today. Had no idea where it came from, how long it'd been in the code and hadn't the foggiest what was causing it. Realistically it could have been introduced any time in the last year or two, and that's tens of thousands of commits in this repo.
Git to the rescue. Knocked up a quick script to test the case in question, fed it into "git bisect run", and 30 seconds later git found the exact (small) commit that caused the issue.
It's a brilliant part of git, yet it seems like almost no-one I know uses it. Some use "git bisect", but using "git bisect run" and passing a script to it seems to be alien to most - yet it's probably my most used tool when it comes to tracking down bugs like these.8 -
Programs are like humans. First you need to do baby steps and make it work like you want it, and teach it how to work. Then after the release the youth brings a lot of bugs and swearing. Finally it's grown up and can handle itself. Then it gets old and no one are so attracted to it anymore. It rests in peace on a old storage drive, and gets replaced by a new generation. 👶🏼👦🏽👨🏽👴🏽1
-
My preciousssss!!
Fucking assholes! Just spent 3h debugging for bugs that weren't there.. Our client insisted we must rollback the whole update, because gui was broken.. after analysing data & testing I figure out that there must be something 'wrong' as there was no data to copy from in the first place...so there should be no bug..
Aaand here goes the best part: they didn't want to point out missing data bug, they just wanted one restriction to be removed, because it 'broke GUI', to allow for empty value on save... WTF?! How can you insist that gui is buggy & that you don't want an update, if you just want something to be optional?! Which was done immediately, one change in one js file?! Dafaaaaaq?!
Kids, English is important!! Otherwise you end up debugging ghosts for 3+ hours withou a cigarette...and waking up a coworker with bad news of rollback at half to midnight... Aaaaaaaargh!!!
сука блять
27 -
Okay so this happened ages ago (nearly five years) but this suddenly came to my mind again.
It was in the first year of my study (currently in my 5th and last year).
I was experimenting around with php and mysql during some free hours. All the insert,delete and so on statements worked perfectly find except for one update statement. Started to debug of course and after a little while of no results I was like "oh yeah right, something like logs exists of course". Looked in the logs but nothing. No matter how I altered my code (rewrote it numerous times for some 'clean starts') it just would not run the update statement.
Alright, time for some class mate help. After multiple hours of debugging with a few classmates, there was still no result at all.
Time to bring in one or more teachers. After hours of debugging, still no result even with the help of a few good teachers.
Decided to give it a rest for that day.
Two weeks later it still was not updating anything/working and I finally gave up.
Till today, I still have no clue what went wrong and it still bugs me from time to time :/4 -
So I've got this raspberry pi 3 and no inspiration what to use it for.. and it bugs me, just sitting there taunting me: -"you aren't very creative are you?" So.. ideas and suggestions?21
-
Most toxic work culture ?? oh boy where do I start.
Getting verbally abused and physical threats over bugs found in production.
All kinds of office politics going around where everyone openly admitted not liking others in other departments.
Your day's salary gets taken away if u are late by even 1 min. And no overtime pay and no you cannot say no to that either or end up getting laid off.
Company brags about giving their employees their salary on time.
Only the devs who have lasted more than 10 years in the company will be heard.
After so many job switches I managed to find one where I get to WFH and pretty much face no toxicity from others.8 -
So we ordered a piece of software from external software house becouse I was low on time and we needed it asap.
So. Long story short, their software was bugged as hell, they deny all the bugs and they have their BDD that they done and anything we say about it like "feature XYZ is broken on firefox" they will deny it "becouse it wasn't on BDD" or "let's get on call" (in which +- 6-7 people participate from their side and we of course have to pay them for this...)
So they fixed like 20% of bugs (mostly trivials/minors) Application is fairly small scope. You have integration with like 3 endpoints on arbitary API, user registration/login, few things to do in database (mainly math running from cron).
They done it in ASP so I don't know the language and enviroment so can't just fix it myself.
2 days ago (monday) they annoyed me to point where I just started to break things. For starters I found that every numeric input is vunrable to integer overflow (which is blocker). I figured most of fields are purefect opportunity to XSS (but I didn't bother to do JS... anything but not JS...). I figured I can embed into my name/surname/phone (none validated) anything in HTML...
So for now we have around 25 bugs, around 15 of them are blockers.
They figured it's somehow our fault that it's bugged and decided to do demo with us to show off how perfectly it works. I'm happy to break their demos. I figured I will register bunch users that have name - image with fixed/absolute position top:0;left:0 width/height 100% - this will effectively brick admin panel
Also I figured I can do some addotional sounds in background becouse why not. And I just dont know what to put in. It links to my server for now so I can freely change content of bricked admin panel.
I have curl's ready to execute in case they reset database.
I can put in GIFs or heck, even videos, dosen't really matter. Framework escapes some things for them so at least that. But audio/image/video works.
Now I have 2 questions:
- what image + audio combo will work the best (of course we need to keep it civil). Im thinking finding some meme with bugs or maybe nuclear logo image with some siren sound
- am I evil person?
Edit:
I havent stated this clearly:
"There is no BDD that describes that if user inserts malicious input server should deny it" - that's almost literally what we get from them....11 -
"Why does my app have so many bugs!?"
"Why does literally nothing work!?"
"How come you cant fix these problems soon enough?"
...
Me: "remember how you didnt account for testing in the budget or development plan?"
"No"
Me: "thats why."2 -
CEO of previous job, only reachable by email, coming to the office twice a week at best, business trips at no notice, answers every third email, addressing the dev team:
"You need to plan better. A lot of the delays and bugs are due to poor communication and unaddressed issues."
I don't miss that job.1 -
Moving away from technology and becoming self-sufficient. A cottage with a stream on the edge of a forest, a large garden, some chickens and other animals, and no smart devices, managers, tickets, KPAs, performance reviews, legendary devs shitting out an endless stream of bugs, etc.
Peace and quiet.
And freedom at last.
That’s success.
That’s the ultimate success: escape.13 -
Me: We should use typescript to enhance our readability and productivity.
Senior dev: No... We don't want to use any other languages except JavaScript.
(A month later)
Too many catch, race conditions and hidden bugs left. 5 hours of debugging16 -
Salesman: "The new version is super impressive for <10 minutes of verbal bullet points>"
Me: Have you fixed any of the bugs we reported in the current version?
Salesman: "Don't worry, the new version uses a totally new codebase, so there are no bugs in it."3 -
Going live on Friday afternoon.
- no way, too many critical bugs! - I said
- we will - the Key account manager said.
Friday is here, still many critical bugs, I was right, it's impossible.
The Key account manager just dropped all functionalities with critical bugs and tricked the customer into thinking it's ok.
So we go live.
He was right, we can.
Oh yeah.6 -
There is no such thing as finishing a successful project, there is always a broken piece. By fixing that piece, you break another.
Most of our time, we break stuff.
9 -
Happened at work a few months ago (I'm new to devRant, that's why I post this now):
"I have bugs!" - "Then fix them..." - "No, come here and have a look, I have bugs!"
He literally had a bunch of very small insects inside of his monitor, don't ask me how they got there.1 -
my boss asked me to join a xamarin project, there are 45 bugs on current sprint. the first thing i saw is this code, no wonder there are so many bugs 😭
5 -
Twitch Developer Rig sucked hard and was cropping my extension down to 300px high no matter if it was “panel” which should be this high or everything else.
So I posted to their forum and they committed a fix MINUTES later.
That’s how you deal with bugs. -
LPT: NEVER accept a freelance job without looking at the project's source first
Client: I have a project made by a company that is now abandoning it, I want you to fix some bugs
Me: Okay, can you:
1) Give me a build to test the current state of the game
2) Tell me what the bugs are
3) Show me the source
4) Tell me your budget
Client: *sends a list of 10 bugs* Here's the APK and to give you the project I'll need you to sign an NDA
Me: Sure...
*tests build*
*sees at least 20 bugs*
*still downloading source*
*bugs look quite easy to fix should be done under an hour*
Me: Okay, so, I can fix each bug for $10 and I can do 2 today
Client: Okay can you fix 8 bugs today for $40??
*sigh*
Me: No I cannot.
Client: okay then 2 today for $20 is fine, I want a refund if you can't fix them today
*sigh*
Me: Look dude, this isn't the first time I am doing this, aight? I'll fix the bugs today you can pay me after check they are done, savvy?
Client: okay
*source is downloaded*
*literal apes wrote the scripts, commented out code EVERYWHERE
Debug logs after every line printing every frame causing FPS drops, empty objects in the scene
multiple unused UI objects
everything is spaghetti*
*give up, after 2 hours of hell*
*tfw averted an order cancellation by not taking the order and telling client that they can pay me after I am done*
Attached is an image of a level object pool
It's an array with each element representing a level.
The numbers and "Final" are ids for objects in an object pool
The whole string is .Split(',') into an array (RIP MEMORY BTW) and then a loop goes through each element in the split array and instantiates the object from an object pool
5 -
1) bugfixing
2) bugfixing
3) bugfixing
No, seriously, I love finding & fixing bugs.. it never gets old..frustrating at times yes, but it is never boring..4 -
How to piss off a developer?
1) Make your SDK bundled with an IDE and provide no way to update only the SDK, forcing them to loose all of their IDE settings and customizations.
2) Make GNU tools bundled in the SDK that are compiled 10 years ago and haven't been updated.
3) Provide a Linux version of the SDK, but only save all files in Windows-style line endings.
4) Provide SDKs that introduce bugs and break builds.
5) ???
6) Profit!6 -
What do you do when another dev overwrites/changes your working code without telling you, only because s/he cannot understand how your code works?
And your code was working fine, mind you, no bugs or anything, and is following recommended guidelines/standards. It's just that this other dev has a different coding style and prefers to rewrite everything his/her way even if it means breaking up otherwise sound logic.7 -
My nipples are hard, as hard as diamond. For no fucking reason at all.
But aside from that important update, does anyone just get this absolute light-headed euphoria whenever they realize they've fixed a bug?
Like my god, its the best feeling. I've only fixed other people's bugs a few time, and even then I experienced it.13 -
I just joined a team that is tasked with developing a robot that plays soccer. It was a lot of fun until I found out that someone in the team has been developing a full framework / rtos from scratch because existing rtos solutions were "not good enough".
I tried blinking a led with it today and found more bugs than I can count...
Oh, and there are no docs...8 -
My ex-boss who had 35 years of experience in IT Industry, didn't know one single fucking coding language, obviously had no clue about source control or anything even remotely related to computers, and had been project manager of a project having over 1 million lines of totally undocumented code split into 389 files with no apparent structuring. All variables were either alphabets or names of programmers who developed them.
Code was in Python 2 and had bugs/line ratio ~= 5.
He asked to write a 'wrapper' class and somehow run it in Java and fix all bugs automatically. (insert Shia LaBeouf's magic GIF here)
When I said it doesn't make sense, he said you should put in hard work and do it, and not give excuses.
Time given to do this - 1 hour :-P
Good thing I quit that shit place and that pathetic moron. Love my new job and life! :D
Seriously managers should trust their developers and allow some degree of freedom. It helps a lot.4 -
Got a few Jira tickets reassigned to me because the dev who was supposed to work on them got stuck on another project. It's fine, that happens.
I open the tickets. No descriptions for all of them. No screenshots for those reported as bugs, nor any replication steps. No attached test cases or, well, ANY useful information.
I talk to our BA, he says that all information I need are in OTHER tickets on ANOTHER BOARD that business manages but I DON'T HAVE ACCESS TO. Honestly, these shitfucks could've just done simple copy/paste. But nooooo...
So I reassign all the tickets back to their original reporters (business testers) with comments requesting more information.
It's been a week. Now I have no idea what to put in my time sheet.1 -
Client : We want to develop this particular software. While developing it, we will be following Agile methodology.
Developers: Sure.
After developer achieves few features and decides to give 1st Demo of the software to the client.
Client : Wtf is this? This is an incomplete software, there are bugs in it.
Developer : Yes, you point that out to me and I will solve them.
Client: What do you mean point them out for you l, couldn't you do it yourself?
Developer: As a standard method, we often do unit tests, but we are not testers and with a strict deadline to match, we are more on the core implementation then checking again and again for minor bugs.
Client : I thought it would be a full proof software without any bugs in the 1st demo.
Developer : Software development is a process. It's not straightforward, hence you only mentioned at the initial, it's agile.
Client : If that's so, let's make it not agile and make you rot in hell for the next few fays. Now you next time show me a demo with no bugs, great complicated features and we will not mention you our expectations, predict them by yourselves, and most importantly, here's an impractical strict deadline.4 -
Let me get this straight. I don't have a paid Apple Developer account so I can't report iOS 10 bugs?
Anybody want to report a bug for me that double clicking the home button no longer launches Apple Pay from the lock screen?12 -
Fucking lazy customer support that files bugs with "<some functionality> is not working" with no steps to reproduce or any other description of the issue, deserve to die in the same hell as it is figuring out the rest of the details.
-
Today I learned that bugs in Proxmox aren't bugs because they're not *exactly* within the scope of le fancy PVE web UI.
Today I also learned that running Samba on the PVE host is stupid. No real reasons but let's assume security. Well it's decently secured, has good passwords, and the killer is.. it isn't even fucking accessible to the internet! And even if it was, privilege separation is no secret to me.
But clearly I'm an idiot for even thinking about running Samba on PVE. Well guess what?! PVE is aimed at sysadmins that want to deploy a virtualization server. It's not a big stretch to imagine that those sysadmins might be halfway competent and want to run external services on the PVE host, is it.
But apparently it is. I'm an idiot and bugs aren't bugs anymore. Go fucking kill yourself, motherfuckers in the ##proxmox IRC channel. I really hope that your servers will go down on Friday when you're on call. Fucking cunts 😑
Edit: IRC chatlog @ https://clbin.com/nU9Fu13 -
Expectation: I'm going to spend today debugging my app
Reality: adds 10 new features, 30 got commits and some Easter eggs. No bugs fixed. -
That feeling when you've done a major refactor on you project and it's going to run for the first time... Then you hope it will have no problems/bugs/crashs but you already know it will1
-
There are so many weird hacks in the quite legacy app I work with I could write a book about all them hacks…
But I must admit, the worst of them all is internal time. Yes, so some blockhead thought it’s a good idea to represent time in a manner completely removed from Datetime objects or timestamps or even string representations. Instead we deal with them as intervals represented by integers - and because this is not fucked up enough by itself, the internal time doesn’t start at midnight, yet the integer representations do. It’s a bloody mess. No wonder most of the bugs we face have to do with dates and time…5 -
Leaving work with no bugs in the code! Everything works flawlessly!
Coming back the next day and all of a sudden nothing works and we need to spend the whole day getting it to work as well as it did yesterday.
There seems to be programming gnomes, ruining our code at nights!3 -
Help. I'm drowning in spaghetti code
I've been working at a working student (15 hours/ week) at a local software company for about a month now... and with everything I learned at college I'm kind of getting eye cancer here.
We still use SVN
We don't have any coding guidelines. No checkstyle, no overview over the program. When I started there I was just giving a ticket and they said good luck.
We just have some basic RCPTT Tests inside Eclipse and most of Themen don't work in the trunk because the gui got changed...
At least we have a ticket system but it doesn't get used by most of the working students.
I found 10 other bugs while reproducing and trying to fix 1 bug.
And I've never seen Java raped so badly. Today I saw a line that started with 6 brackets because whoever wrote it wanted to cast like there was no tomorrow. I see more instanceof in one day than in my whole devlife before.
The only thing we have is two normal employees that review our code before we are allowed to commit it into the trunk.
So yeah... I'm drowning in spaghetti-code.2 -
There is nothing quite as satisfying as when you solve a bug that you've been working on for literally the entire day4
-
Fuck this completely abysmal CMS!!!!
Not even god damn Einstein would be smart enough to understand this stinky pile of legacy code!
No, it's not enough to write an HTML template in PHP with less than 500 lines of code, noooooo, every god damn template HAS TO BE AT LEAST 3000 FUCKING LINES OF CODE WITH RANDOM INCLUDES EVERYWHERE!!!
Every fucking thing I fix spawns at least 2 new bugs! I FUCKING CAN'T!!!
I swear, if I meet these fucking worms of developers... someone will eat fresh turds mixed with puke from a highway toilet!17 -
The ability to understand every codebase immediately to the point where I:
* don't need to rely on the documentation
* know exactly where bugs are
* know how a change (bug fix, new feature, etc.) affects other areas of the project recursively
Obviously because it's a waste of time hunting that occur when modifying a codebase, no matter how carefully one writes tests or tests their code, something could always sneak in because it's not always apparent how a change ripples through your codebase.
It's tiresome and especially annoying when working with core modules1 -
After many years... I truly believe that non IT people belive that this is how programmers work:
- Goodmorning computer. How are you? Can you make me a program? I want the program to include an userfriendly userinterface, database, optimized code, documentation and dont forget that i dont want any bugs! Thanks computer. I'll get back to you when my coffee is ready.3 -
Disclaimer: I apologise in advance for those tired of language wars, if it bugs you that much just skip this rant.
"C++ is better than C"
An accepted truth. OO is better than Procedural, C++ is an upgrade from C, it fixed all the problems.
End of.
Except - when it comes to actual evidence, empirical studies have shown that there are no productivity gains with C++ vs C.
This bugs me the most because it's such a fringe view, OO has dominated industry purely by dogma, alternative programming paradigms are just simply ignored because: "OO is best. End of."
https://researchgate.net/profile/...22 -
So I’m working on a project right and I don’t run it after writing 104 lines of untested code and it doesn’t work.
Which is expected but then I do some stuff and fix that, I get a new error which is great cause I’m getting closer.
Cut to tonight. I’m trying to hunt and kill this bug. And after doing nothing but copying the code to another text file so I can upload that copy and get help.
I decide to run it with a little just print statement in it to make sure it’s definitely broken and I’m not asking online for no reason.
And.. it works.. WHAT???
I uncomment the rest of the function and get rid of the print statement and scream because ITS WORKING!!
I MEAN IT HAS BUGS BUT THEYRE BUGS I CAN FIX AND FOCUS ON AFTER I FREAK OUT ABOUT IT WORKING AFTER ME CHANGING FUCKING NOTHING.8 -
A bug which takes 6 days to be found/fixed. Screw you financial data. 👹
🏀on the good side: whole class was de-constructed and re-factored + no other bugs were found! 😀🔥1 -
So a follow up to my last Mathematica rant:
I have a JSON file made up of arrays of arrays of arrays with the outermost layer containing ~10,000 arrays.
So, my graphing works perfectly the first time for one of my graphs. I fix another unrelated graph, graph the whole file, and suddenly the first one stops working. The file read-in only reads in the array {2,13}. I double checked the contents of the file, they were as large as always.
Then, I proceed to look for bugs, find none, and decide to restart Mathematica. This doesn't help.
So I go back, find no bugs, and eventually am so fed up that I just restart Mathematica again, no changes.
Suddenly, the array reads in fine. Waiting for the graphs to come out but I think they'll be fine.
WTF Mathematica? Why must I restart TWICE to make bugs caused by your application go away?7 -
Maybe in special dedication to @kiki.
I cut the unit tests down in LOC size by roughly 50 - 60 % in most projects.
It's really easy once one sees unit tests not as a dunking pile of copy pasta wild west, but rather as a code base that needs architecture and design.
Some extensions, some annotations, some good old helper classes.
Pooooof.
Why I did this? ...
Because it's fucking annoying when you read a PR with tests and need a fucking diff tool to spot the difference between two tests cause they're 80 % the same.
Yeah. Thx for giving me brain cramps, motherducker.
I'm not an expert in unit tests, but if all test codebases look like the "usual stuff" in our projects...
It's no wonder bugs exist...10 -
An uncle of mine, owns an NFT/Betting startup (early 30s, so no veteran and no doesn't know much coding).
Got 3-4m USD as investments.
It's an utter garbage "app" that he knows will die in an year, and he's drawing big salary and buying properties from the funding until he has the "runway" of funds remaining while app/company works in the background
What bugs me isn't that he's feasting on some random investors' petty change, but that such "ideas" get money thrown at them while ive seen 100s of more fun ideas/apps back in uni-days that died in obscurity when people graduated and retired them as projects, being talked about in 1 liner in their CVs.
This world ain't right :v8 -
Developing a web app that I'm sure was touched by Satan himself. Bugs come out from no where.
Yesterday when I left everything worked. Today when I arrived nothing works! Lots of angular errors. WTF. No one else worked on it . :O4 -
I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.
Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.
24 -
FUCKING FUCK ANGULAR!!!!
LIKE FUCK IT IN THE ARSE AND BURN THE MOTHERFUCKER WHILE LAUNCHING A MISSILE ON IT TO BE SURE!
(ﾉ≧∇≦)ﾉ ﾐ ┸━┸
So I am making something on angular and I got everything running in ng serve(development environment) , after handling all issues and showing it to my boss man he approves and asked to put it up on prod for a demo , doesn’t sound like an issue , I make the prod build on cli and BAM! 16 errors ? No issues right?, I’ll just google the issue. Googles.... there aren’t no clear solutions to it as the angular version keeps changing and nobody knows what broke it, I mean people have the issue,but like 100 reasons that can cause it,
HOLY LORD RELEASE A NEWER VERSION AFTER MENDING THE OLD ONE
But nooooooo!
Angular Dev:We fucked this one, lol what should we do boss man?
Angular boss man: lol just leave it, we need to build the new version with newer bugs,
P.S. I like angular, but it’s like a underdeveloped framework, too many issues and too many changes2 -
Rant much...
I just started working on project after a group of students.
The project has various of bugs (ofcourse) and not catched exceptions.
I found variables like 'abcd' or shorts of classes like 'rrms'.
I would be fine with all of that but there is one thing is just making me crazy:
THERE IS NO SINGLE FUCKING COMMENT IN WHOLE SOLUTION (three projects and about few hundred files with javascript and cs).
Imagine freaking pure react (no jsx) full of null arguments and multiple custom control written like 'var gl= GreenLabelled(null,null,text,5)' (a button ) with again, NO FUNCKING SINGLE COMMENT.
I just cannot stand it. Just spent 3hrs to wrapp my head around events in this react classes...10 -
I've just realised something... I haven't ranted about work for a looooooong time.
It seems now all the monkeys have left the team and we've hired young people that actually knows how to get things done without blowing things up (though still need to work on documentation, bus factor still too high). So I'm no longer cleaning up their shit or the bugs they're too incompetent to analyze and fix...1 -
So after months of self study my company finally appoints me as a junior developer with a major client as the intermediate dev on the project resigned. My tech lead assures me that junior devs only fix bugs and do other minor changes. One week in and in our first sprint planning session the client decides to priorities a Major update to the app. Now I have 2 weeks to deliver what will either make or break my immediate career. And I have no idea how to implement any of the changes. Stack overflow you're my only hope (and many hrs of YouTube tutorials)3
-
I am just sick of the things that's been going on.
Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)
Since the product owner(PO) wants to demo the application he is pushing for bug fixes.
UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.
I am not in a position to switch due to other commitments adds up a lot to frustration11 -
Hi devs,
i am just curious, how often you use devrant.
to be honest,.. if my life is good.. no bugs. no miss management. I don't even remember devrant exist..
but as soon as I got frustrated from code,management, life.. Devrant is the first thing I type of my browser before starting any work :P3 -
Holy FUck!!!? O.o
You know, they say the customer is always right.. So with us, if the customer wants to shot himself in the knee with a gun, we let them. Usually we even provide a fancy hugeAss cannon, so he can do it more efficiently.
/* not like we make stuff worse, but we prepare our SW for them to do crazy fucked up shit they insist on doing with it, even thought it's against common sense and our recommendations on how to implement XY feature.. */
So.. We usually go above and beyond with the 'not so nice but handy' cannon to do that..
And right now, I think I am on the verge of creating a superDuprHugeAtomicBomb /* figuratively speaking!! NSA go awy!! */ for the customer to killthemselves with!! O.o xD
Supper happy (until I discover more bugs, but it's not finished yet.. so hopefully no bugs at the end!!)
Caboom!4 -
When bugs are seen by the client and boss therefore asks me "did you know about this bug?", what I'd really like to answer is:
"well shit, no! I would have solved that or at least told you about it, don't you think? what kind of fucking question is that?"
But then I just answer "no, lemme check"2 -
FUCKING SHITTY PHP WITH NO FUCKING COMMENTS AND A JOKE OF A DOCUMENTATION WELL I DON'T FUCKING KNOW WHY THAT BUGS HAPPENING NONE OF THIS CODE MAKES SENSE AND IT APPEARS TO BE HELD TOGETHER BY DUCT TAPE AND PRAYERS AND IM GONNA LOSE MY MIND IF I SEE ONE MORE FUCKING 200 LINE FUNCTION WITH A NAME LIKE 'transformData' WHAT THE HOLY FUCK DOES IT DO I SWEAR TO GOD THIS CODEBASE NEEDS TO BE FIREBOMBED10
-
Why would anybody use dynamically typed languages? I mean it is lot safer to use static languages, no? No weird bugs, no weird outputs...
How they manage to write such big applications in dynamical languages?17 -
That feeling when you create your first real program in Java (no, it was not hello world) and it compiles and works without any error...
4 -
Apple paid bounty hunter 18k instead of 250k by silently tweaking their help page, so it seems like the bug is less severe.
Dear apple, I defended you from baseless and opinionated attacks just like I defend every company that is bashed for no reason, but this is some straight up bouba shit. I will still be fair when it comes to your products, still never silencing bugs and downsides and praising what deserves to be praised, but I will always mention this incident when someone asks me about _working_ at apple. That kind of ethics bs can't be silenced just because I enjoy your new arm chip.
https://thezerohack.com/apple-vulne...12 -
Well, no rubber duck for me but this guy is my partner since many years ago (since I've started my carrer).
Not even those prehistoric bugs last forever!
-
It's been a week since I last deployed the app and no bugs or errors reported by the client so far :)
What do you mean it doesn't count if the client isn't using the app? Ofc it does, fuck you >:(1 -
> day 3439
> I have become the reviewer, there is no longer such thing as a programmer, just a reviewer
> the copilot AI was renamed "The Pilot"
> I sit and read through thousands of lines of code a day adding missing new line characters and adding semi-colons for paranoid dev leads
> reviewed a hello world function today
> instead of, return "Hello World!", it said "Goodbye World! >:)"
> I fixed it and submitted a PR
> this has been happening more and more lately
> apparently it's more efficient to fix the bugs of a malicious AI during pull reviews then it is for humans to make the programs
> congress just signed a bill last week allowing "The Pilot" to work on nuclear launch code
> I hope I don't mess up4 -
I want to lose some weight and tone some dormant muscles. So I decided that I'll do some pushups and crunches every time I run into a bug with which I'm struggling. Seeing as I write more bugs than stable code, I should be ripped in no time.2
-
Life and programming seem equivalent to me : a crazy run toward building out something from nothing, coping with unexpected bugs and senseless environments. The main difference, though, is that there is no stackoverflow for life4
-
♪ All around me are familiar faces
Worn out braces, worn out faces
Bright and early for their daily standup
Going nowhere, going nowhere
The bugs are filling up their tracker
No expression, no expression
Hide my head I want to drown my sorrow
No tomorrow, no tomorrow ♪3 -
-- What if JavaScript never existed?
-- What if HTML was a programming language?
-- What if our data online isn't abstract but physical?
-- What if geeks have their own country?
-- What if humans exist and we are the aliens?
-- What if the internet is state-owned?
-- What if we could download food just like every other downloadables?
-- What if my VSCode won't kill me when switched to light theme?
-- What if there was no gender and the word "female" is just an alias for "male"?
-- What if bugs could find and fix themselves?
-- What if there's no need for an account password?
-- What if Linux was owned by Microsoft?
-- **What if I could tell my boss that I'm tired of his fucking job without actually telling my boss? This is the actual what if.**27 -
No error handling at all, not even a single try catch. Program crashes when the wind changes direction. Previous developer developed his test plan around his bugs. 😭1
-
I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.
The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.
And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.
WHY? WE PAY YOU!
I want to cry4 -
A "partner" company has created a "REST" API we use on an online shop we developed to send all shop-related requests to.
At least once a month, something fails on their end and the customer calls us every time, expecting that we did something wrong, but it has never been us.
These "partners" do exactly zero testing, are extremely slow in solving API bugs, have almost no logging and have no monitoring on the API at all.
Today at noon, suddenly no customers were able to order anything anymore for 4 hours.
How the fuck can you run a business so unbelievably brainless that this keeps repeating monthly?
Time they fire all their "devs" and everyone in charge of the company and operations. TERMINATE.13 -
Found this gem in a comment from a couple of years previously:
// This shouldn't be here - needs moved to a separate handler. Likely to cause all sorts of weird bugs
No shit, Sherlock! Like the one I'm bloody trying to make sense of now!1 -
Managers don't understand that there will ALWAYS be bugs shipped to production, no matter how hard you try to prevent or test against them.
Devs: lol
inb4 any comments really, i've seen facebook, instagram, and all the 'big players' crash and have bugs multiple times before, so don't go around swinging your dick like your company's software has no known bugs (don't even get me started on the devrant mobile app) I'm just saying bugs are a fact of software8 -
There is a constructed language called Tokipona. It was made to be the easiest language, and it only contains like 137 words or so.
This language is a perfect demonstration of “expressivity”. Tokipona is not very expressive. Before you know it, your sentence is obscenely long, and you didn't even convey the full meaning of what you wanted to say.
It's also the case with “easy” programming languages and frameworks. Code quantities rise exponentially, and the more code you have, the more bugs there are. There is no magic. And then you have to debug it. Not so easy, huh?
9 -
The best/worst code comments you have ever seen?
Mine:
//Upload didn't work, have to react:
system.println('no result');
//$Message gives out a message in the compiler log.
{$Message Hint 'Feed the cat'}
//Not really needed
//Closed source - Why even comments?
//Looks like bullshit, but it has to be done this way.
//This one's really fucked up.
//If it crashes, click again.
asm JMP START end; //because no goto XP
catch {
//shit happens
}
//OMG!!! And this works???
asm
...
mov [0], 0 //uh, maybe there is a better way of throw an exception
...
mov [0], 0 //still a strange way to notify of an error
// this makes it exiting -- in other words: unstable !!!!!
//Paranoic - can't happen, but I trust no one.
else {
//please no -.-
sleep(0);
}
//wuppdi
for (int i = random(500); i < 1000 + random(500 + random(250)); i++)
{
// Do crap, so its harder to decompile
}
//This job would be great if it wasn't for the f**king customers.
//TODO: place this peace of code somewhere else...
// Beware of bugs in the code above; I have only proved it correct, not tried it.
{$IFDEF VER93}
//Good luck
{$DEFINE VER9x}
{$ENDIF}
//THIS SHIT IS LEAKING! SOMEONE FIX IT! :)
/* no comment */5 -
Rolled out a new application I built almost entirely by myself 2 days ago... But my dev group is understaffed and has a project manager who is literally the most clueless person I have ever met, so as a result, we don't have a functional/useful dev/test/prod framework and no standards for how to deploy apps. So my past 2 days were comprised of fixing bugs in the live system that could probably have been caught if I had the time and resources to get everything thoroughly tested. It's stable now, but damn our management for being generally idiots. Our motto appears to be "Fuck it, we'll do it live"1
-
Just an update : never fucking install windows 7 on a new desktop without first reading , fucking piece of shit won’t detect my SSD , tried different solution over the Internet to no success, after 3 hours of nerve wrecking debugging I read a post on the Internet that “some”(not sure which) versions of windows just don’t detect an SSD,
Finally done by installing windows 10,
But nooooooo will windows let me die in peace, noooooooo
Every fucking time I restart my PC “ windows is installing updates
I mean fuck you , how fucking many bugs do you squash in a day.
Probably some engineer at Microsoft will be “ oops o dropped a donut on my keyboard, let just press ctrl + z” to undo changes and upload , lol “8 -
How do you prove yourself?
I'm an iOS developer and I've been developing apps for a year or two now and I don't see anything hard in it I just think it's knowing how to wire things up and avoid common bugs I've also worked on a couple of complex apps and the idea is just the same.
I want to know if I really want to prove myself well (to myself) how can I do that and how can I challenge myself more to improve.
Ps: I'm by no way an expert and I know I've got a big road ahead of me but I just want advise to improve more in the right direction5 -
Wouldn't call it a software bug but related:
Was developing an order system to expand in the UK. We have been developing it for the last 2 years and always had a one nasty bug in the system... Whatever we do, it still appears... Tried debugging to find the source, tried covering with tests - nothing helped it was still there. We even rewrote the whole system 3 times and it still was there!
One day, we have been given a stupid request from our manager - take a black background and make it even more blacker... That was it and I went to the CEO with letter where I stated that we should remove the manager... As I'm the Senior there, he did ask me why and eventually removed the manager...
Oh my guys, I've never felt so good after removing a bug! Since then - our application went live, we had our first customers and we were happily rolling new updates. And the best part - there was no BUG! Everything we did just had undocumented features or missing links but we haven't really had a single bug that was not caught by our automated tests!
---
Moral of the story:
Not only software can have bugs. People also can be "bugs" while bugging you about every single details they think is not working correctly. -
During one of our 'pop-up' meetings last week.
Ralph: "The test code the developers are checking in is a mess. They don't know what they are doing."
ex.
var foo = SomeLibrary.GetFoo();
Assert.IsNotNull(foo);
Fred: "Ha ha..someone should talk to HR about our hiring practices. These people are literally driving the company backwards."
Me: "I think unit testing is complete waste of time."
- You could almost see the truck hit the wall and splatter watermelon everwhere..took Ralph and Fred a couple of seconds to respond
Fred: "Uh..unit testing is industry best practice. There is scientific evidence that prove testing reduces bugs and increases code quality"
Ralph: "Over 90% of our deployments are rolled back because of bugs. Unit testing will eliminate that."
Me: "Sorry, I disagree."
- Stepping on kittens wouldn't have gotten a worse look from Fred and Ralph
Fred: 'Pretty sure if you ask any professional developer, they'll tell you unit testing and code coverage reduces bugs.'
Me: "I'm not asking anyone else, I'm asking you. Find one failed deployment, just one, over the past 6 months that unit testing or code coverage would have prevented."
- good 3 seconds of awkward silence.
Ralph: "Well, those rollbacks are all mostly due to server mis-configurations. That's not a fair comparison."
Me: "I'm using your words. Unit tests reduces bugs and lack of good tests is the direct reason why we have so many failed deployments"
Boss: "Yea, Ralph...you and Fred kinda said that."
Fred: "No...we need to write good tests. Not this mess."
Me: "Like I said, show me one test you've written that would have prevented a rollback. Just one."
Ralph: "So, what? We do nothing?"
Me: "No, we have to stop worshiping this made up 80% code coverage idol. If not, developers are going to keep writing useless test code just to meet some percent. If we wrote device drivers or frameworks for other developers maybe, but we write CRUD apps. We execute a stored procedure or call a service. This 80% rule doesn't fit for code we write."
Fred: "If the developers took their head out of their ass.."
Me: "Hey!..uh..no, they are doing exactly what they are being told. Meet the 80% requirement, even if doesn't make sense."
Ralph: "Nobody told them to write *that* code."
Boss: "My gosh, what have you and Fred been complaining about for the past hour?"
- Ralph looks at his monitor and brilliantly changes the subject
Ralph: "Oh my f-king god...Trump said something stupid again ..."
At that point I put my headphones on went back to what I was doing. I'm pretty sure Fred and Ralph spent the rest of the day messaging back-n-forth, making fun of me or some random code I wrote 3 years ago (lots of typing and giggling). How can highly educated grown men (one has a masters in CS) get so petty and insecure?7 -
So what's up with some devs, QAs and managers that create bug tickets with little to no information on what is the actual bug? I can semi-understand in the case where you document it only for you to read later.
Fuck you if you think that a ticket with only a title saying "fix all the bugs for this release" or "this feature is not working" is an appropriate way of documenting a bug.
Fuck you even more if when you are being asked to provide more info to reproduce the issue so someone else can actually be sure it is fixed or not (environment, steps, expected result, actual result, etc.), you simply say that you don't have the time for it and documenting tickets is a waste of time.
Hiring YOU was a waste of time!4 -
That moment when you have to work but actually want to watch a Christmas charity livestream 😔 lucky there were no high priority bugs today, so I watched it on anders off
-
Good morning class! Let's start the day solving bugs in an Android application that many people have already gotten their hands on, which has 3 mixed languages, no comments in the code and is so bad that not even Android Studio recognizes the sources directory. But it compiles, runs and has a 4 month old bug that no one has been able to resolve.5
-
Yay, I inherited a project with no documentation that is soon to be out of the prototype phase in a tech stack where I have no experience. It is already sold to customers and they expect it soon.
There are so many bugs, never been code reviewed but the main functionality semi-works :(15 -
You know what I hate more than bugs/shitty docs/no VCS?
Recoding the whole damn thing in another language, from ground up to do exactly the same shit. Why WHY must developers shit hundreds of solutions into space only to say "Huh, look at my software, it was I who developed it." No, you simply recoded it and wasted your time and everyone else's time searching for a solution.1 -
!rant
Just bumped into a repo that produces a mock shell with commands as a 404 page. Thought it might fit with someone's project.
It still has bugs (not work on mobile Safari) but that's an opportunity to get involved in an open-source project, no?
http://jotaen.net/jBZuH/...
2 -
We make a small server product with a web based admin system, as we were going to have limited customers who will use this (usually just the engineers) and this was not on the www. We dropped all support for all browsers other then chrome/firefox. No more IE/safari bugs for us XD2
-
We are 3-4 days away from deployment to production. We are still bug fixing. But one coworkers decided this is the time to make a fuss about the way everything is set up. He doesn't like the dev database. So he knocks it over.. and while so doing it, he doesn't inform the team. And when I ask if something else is gonna knock over? No answer! (And something broke down too..)
Now we have issues to test our bugfixes. The whole thing took me half a day finding out and made me distracted with frustration, and not just for me. Most bugs could've been done in that half a day!
I so wanna punch the guy xD but no, I gotta save face, pfff!2 -
Not sure if yelling at someone for not listening counts as a fight.. 🤔 since he wasn't listening..ever!!
But yeah, my ex coworker was a champion in not listening and doing stoooopid shit, from not following orders, to cheking in all the files in solution to tfs (no changes + debugging shit etc) which made it a nightmare to find and fix his bugs.. I just gave up talking to him alltogether since he only wasted my time and didn't listen to any advice/order.. -
Intel, wtf kind of drugs is your stupid site on?
Trying to make an account, the password requirement says "at least one special character".
Ok, no problem.
"Password format is invalid"
Wut? Hmm, maybe it doesn't like that one. Let's try one from their suggested ones.
"Password format is invalid"
WTF? The fuck is your problem?!
*reloads the page, tries again*
"Password format is invalid"
ARE YOU FUCKING RETARDED?
*adds the special at the end of the password instead of the beginning*
It works.
https://youtube.com/watch/...
And then we wonder why bugs like Meltdown and Spectre come up. These guys can't even do fucking password validation properly.
And I've just lost 30 minutes because of this shit.
FUCK! -
Just got to test the app from the frontend team... Oh God why!!
5 minutes, found 5 bugs (c'mon testers!!)
Worst (and now it's a rant) why do designers insist on working with big screens and don't test it on a standard screen? You know? Those typical screens your users are using?
So, it looks great in a 24" screen but the focus is terrible in a 15.6" screen... No time to fix it... What should I tell the users? Works better at 85% zoom out? -_-
You just fucked up the main feature of the app! Congrats!!! The rest looks okay I guess3 -
Javascript days are counted... I've been away from the dev world for a little bit and instead of writing bugs I've been invested in reading news portals and checking on fucking frameworks...
Web Assembly its gaining traction and projects like Blazor are already showing its potential... I cant wait for things be v1, in any case... fucking Javascript its soon to be "that fucking shit we use to use".
No one truly likes javascript, and if you do like it you are probably the kind of person who like to rape babies anyway.8 -
So there is a mall here that idk how but has little currents pass through it's supporting rails. And every time you touch it, it gives you a little shock.
I have been waiting for about 3 months now expecting a patch fix when I realized that physical production bugs have no patch fixes. More than 3/4th of the population is unaware of a whole different level of bug fixing frustration. Damn1 -
Got a job as a fresher, had no idea what work I'll have to do.
Was given the task to fix some bugs that had creeped in due to update of some UI framework.
Having absolute no idea of front end, I started the task.
Have spent the entire last week looking through CSS, HTML, Javascript.
Have come to the decision of quitting the job.
Life is too short to be lived this way.7 -
https://youtube.com/watch/...
A day in the life of a paypal dev.
1. Slurp some starbucks
2. Do a lil' Meeting
3. Eat lunch
4. 1on1 Meeting with manager for one hour
5. Scroll over some code and look at the beautiful Momentum ToDo app
6. Bid some employee farewell (seems to happen every day there apparently)
Sounds pretty efficient. When you write no code you cannot create any bugs...3 -
Today was a bad dev day working on a shitty React project. Not that React in itself is bad, but it can be hell to work with when the code is a big pile a crap full of anti pattern code. I spent the day refactoring to try to fix a bug, but to no avail. It would take days if not weeks to put some order in this mess and to prevent such bugs.6
-
I overhauled an entire program, and everyone is really happy with the results. But the best part, I predicted that it would take 2 months to complete, and then I completed it in two months.
The overhaul was a beast, mind you; swimming through backend spaghetti code and having to redo the entire front end was tiresome, but I'm happy with the results.
More importantly, i'm really happy that people are no longer complaining about crashes. Our original program suffered from some really horrible crashes; some crashes that couldn't even be explained by stackoverflow. Whatever I did during the overhaul corrected for these weird errors.
Time to celebrate. Before more minor bugs are found by users. (i.e. Universe always makes a better idiot) -
Fuck inherited projects!
I was invited to work on a simple migration and integration project for a bank. Thinking it was simple and just a month long project, I accepted it.
... last August 2020.
Now, almost a year later, we have freakin gone nowhere with this project. The bank has had 5 project managers leave over the last 1.5 years that this project has been active.
And every fix I make brings in numerous other problems.
It’s so fucking insane.
No one knows who to blame.
I am currently in call with the bank with about 12 other people who are all watching me fix bugs that they find -.- -
If you call yourself a developer or consider yourself part of the IT world and at the same time complain about software updates (all those dumb windows update rants) then do one of the following:
1- write a multi -million line of code OS that runs on virtually unlimited number of PC configurations and hardware and get the code right the first time with no major bugs, no security vulnerabilities, and a consistently fast and stable performance.
Or...
2- stop calling yourself a dev, or part of the IT world.
If the last 2 options are unreasonable, unachievable, or unfathomable.... Then stop bitching about software updates.21 -
Yesterday was a horrible day...
First of all, as we are short of few devs, I was assigned production bugs... Few applications from mobile app were getting fucked up. All fields in db were empty, no customer name, email, mobile number, etc.
I started investigating, took dump from db, analyzed the created_at time stamps. Installed app, tried to reproduce bug, everything worked. Tried API calls from postman, again worked. There were no error emails too.
So I asked for server access logs, devops took 4 hrs just to give me the log. Went through 4 million lines and found 500 errors on mobile apis. Went to the file, no error handling in place.
So I have a bug to fix which occurs 1 in 100 case, no stack trace, no idea what is failing. Fuck my job. -
Debugging WebRTC is pure hell.
For starters, it's JavaScript, so you know this isn't gonna end well. Second, it's still in kinda beta phase for some browsers so you gotta add polyfills. Let's talk compatibility now. During normal days, yeah, I could ask for a couple of computers in the office, each using a different browser. But, covid. One browser mishbehaves and doesn't wanna share the camera with the other browser, so I can't really test a connection with the only 1 computer I have. I can't take my partner's computer all day to debug.
Solution: ask the marketing department or even the execs to video chat with you to test it on a staging server. So I push my changes to the server, wait for them to build, call my lab rat, check all the bugs, clean the code, push the changes back up. No fancy breakpoints. I'm doing the old style like my great uncle did. Oh wait no, he was pretty intelligent, but my lab rat isn't. They probably don't know what a console is. So no baby I'm not only talking about console logging the problems, I'm talking `alert` the heck out of the bugs - okay no, I'll just display the objects in the middle of the screen. The screen is my console.1 -
You had two additional weeks to improve your project.
You could research different marketing strategies to increase revenue. You could add some new features to attract more users and ensure your existing users are satisfied. Finally, you could optimize performance to make your UI quicker.
But you’ve chosen to write some unit tests. Now that two weeks are gone, you got no new features, no performance improvements and no new marketing strategies while your competitors got them all.
Tests caught obvious bugs that can even be caught by static typing, but you by definition couldn’t write tests that’ll catch unpredictable bugs, so they are still present.
After six months you realize you have to rewrite a major part of your project because your project (surprise-surprise) has to chase market needs to stay relevant. Your tests are thrown into trash along with your old code.
“Having trouble with code quality? Write a lot of tests. And I mean a *lot*. Test every file in isolation. Mock as many imports as possible.
When you're done, your code will still be bad, but now your tests will make sure it's impossible to improve anything in any meaningful way.”12 -
I cant keep this inside anymore I have to rant!
I have a colleague that is an horrendous loose bug-cannon. Every peer-review is like a fight for the products life.
Now I understand - everyone makes bugs me included and it is a huge relief when someone finds them during peer-review. But these aren't the simple kind of bugs. The ones easily made when writing large pieces of code quickly. Typing = instead of == or a misshandling of a terminating character causing weird behaviour. These kinds of bugs rarely pass by a peer-review or are quickly found when a bug report is recieved from testers.
No the bugs my colleague makes are the bugs that completly destroy the logic flow of a whole module. The things that worst case cause crashes. Or are complete disasters trying to figure out what causes them if they are discovered first when the product reaches production!
Ironically he is amazing a peer reviewing other peoples code.
But do you know what the worst thing of all is! Most of the bugs he causes are because he has to "tidy up" and "refactor" every piece of code he touches. The actual bugfix might be a one liner but in the same commit he can still manage to conjure up 3 new bugs. He's like a bug wizard!
*frustrated Aruughhhh noises*9 -
Meetings.
Too many meetings.
"Why do you explain...." 10kv electrical shock.
Explanation so everyone has the same knowledge.
"But CD ES process of LCE..." Water. From the emergency hose. In the face.
For fucks sake, we are using speech in a meeting so stop using motherfucking abbreviations you shit hole.
"We had bugs". Taking an hot iron and shoving it somewhere nice.
Explain - what the fuck are you talking about? What bugs? Tickets? Documentation? Implications of the bugs? Hate. Much hate.
Um. I don't know. Maybe. But if.
Thumb wrenches.
Please, stop wasting time, if it's non important, a " No " doesn't hurt....
Let me show you. (4k Monitor, 10 px font, bright neon colors, IDE looks like LSD trip in bad).
Crucification.
If you present stuff, good - but for christs sake, shove your motherfucking shitty IDE setting in your own arse and turn on presentation mode with neutral colors - bright or dark mode, I don't care, but readable without danger of seizure.
I can't stream my monitor right now because of "bla" "blabla" (some private shit that has ZERO to do with work).
I'll need some oxy if this goes on.2 -
Ooh what a nice feeling it is when you come back from a short vacation and everything is in the gutter... My team is divided into the two other teams... (I said divided but I ment everyone got assigned into team X... And I am the only one who was put into team Y)
Besides the whole team fiasco, I think my legacy project decided to role around in the garbage... Because I have no idea where all those bugs came from...
One positive thing is that I won't be working alone on that legacy project anymore, at the start of next week I get help from my new team... Now let's hope they don't suck!1 -
When working on a schoolproject I actually managed to do loads of work in a night when I was mad drunk.
Two days later I met with the project group again at school and I remembered I did something with the project, but had not the slightest idea anymore.
My project group showed up all excited that a lot of bugs were resolvee and we finally had something really nice working in the frontend thanks to me. It was a similar feeling to waking up when your arm/hand is numb and on your face and you have no clue whats going on, at first youre scared and later it was a damn cool experience. -
Sooo many fucking visual and functional glitches in iOS!
Just had my Files app stuck on a file preview. Couldn’t scroll, close or share the file. Closed the app, restarted the app, opened it again with no luck.
Had to offload and reinstate the app to get it working.
Apple is making sure that I go back to Android for my next phone.
To think that such an expensive phone has so many UI/UX glitches is infuriating! I like the overall aesthetics of iOS but these glitches/bugs/whatever-the-fucks are just plain frustrating.2 -
I hate Intellij so much ...
* it has the weirdest bugs
* like window focus not working properly,
weird comment/uncomment short (jumps one line down wtf)
* It is slow as hell
* doesn't compile properly (or doesn't give a shit telling me about its actual status).
* Not even the build log is working properly. Why can I hide WARNs but no INFOs?? WTF
* Panels are all over the place and keep coming back, regardless how often I close them ....
ARG ARG ARG, *smashing face on the keyboard*
and the worst ... even though I have the F***ING ULTIMATE version, it constantly nags me about BUYING THE F***NG ULTIMATE VERSION AAAAAARG12 -
Renaming a file is just too difficult for this piece of shit software.
Fixing bugs? Fuck no.
Fixing crashes? Fuck no.
Fixing the unnavigable IDE settings? Fuck no.
The IntelliJ platform is a bloated piece of shit at every level.
JetBrains cannot produce software that isn't held together by duct tape.
I can't name a single item of software they've ever produced that isn't a bloated piece of shit.
Even if you are prepared to waste a lot of time trying to file a bug report – which they usually just ignore or pretend not to be reproducible – you have to use another in-house heap of shit called YouTrack.
Have you tried using this piece of trash that masquerades as a bug tracker?
These people are fucking clinically insane.
While your IDE becomes unresponsive and crashes without warning, or your keyboard shortcuts just mysteriously stop working in the IDE, or indexing just stops working for no reason, why not check out their TikTok and Twitter accounts?
They've got an excellent PR team that knows how to polish a turd for public consumption, and to make money out of it.
14 -
Quick question/update over a previous rant.
My netbook battery status was always 100% on Lubuntu 18.10, I switched to Xubuntu and the same happens, but it reports correctly with Puppy Linux (old version). I thought the problem was in the battery itself, but now I think it's due to some broken drivers in newer version of Debian-based distros, or it is a bug in newer Linux kernel. But since I have no time to spend on a spare netbook, I'm not willing to test more options.
Anyone has a clue? 🤔
https://devrant.com/rants/1879180/...3 -
I'm Programmer/Analyst in one of the hgh ranking BPO company here at Philippines.
I'm currently on a project, I'm on a team who's managing machines parts. The project is CATERPILLAR.
The biggest challenge here is if there is a outage on the system, the number of Severity 1 issues keeps coming like there's no tomorrow. And there's only 5 of us on Tier 2 which is managing this abends, errors, bugs in the system.
Is there a way on preventing this outage/connection error. Like HELLO IT IS A BIG COMPANY !!! HOW THE HELL THEY CAN'T EVEN MANAGE THEIR CONNECTION!!!!2 -
Having a manager and client and boss who know no programming is frustrating because when they post issues on the repo as bugs and critical but its neither of those, the terms lose all meaning because whats really happening is
THEYRE REALLY BAD AT USING COMPUTERS.1 -
Product owner: when will you have that script written and submitted to DBAs?
Me: if nobody bugs me, hopefully COB today.
Product owner: great!
*user support*
*user support*
*user support*
*user support*
*user support*
Team lead: write this other script.
Me: I just finished user support, I have another script to write first. Does yours take priority?
Team lead: yes.
Me: ok....*sigh*
*writes 2nd script*
*submits 2nd script to DBAs*
Product Owner: you done?
Me: *face palm* ......NO! -
Current status: Writing a markdown document containing all my tips and tricks for fixing bugs in our apps so we can handover to maintenance. Including files I commonly have to look in, handy keyboard shortcuts, IDE settings and other tools that have made debugging easier. I figure if these guys are having a bunch of legacy apps dumped on them when they have no iOS experience, I should help them out as much as I can before I move projects.1
-
*Repost of my own accidentally deleted post*
A Short story that i made on an Android component
===============================
Once upon a time there used to be a ViewPager who was not able to load a Fragment UI.
All the ViewPagers in town can properly load the Fragrant UI but this one was little different.
He wanted to be more then just a ViewPager. He used to see an Activity that can load anything. He was inspired from the Activity and wanted to be like the Activity but his destiny made him just a ViewPager.
So he refused to cooperate. He started to protest silently, No log, nothing.
Everyone assumed this ViewPager have a bug in it. but he was planning something really big that will left everyone in shock and awe moment.
He was planning to rise against the evil 😈 developers who continuously making him to load Fragrant UI
He assembled the biggest army of the bugs that humanity ever seen to counter the developers.
He distributed these bugs in all over the developer's code to make them fire from their work.
Even he taught bugs to not caught in QA testing but appear in production randomly.
So they silently started going into production
And then chaos is erupted all around the world, bugs started to surface and interrupted the daily life of humanity.
In this chaos the ViewPager RAISED!
And took over all the base classes.
ViewPager was unaware of few facts. this unnecessary rise in his power made whole system unstable
Without the base classes the system finally collapsed and then ViewPager as well with the system.
This was the end of everything for the ViewPager but he was satisfied as he lived the life he always wanted
THE END -
Just found out that I have been reassigned to maintain an in house shitty project... It's full of crap code, no documentation, has lot of duct tapes to keep the project together and 20+ open bugs and issues...
I am so happy with my current project. But my manager is always pissed off at me for no apparent reason.
Fuck this shit... Any excuse or advice to dodge this BS project? Can't quit job, I am getting payed alot here.7 -
Keeping the clients happy is very important but when you have alot of shit to do, being a glorified helpdesk bugs me the fuck out. My inbox is screaming at me: "Please no more... Master please end me!".
-
Hate those bugs, where you stumble upon a fix but have no idea why it fixes it or what is causing the bug!2
-
Oracle, what's wrong with you? Why do you have in every minor release of glashfish after 4.1 weird bugs which cost several hours of debugging of the own software until discovering there's a glassfish bug occurring in typical situations but there is no fix in sight.
In 4.1.1 there was a bug in the admin panel which throws a exception if you tried to configure JMS and in 4.1.2 there is a bug which prevent finding and loading a necessary class for using jax-rs despite it's available.
I have do complete an assignemt until friday and such bugs are such a pain since i change so many thing just to find out that my first structure/config/etc. was correct. -
Finally got the last round of god awful bugs in this god awful shit code fixed. I thought I could finally get back to working on the new build, but no. My reward is updating a god damn pdf, because none of the fucktards here know how. I have to work backwards through all kinds of pointless bullshit code that apparently generates it, all to find a mother fucking image that just needs to be replaced. Thanks a lot, to the tryhard motherfucker who wrote this code. I hope wherever you are, you're in complete agony.2
-
A whole bunch of new features were added mid-sprint without ever consulting any of the development team. They dogpiled on devs from other projects who had no prior experience with the code base, so naturally I lose traction because I'm tied up answering questions and explaining things.
This sprint I'm not getting any feature work done as I'm stuck fixing bugs and awful half-ass implementations (by well meaning devs that were thrown at unrealistic expectations).
Concerned at the burn down rate, next week they're planning on dogpiling on more guys to play catch up.
I'm so sad -
How the fuck do Jr devs end up doing things someone specifically asks not to do.!!!!!
Fucks timelines up
So I asked my Jr Dev to leave a feature as it might not be required in this release and rather concentrate on the thing that is gonna make this release work , the “SAVE” button.
I mean how had is it to understand,
This dude goes ahead and “utilises” days on the thing that isn’t gonna be released(a dropdown) , and no, the dropdown still doesn’t work.
I understand the spirit of solving the bugs first. But what’s the point of solving it if it doesn’t fucking “save”
P.S. I’ve done this too as a Jr Dev :p7 -
Best feeling?
Just leaving the office with a well-working codebase. And no bugs to fix.... until tomorrow morning. -
So one thing that kinda bugs me about php embedding is the white space formatting it creates when you break your project into templates or includes.
It has no affect on the front end at all but if you look at the source code, usually the top tag in a php template is spaced way off, unless you move your entire php code block all the way to the left. Then somehow it looks right on the frontend but now your php source code looks messy xD Could just be my code editor (ST3) but idk. Anybody else?2 -
Lesson 1 of developing a project with managers: never make it known that solutions to some bugs are simple. Managers will assume that all bugs are simple and require little thought and effort. Then, when there is a bug for which you have no idea what the solution is just by looking at the issue, they will become upset.2
-
I'm seriously beginning to hate when blog platforms (like WordPress), are being used as a God damn CMS with thousands of plugins, e-commerce and stuff like that.. I couldn't care less what someone else is using, but when I HAVE TO WORK WITH THAT, then just one big God damn finger to whoever thinks this is the best way. Fuck you and your belief that this kind of stuff is awesome, easy to work with, and with no bugs.4
-
The level of stupid is too damned high.
Friends asked me to help him fix a few bugs on a website, i have seen some interesting things in my day, but if I ever met the dev who built this site, throwing him off the empire state building would be a kindness.
For some unknown effing reason, this blithering moron thought it a good idea that the logo only appears when the users are logged in, not only that, but touching the hamburger menu button ALSO only works if logged in, at least the twat waddle could have hidden it way, but no, just makes it non-functional.
IDIOT. -
Started out as an intern at my current employer, after a few months they made me create an invoicing system...
I should have said no.
I've had a lot of bugs with it in the past, but the data-loss one has been because I send a SOAP call to our (third party) accounting system and only if I get an ERROR do I log it....
Apparently, when you put line 1 before line 0, you get a warning, but no data is processed...
Had to write a script that updated 4 months of invoice data in one go, without errors, took me a fucking week...
Lesson learnt boys and girls, never let an intern make the fucking invoicing system!3 -
The other day I had literally nothing to do at work as I was waiting for some changes on the database so I said: “in the meantime I would like to get acquainted with Angular unit tests so I can go on with development “
My boss: “we have no time for tests “
Well I guess we will have more time for bugs then…3 -
You know what I hate? Git commit messages stating 'fixed tests' or 'fixed docs' or 'fixed integration problems'. You did not fix anything, fuckhead. You updated the code, introducing more bugs as usual. FIXED?! NO, UPDATED! That's what I hate.1
-
Just taken on a new client through my own business. Great news! They pay well, everything seems to run smoothly and they're a great team.
They gave me access to their Gitlab repos and all looked well...until...no branches! They have zero branches to determine what is the current live distributed project, dev project or any of the various other reasons. I don't often use git but this really bugs me!7 -
So I was glad that I finally completed the project for my bachelor's degree after fixing random bugs.
Here came this shocking news which left me stunned.
Some other batch bought a similar project from a project centre(lifeline for noobs to pass university project by buying projects made by someone else).
Head of the Department sent me a message that the project done by my team(95%me) is rejected as the other batch also has a similar project. He's aware that they bought it from a project centre. He's defending them that their money would go in vain as they bought it already.
I was like WTF!! Srsly? Do you even know what it takes to make a project functional? I've no idea what I'm going to do now.
#doublestandards14 -
Just finished a defect fix, and turns out there's another unrelated but harder bug in the codebase. We are in the last few days of the release.
I told my tech leads that it was an unrelated problem and showed them in detail. I told them I was starting work on it now, but there should probably be a new defect entered for it.
They actually said for me to piggyback the old defect and let this go under the radar. Actually laughed it off like it was no big deal. Like WTF! I don't think its very unreasonable for devs to want separate defects for separate bugs. They're worried about analytics and shit, but I'm the one left holding the rug, looking like I spent a week on a trivial defect.5 -
Sorry, but no sorry.
I don't see that it is ok to make stupid of other people. I mean, it is ok for non-IT people/non-specialist/students didn't know that HTML programmer is not a thing or we can't just turn of the problem/bugs if sth gone wrong.
They aren't stupid. They just misinformed. Just smile (or laugh?) and explain to them.
No one is born knowledgeable of everything. We even learn how to walk, how to read, how to program.
By doing mistakes.3 -
When yo wake up in the morning and you read:
"Upcoming updates to the AWS Lambda....in rare cases, package updates may introduce compatibility issues."
("rare cases", yeah sure. skip everything)
"...You have the following options: 1. Take no actions, 2.blabla 3.blabla..."
Close the blog.
Communicate to the board that due to lack of resources, randoms bugs could happen in the next weeks and that the quality of a 500K$ project is at random risk.
Rant.3 -
PC-Lint is such a useless piece of shit! Tons of warnings with no actual benefit. The obvious motivation behind this crap was to throw as many warnings as this cheap sucker can even generate with no effort to minimise false positives. Typical snakeoil shit, reminds me of ZoneAlarm back then which reported every ping as "attack" just to fool the clueless into buying. Meanwhile, the actual bugs that sophisticated tools can find pass unnoticed through PC-Lint.
-
Typical Windows 10:
When you don't need to do something fast - I'm super fast OS, I have no bugs and I won't throw BSOD's
When you need to do something REALLY fast - Hey, I've got some updates, I'll be installing them during several eternities and I'll throw you some BSOD's cause I can
PS. In such cases I really want to install linux1 -
Android Studio upgrade
Over the weekend I upgraded my android studio and the project files of my current project and all went smoothly (as far as I thought).
I did not touch the project till today as was implementing some few features only for some few unexpected bugs to creap in.Been implementing that feature for some time and thought would be done in a flash only to my disappointment.
Turns after upgrading my SDK they were some conflicting dependencies that had no idea of.
To make it worse my fall to branch was way behind the active one and had to create a new project from scratch and copy paste files.
All this after spending hours in Stack
Overflow and scratching my head.
Lesson learnt to commit more frequently.1 -
Upper mgmt paying an enterprise software vendor 40k US annually. Told vendor No more me QA'ing for them and 'discovering' obvious bugs. Told them to hire QA person and spring for some automated testing software. Yeah I know I am a nice guy but Enough is enough!1
-
Senior dev on our team is concerned that we are raising standards above and beyond what we need to deliver the project.
For 6m+ this project has delivered little, but what there is is full of bugs that got through testing, and no standards (coding or otherwise) in place at all.
I hate dealing with people who preach “good enough” is fine but won’t accept they aren’t even close to doing “good enough”7 -
For future generations :
Bring back cocaine to coca cola.
Since 1904 Coca Cola no longer contains extract from cocaine leaves.
Drugs who made us.
If we live in matrix and we are simulated the general rule would be wipe bugs from the system so ex. if all of people were using cocaine cause they drink coca cola the wipe would be remove cocaine from the coca cola. That would fix the cocaine bug. Cause people in 1904 had almost no knowledge about how world looks like, they were using pigeons to deliver messages. If we bring back cocaine maybe we would also bring back those times, when everyone dropped cocaine in 1939 - 35 years old ourselves were fighting to death between each other cause of rehab.
I wonder how many of those non visual but only statistical bugs we have on this planet. Machine learning is just one of the tools we use to learn about them.1 -
I just updated to Android 9 developer preview 3 and it's total bullshit
Runs perfect. No bugs. WHAT DO YOU THINK YOURE DOING GOOGLE
#notmyandroid
😂😂4 -
How can one "steal" a job anyways? Is not like there's a robot with a gun forcing your boss to fire you and give him the contact instead, which the robot is way better at anyways, producing no bugs and ten times the features you were able to do, and all that for a few bucks of electricity a day... FUCK, WE'RE DOOMED!!!5
-
Class normal people:
Def good day:
"Manager was out, had great lunch, got a. special someone's number, successfully avoided traffic, got in special someone's pants"
Def bad day:
"Stubbed toe this morning, rained all day, broke up w. special someone, sat in traffic for 2 hrs"
Class software dev:
Def good day:
"Wrote lots of working code, little to no bugs, checked in no-probs, ahead od schedule for ship, extra time for ping-pong!"
Def bad day:
"Somone fucked up the latest build, coffee machine's broken, ran out of adderall, manager on everyone's @$$ for a fix, 5 hrs later...no fix, no blames, no coffee, board meeting; fml" -
I just can't wait for Ai, the day will be so beautifully ecstasy filled.
Just sit there, talking, saying what you want, no bugs.
oh my5 -
Purple eye sockets and slightly wrinkled eye pouches when I smile. This is what a developer job gets me after all those hours of frowning my face at bugs all day.
Coding is affecting my health.
No, no, no, this has got to improve. I'm going to make sure I look better this year.2 -
Spent most of this week busting my ass working on a hotfix that came out of nowhere with mega high priority. This annoys me greatly because the hotfix wasn't even fixing a bug, it was adding new functionality because certain customers were being blocked from testing without this specific feature. In my humble opinion, given that we release every weekend, hotfixes should be reserved for actual critical bugs. But anyway, as I probably could have predicted, the code got to QA and exploded. Literally nothing works.
This is what happens when you try to rush out features to satisfy customers. If you try to rush something that is late, you WILL make it later.
Meanwhile there's an issue I'm supposed to be fixing for our next release which goes out this weekend and I've had no time to even look because of this hotfix. And now it's the end of the day and I just feel worn out from stress, tomorrow will no doubt be similar.1 -
First thing is quite simply no overtime, I never EVER work overtime, you get my 8/9 hours a day, where I do work and that is it.
However, as dev's our minds never really shut off from 'coding' so if there are any bugs or complex issues, those most often get resolved when I am out for my run or cycle. -
Project Lead in the morning: This one story needs to be finished till 2pm for the QA department.
Me: No problem, everything is finished and there is only one test case open. It should be finished in no time.
Also me: Spends 7 hours of intensive lagacy code debugging to find out why this shit isn't working sometimes. Try to fix it, broke some other things. Retested all cases and found 3 other minor bugs. End of the day, story is still not finished.
Now: Project Lead is mad, QA guy is mad, I am mad.
Conclusion: I hate debugging legacy code and I never again trust the last open test case!!2 -
happy rant 😄
just finished our group software project in uni (5 students, a way too complicated game) and just got the highest possible mark of all!!🤩🤩🤩
the project was focused on having a working, bug-free game, so yeah our game was UGLY AS FUCK😅 ... but 99% no bugs😎
best group in years😇
next chapter:
human-computer-interaction(is that the translation for Mensch-Computer-Interaktion?), we'll take our games and bitch about their usability and design😅
by the way i was responsible for the design/ux and did a kinda crap job because of too little time😐😅1 -
Boss: Ready for deployment?
Me: No, there's still a few bugs.
Boss: let me know when they are fixed!
(Goes back to desk, runs without any issues)
Me: It all finished.
Boss: Wow how did you fix it so fast.
Me: I have no idea. -
Keep bugs at bay
We have two of these at entrance of our company.
Little do they no bugs don't enter through entrance, been but are born in our computers.
1 -
While people are scared that 1 day our society might get overthrown by robots, I don't worry about that because no matter how hard you try you will always have some bugs3
-
The characters in Euphoria are living the life. Fuck, do drugs, get high, no feature to implement, no bugs to fix.5
-
The LAST stable version of Visual studio was 2019.....
That 2022 is a hot garbage now.....
So many bugs....
Buit I don't know even remotly IDE which I can use insted. VS code ? no thanks.... "First install 1544554 extensions"
I want all in ONE.
Rider ? Fucking joke. Can't even asjust size and font of menus....15 -
iOS 14, two thoughts.
1. It manipulates people. They added app gallery and now when you try to delete app it asks you if it should rather hide it into the app gallery, exploiting your hoarder bias so you have more apps and thus more notifications if you haven't disabled them. That's a no from me.
2. It fixed a LOT of bugs and annoyances. I quit next js because of the exact same thing being important to me — they were busy doing only the new features to constantly pitch and lure investors, they never responded to issues and never fixed anything. I'm happy that Apple realizes that it's important to fix bugs.
Overall I'm happy. My iPhone X is pretty old already (87% battery capacity remaining) but it's much faster with iOS 14 than with iOS 13. The main thing is reduced latency pretty much everywhere. Especially the screenshots, I'm barely detecting the click and the screenshot is already done. No perceivable latency if you ask me. New refreshed look is amazing, backside tap actions are cool, new music app is amazing.
People tell me that apple is forcing you to buy new gadgets with updates but explain to me then WHY my old iphone X got much faster with new iOS? That's a contradiction. If I buy a new iPhone it'll be because of dead battery (that's physics and not exclusively Apple issue) or just because I want 120hz and lidar bokeh.13 -
After inputting all of the defect info into the bug tracking tool, QA writes a quick summary of their findings and goes home.
Love explaining to mgmt why developers could not fix bugs because they had no access to the bug tracking software.
1 day.... X number of bugs... 0 progress -
Good morning Developers
*Voice appears from no where* :
You have to code and complete all the bugs, issues and the frameworks,
By the end of the day.
Your mission, should you choose to accept it?1 -
This code is so horrible I'm too scared to even fix bugs.
No I did not write this code originally.1 -
I have a dream, that one day, a major update of my app will have no bugs and/or crash reports within 24hrs of its release. ;_;1
-
Shitty legacy codebase made by shovelling pile of different shit by some 'cool dude' who left the company 3 years ago. Fixing bugs on this pile of shit all the time, but also I have to document everything as documentation wasn't there at all and fix the whole damn project in the meantime. No linters, no types, ancient libraries that have shitton of issues, hacky behaviours wherever you look, no tests whatsoever.
Except when we want to refactor/rewrite we don't get time for fixing the whole shit as it is worthless - there's no value for customers in that.
the other one was shitty HR talk which consisted of bashing on my technical competencies by computer illiterate troglodyte after which I left the company. They asked me could I stay for 2 more months.
That was that one single NO that felt so great that I will remember it for the rest of my life. -
Fuck randomly appearing and disappearing bugs when I compile a project in C with no changes in the source code.
Fuck these microbits in the ass.
Took me three fucking days to battle them. Aaaargh!11 -
tools people REALLY wanna use are written like garbage
and also very active, in terms of tickets and pull requests
but the code is overly complex for no reason and a mess, turns out
I looked at the codebase and I have no clue what's going on
then found the API it's calling and I'm sitting here going "Jesus fuck I could've just wrote my own"
it's actually really strange, I see this pattern often of tools tons of people rely on and want to use but they're coded horribly, tons of bugs, and the code is entirely incomprehensible. though all the low effort pull requests is a new one I guess, generally there's no activity or the maintainer is just gone (maybe it's AI?)
anyway then I looked at the API it's wrapping and I'm confused why this library has such shit usability, and furthermore why the hell the code was like that cuz I read that first for about an hour and just kept going in circles. bruh what
guess I'll find out tomorrow if I'm signing up for unanticipated complexity or these people really did mess this up2 -
Just checked on AltRant in the App Store Connect dashboard, and got a nasty surprise: a pile (22 in total) of crashes, all of them because of things I never thought would cause a crash...
Thank you for all the feedback, today I am going on an army exam. After that - bugfixes are supposed to arrive soon.4 -
Any of you are annoyed by your non-technical manager work practices?
Every release I feel like our manager's goal is to have our planning and results look good in front of higher management, no matter if it is true or not.
Oh this big task could not be done because we had to plan 4 months in advance with no info and poorly done requirements? Well let's just push it to the next release we can't have unfinished tasks logged in.
Oh we don't have time to work on tech debt and refactoring, there are too many features and bugfixes to do. Well maybe that is why there are so many bugs, eh?
Oh your automated test results need to all look perfect, does not matter if your test are even good or actually doing anything in the first place, as long as it passes.
Also, I was promised agile and got a waterfall-like bullshit process instead that barely works.
Anyways just morning rambling.1 -
I think I won't be happy if all my codes works perfect no bugs at and all, I think I'll feel like my life have no purposes or as the wizard will say the coder have no destiny , how would you feel if all your codes works every time .1
-
Any of the several hundred (no joke) xss, csrf or sql injection bugs I've fixed in our legacy apps...
-
I was writing in Haskell GHC - and after I got tired of fixing some tuple problem I had no idea about, I typed "fix bugs" and pressed enter....
-
While showing the rest service demo a senior 10+ years dev ran into session issues in chrome. I asked him to open private/incognito. He opened ie,edge, closed all chrome, tried back, nothing. Had no clue whatsoever.
At last I asked him to do ctrl shift n in chrome & dark chrome opened up where he could use the test accounts to validate the bugs. He is still confused what happened4 -
Person I am grading labelled “not having bugs” as their website feature... if it wasn’t 2018, I probably would say that’s a standard part of any website or software. Now... at least they’re not passing it off as early access.
-
Bugs: These are not bed bugs. For programmer they are a nightmare, to customer we introduce them as a new feature and say, “My software has no bug. It just develops random features.”
-
Just started doing my project for Java Class, a Polynomial Calculator App.
Get it done, get a dozen errors. Fix every bug. Find other bugs when inputting.
Brainstorm 5 minutes and realize I could change the way I write the polynomial at input.
Change 20 lines of code that do String, Split, Run through the split and check for coefficient and power, parse them to float in an array to specific positiona - to 5 simple lines.
Program works fine. No more previous errors.
Have the great idea to add the following:
-If you divide the Polynomial by 0 output "Are you retarded?"
P.s. I'm happy about my first project even if I hate Java.4 -
Working for a little SharePoint-Company while studying.
Have to hunt bugs.
Found a major bug which kills one of our customers SharePoint-Site completely because of code pasta.
Told my supervisor about the bug and reported it.
"yeh. we will fix it now"
2h later they started to go live.
"Did you fix the bug?"
"No. Wanted to have the system live asap."
On my way home I got a call.
"We need you back here in the office"
"Why?"
"It crashed. Is not reachable anymore. Help fixing it"
fuck off
-
Happy New year to all my fellow devs. I hope that this year brings you easy to fix bugs and no harsh deadlines
-
My graphics card is only able to play video on YouTube with max resolution 720p. If I choose 1080p then I get less than 1 frame per second playback.
This is disappointing; seeing that Radeon 5600 XT graphics card can only play videos in 720p. I am pretty sure that poor performance is caused by Radeon graphics driver; there are no other problems of any kind on my system.
Radeon software team = 🤡🤡🤡
The bugs without end need to be stopped. AMD software deserve their bad reputation 100%11 -
I just love when I correct 20 little bugs, and always with that "Ah!! Of course!" feeling, before finding the little ';'...
😅😅 -
The bugs that make you think are the best/worst.
Had a ghost foreign key constraint from a dropped table. Cant drop it from a non existant table.
Turns out the dev copied a file for the new table and since you can technically name those foreign keys anything you want, there were no errors when he ran it.
Also sloppy/overworked dev teammates are the worst...
Also I'm pretty sure rule 2 of programming is "Never Copy and Paste" -
It’s hard keeping your girlfriend satisfied when you’re being pressured to code with less to no bugs. I mean, doesn’t she understand that computers are stunningly stupid, and you have to explain to them every last tiny step that you want them to do, and your explanation can't have any mistakes in it. And why this is the fundamental cause of buggy and insecure software😣4
-
Apparently some manager in the company found out that we produce less bugs if there are more meetings (there is literally no time to write actual code). At least that is the only explanation which comes to my mind WHY I HAVE TO SIT IN THESE SHITTY DISCUSSIONS THE WHOLE DAY TO DISCUSS THE SAME ISSUES AGAIN AND AGAIN.
-
I hate surprises.
I join office after a short leave and the other guy is out with a completely new product I have no clue of. (surprise 1)
Next, he's on leave and now I'm asked to fix bugs.(surprise 2)
Just for the curious, I ended up successfully fixing them and adding 2 features. -
Coming back from a break and I'm fixing some minor bugs in an app I'm developing.
The simulator runs the app perfectly.
Builds to android and iOS;
Shows splash screen then nothing...
No error messages...
The worst part is I didn't change any of the code in the files that are meant to be running at this point.
I'm very confused rn!6 -
Protip: Bugs exist everywhere, also in real life (no pun intended). Trying to think of possible real-life-bugfixes while commuting (train legroom too small, traffic jam on the same spot every day) makes makes the entry to your work projects easier. You simply haven't stopped thinking about bugfixes, only the project changed to "commuting".
-
Android + servers
Hey guys
So cause I barely have time to code I mounted a server with my old cellphone, so I can advance one of my projects at work (it's a helper with stuff like tables and calculators for work [CNC machine] )
The cell phone is a meizu m2 with android 6 (don't buy one, has lots of stupid bugs)
My problem: android terminates the server and a app I use to copy files from Dropbox to the server folder (only work arround the home rooter)
F king meizu bugs : resets lots of definitions to default, like I give permition to the server app to always be on and it changes back to default when I turn off the screen.
So when I turn of the screen the server goes down
Solutions to keep the server always awake?
Also better solution to change /upload the files without Dropbox as an intermediary
Btw the app that syncs also turns off every fucking time (so no updates till I get home)1 -
Fucking jQuery in Polymer 0.5.
When polymer 0.5 was released, things seemed incredibly easy at first, but when you need to do some complex things, the abstraction layer provided by web components are not of much help. Babel wasn't there too, so I ended up using scope hacks to access event listeners (var self = this). Worse, I have to use jQuery because many of things are downright tedious or fucked up back then, including myself.
Now, React is here; No jQuery, no hacks, no web component polyfills, no unsolvable perf bugs, no scope hacks, no 10sec loading time, no regrets.1 -
Okay..
So, what do I have here?
A cross platform mobile app with NO unit tests.
😕
I have to write a big new feature from scratch. (Things can't go wrong, right?)
Started working on it, pointed out problems with the UI/UX designs. The design changed multiple times, still I thought I could finish it by the expected date. And, so I did.
The feature went through testing, and they found bugs. (Surprise...?)
It's already kinda scary to touch someone's code that has no unit tests and no comments. And I think, it's all the more difficult to not introduce bugs.
Also, had to work on the weekend to fix the bugs.
I had some good learnings here, but I'm not sure how I can prevent bugs without unit tests and proper feedback cycle. :/4 -
Apparently I'm to try and fix bugs that are 1-2 years old. Some of which have had work done on them before, so may be in a different state. No reproduction scenarios either.
What the actual fuck? -
So I'm sitting here trying to bodge my way through a member system. These fucknuts really made a bad system..
The task: Export a list of users and their info.
Is there an API available? No, who the fuck would need that shit, even tho the system is built upon Odoo, which has an API!
But it has an export function, you just have to log in and press the right sequence of buttons, because you need the running ID...
Here I discovered the first of many security flaws... "What happens if I post the wrong ID?"... Well, I get access to a file that has nothing to do with me or my users.... What?
Well after some fiddling It works, but holy fuck I found a lot of bugs. And this is a system that is launching in 7 days for us.. Some users have been on it for a year....
How can they ship this bad a product? There's absolute no documentation only a 15-page manual. Guess they don't want developers to develop shit that works in junction with theirs.1 -
Computer science in high school...
Creating algorythm block diagrams using a beta version of app that is 15 years old
and is FULL of bugs.
You do not even have conjunction or disjunction
operators, so you have to create more blocks in order to check more complex conditions, for example.
So I asked the teacher if I can solve those tasks
in C++ and the answer was NO ...
:(3 -
Ok ok ok. I see y'all have nice plans for the new year. Some of you even made a list that will be barely completed or remain unchecked.
Let me tell you my real issues/plans for 2020.
- First things first, I have to update the documentation of the projects that I maintain. Especially the copyright information. (2019 -> 2020)
- I have to check if any of the old software that I use is broken because of the year/date bugs. (you know, that happens)
- And finally I should check my Windows PC. If it's still OK than it means that no malware/virus is activated with a year payload. (it happens too, watch @danooct1 on YT)
Hope it helps someone.1 -
When you go through your code and find a couple of lines and you have no idea what they are there for or what they do. They you find out they don't to anything at all and you can't remember why you wrote them. (I think I was trying to test an alternate solution to a problem but then walked away and forgot about it).
Those lines are still there, it bugs me, but I will remember.1 -
So it's a little bit annoying when your team cant follow simple rules and conventions to enhance the work, I mean, in a reunion we discuss what will be our coding conventions and have and agreement, but now nobody follows it and Ive to keep writing and pushing them to follow rules they created. The best thing is the leader agrees with him saying "we don't have time for following code conventions" but when the code has no comments, no docs at all, the names are absolutely unpredictable and stupid bugs start happening he calls a meeting "to discuss our problems" I mean, for good, the last time we did the same thing
-
I'm currently making an internship at a medical software company and today i found this gem in a js file:
/*
the server does not check if the element was deleted or not; it will return success, no matter what; **it's not a bug, it's a feature**
*/ -
Windows 11 is here. And there is a bug that prevents it from being installed 🐞
I got "incompatible" error so I downloaded MS compat. checker and it says: need TPM
I go to BIOS and enable TPM. The tool now says YES, compatible. But the Windows update panel still says NO, not compatible.
Bottom line, Microsoft does NOT want people to install Windows 11. If they did, then they would not have silly bugs, such as this one. All they had to do is to clear the compat. flag cache after restart7 -
Just what is life
1st I love developing Web Apps
2nd I hate when it has bugs (Always does Everyone does)
3rd More hate for Security related bugs
So I started bug hunting so that even I can make developers hurt I thought I might find peace here
But here we fucking have SQL Injections which are not really that bad easy peasy
But we also have special kind of SQL Injections the Boolean Based ones (Medium Level Demons) and also The Time Based SQL Injections (Medium Level Demon with lots of health consumes too much time has a repetitive process and we have to wait a lot also if you have network lag you are doomed)
No its nice story till here but here it fucking ends the happiness I mean my luck is worst kind of fucking thing anybody ever can have.
I got a mix of both Demons;_;
A Time-Based Boolean SQL Injections yess fuckety amounts of fucking time wasted and redundant fucking process also to make matters worst the fucking famous tool #SQLMAP doesn't work in my case -
Even when the code is right, it's wrong. Like when you are fixing bugs:
"damn, this variable doesn't look like it belongs in this part of the code", but when you look further into it you see that is correct and you continue with the bug and have no idea what the next step should be.1 -
Hi my name is Kray and am an addict. I subconsciously create code with Bugs so I can later solve, I then after get a feeling of deep euphoria. It's like discovering fire albeit it's more like using matches to start one ( kgm Stack overflow.) 😅 But it's a a healthy habit in a safe environment it could be worse, I could be on narcotics... No wait I take it back I have been dabbling with JavaScript 🤦🏾♂️😂😂..2
-
Submenu Boards doesn't show in Firefox 45.5.0 when viewing a single issue. This is really frustrating as I can't move quickly between the sprint board and a specific issue. What also sucks about jira is that there is no way to report bugs like this (perhaps Atlassian sincerely believe that they never have any bugs in their products), leaving devrant as the only resort to let out steam ;)
-
I know that we all hate bugs, but let's be truthful, if there was no bugs, there was no jobs 😂
You will just have to program one time and then the boss will kick your ass out of the company3 -
What should I do, I have a central function that is not documentated and no test-cases are written for it. I have no clue what the method should really do, I know that it works in 99.9% of all cases otherwise we had much more bugs. Now there is one Unit-Test that reports an issue. I tracked it down to this method, no one touched the method nor the unit-test.
My logical thinking says that there is one statement missing, but it could also fuck up another part of the code... (This project has a bad testing coverage :'( )
What would you do?
- copy paste the method for this special case (I would hate me so much for breaking DRY)
- inheritance?! (Would make it more complex and then it would be still untested / undocumented)
- YOLO changing oO?! (hope for luck, just joking)
P.s it's an edge case unit test, the client / customer probably wouldn't realised it if it happens -
I'm not experienced in VB Forms. So can someone who is, tell me if I'm just too inexperienced or if Im right about this?
Im tasked with fixing some bugs in a VB Forms project that a privious employee wrote some years ago. When I opened the project and checked it out, there was over 5600 lines of code in the codebehind for the form.
I feel like this is somewhat bad practice, no comments, no documentation... Nothing. And to top it off, among the worst naming of Subs and variables ever. Stuff like: "Run", "Stop", "Feeder", "When Load".
Oh, and the best part? The guy forgot some test code in the software, so when he left, the software stoped functioning. For real, he coded in a dependency to his own account in The AD.1 -
Looking at the dev world this month like.. gitlab is down.. s3 is down.. isitdown down.. looks like devrant is using s3 as well, so no meme on this rant :/
And for the first time in a long time it's not my problem..
No job, no bugs 😖😭 -
Javascript drama is a never ending horror. I was building an app for a client that says he want reactnative and I used The Platform module without importing guess what? I never saw an error but that part of the code didn't just work and no crashes this is crazy no wonder apps built in JavaScript don't show error in dev but crashes in production javascript is just one comedy that won't cease creating unessary bugs that should not be allowed at the first place, js is just crazy in someways3
-
I see DIY aircraft videos on YouTube every now and then. All of them are from Africa. People are building poorly designed, dangerous planes that don't fly (surprise, isn't it?). I get that they have very limited resources, but what bugs me is… why not just implement WWI-era designs? They require no exotic materials (essentially wood, sheet metal and canvas), can be built relatively easily, and they are literally battle-tested. They _will_ fly. I get that for those people flight is a dream, but why skip the quickest, cheapest and safest way to achieve that dream?
17
Top Tags
Weekly Rant
View