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
-
I'll just tell the client it's where developers go to complain about difficult bugs in their code...
168 -
Hoorah! My code finally works! Now gotta remove those 1000 print statements I used to identify the bugs 😥11
-
Me : So how's the deadlines here?
Coworker : There are none.
Me : ?
Coworker : if they are unrealistic, we push non-working code. Prod comes up with bugs, and we get a new sprint to resolve those bugs.
Me: ╰[ ⁰﹏⁰ ]╯10 -
1 - Programmer produces code he believes is bug-free.
2 - Product is tested. 20 bugs are found.
3- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
4 - Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
5 - Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
6 - Users find 137 new bugs.
7 - Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
8 - Entire testing department gets fired.
9 - Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
10 - New CEO is brought in by board of directors. He raises the programming team's salary to redo the program from scratch.
11 - Programmer produces code he believes is bug-free.
12 - fml9 -
A more experienced friend told me
"don't be a pussy, test in production"
I'm the one fixing the bugs, not him
8 -
That facepalm moment when the client rejects your code saying it's too small, and it might contain bugs.6
-
99 bugs in the code. 99 bugs in the coooode. Squish one out, patch it around. 128 bugs in the code.4
-
- 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 -
0. Problem
1. Thinking of an algo
2. Writing a code
3. Compile
4. Compile Error
5. Fixing bugs
...
6. Finally compiled!!
7. Running a test
8. Run time error
9. Fixing bugs
...
10. Finally I can see the result !!!!
11. Shit!
12. LOGICAL ERROR :/3 -
The knitted Minecraft creeper my girlfriend made for me. More incentive to figure out bugs compared to the usual rubber duck...
5 -
Sitting at home debugging code for the fun of it when... "I would debug 500 bugs, and I would debug 500 more. Just to be the man who debugged a thousand bugs to fall asleep on the floor."1
-
git commit -m "fixed bug where div wasn't resizing with window size change. Next I'll work on new bug which makes it so the pages won't load at all"
3 -
[PM] - "Hey, <that guy> is joining our team for the next 6 sprints"
[Me] - "Really?, <that guy>? You want bugs? Cos' that's how you get bugs"1 -
The 2018 bucket list!
I sort of swear to be a good coder, to take honour and dignity in all the lines I write, I will not take shortcuts, I will obtain a +80% test coverage across my projects, write clean and accurate documentation, and ultimately I will write less bugs!
Yea..., probably not but worth a try anyway!!1 -
These two!!!
Sherlock giving the motivation to do detective work and find the bugs. Dumbledore giving the motivation to use magic and code the solution. :D
8 -
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 -
Rant::aboutMyself(my_code){
Wrote 500+ lines of code without proper documentation. Got 200 little bugs. Got frustrated. Gave up on code. Started documenting it. Step by step. Resolved many silly mistake while documenting the code. Completed documentation. Run the program . Bugs reduced to 10. I'm sooo happy. I LOVE DOCUMENTATION 😍
}2 -
"If debugging is the process of removing software bugs, then programming must be the process of putting them in." - E. W. Dijkstra3
-
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 -
There are two type of bugs that will keep you awake all night.
Mosquitos and bugs in the code.
Both equally annoying1 -
These fucking imbecile devs left me a bunch of bugs in a 150k LOC legacy hell...
Too bad it took some 8 months for them to finally surface in prod. God damned...
Technically, this whole codebase is one giant abyss filled to the brim with bugs.6 -
Merry Christmas as well to all the people who have to program, monitor servers, fix bugs and all the other stuffs!
-
Me...
The language is fine, it's just me who keeps adding bugs to the programs and forgetting semicolons... -
My dev superpower would be finding bugs instantly, because I think looking for bugs is the most time consuming part in programming.1
-
Everytime I don't sit in front of my code (and go for a walk or something), I immediately find bugs or things to improve from all the code I've written, IN MY HEAD. If you have a hard time finding bugs, try this, maybe. Might help.3
-
[...] we should never ignore any part of code. The parts we ignore are where the bugs will hide.
- Uncle Bob1 -
My senior developer says he wont fix any bugs that are reported by any user in the company, because bugs will appear anyway.
I think he needs to change job2 -
Freelance:
Me: I'm done with the major bugs. Can I do the minor bugs tomorrow?
PM: can you hang on just a moment? Can you pls remove the ...
Me: I'll try. I'm experiencing brain dysfunction right now.
PM: Oh? Hahaha! Just a minor tweak tho. Teeheehee.
Me: (fudge)3 -
An iOS app which was basically a wrapper for a giant jQuery eForm.
~5000 lines of custom JS and it broke ALL THE DAMN TIME. A team of us worked on it for about a year and all we ever did was fix bugs. But the bug count never went down. The bugs just got replaced with more bugs.
Thankfully its not live anymore.
After the global thermonuclear war, all that will remain is cockroaches and jQuery. -
Interviewed for a Q&A position.
Found bugs and errors on the test questions just fine.
Found broken assets and errors within the test itself outside of the questions. (Misspellings, typos, broken images, botched styling, etc.)
Didn't get hired because they thought I'd spend too much time finding bugs.
What gives?7 -
When the change log says "fixed bugs and improved performance" only to find the entire application has been redesigned.1
-
Developer of said repo notices the influx of activity, but then just updates the readme by saying there are bugs, not fixing.
Bro I just gave you a PR. Take the fucking PR and that will fix the bugs. -
Added some features to an internal app used by finance. Tester found some bugs, but most of them were due to old code. Tried fixing them, found some more serious bugs that could have a large economic impact. Rewrote the service, squashed all the bugs we found and reduced code by roughly 50%. Felt good.1
-
Once upon a time, devs were evaluated on the number of source lines of code written, and how many bugs were found and fixed. Needless to say, a ten line piece of code became 150 lines, a couple of bugs would be thrown in for good measure.4
-
When I was a kid :
- Bugs eat grass
Now:
- Bugs eat time
I still wonder when will the day come when I write bug-free code in my first attempt (:(8 -
99 little bugs in the code, 99 little huge, take on down, patch it around, 157 little bugs in the code
-
So yesterday I was testing my friend's app which as said by him is 100% okay.
I found 48 major bugs and reported him. His reaction was "Dude these are just minor issues and client don't even know about it. See there is some real bugs?"
RIP to the app developer and the client. -
Making your build site go live at 12am, stay up til 2am working on bugs, wake up at 5am to continue working on bugs.
The programmers life1 -
//Not a Rant
Jakub Steplowski, thank you for this updated UWP app. The time you spent fixing the bugs was worth it!4 -
Who doesn't love bugs, we all love them, they provide the help needed to sleep, whether they were IRL bugs or program bugs
2 -
I'm the bone of my project
Steel is my brain and fire is my eye
I have created over a thousand bugs
Unknown to people, Solve by death.
Have withstood pain to create many function
Yet, those bugs will never be solved
So as I pray, Unlimited Hope Works4 -
Tried to be normal and sit outside in the sun while my kid played.
Damn sun glare on the laptop and bugs. -
99 little bugs in the code
99 little bugs
Take one down and pass it around
127 little bugs in the code2 -
This is for all those people that like dark themes and when asked why you say it's because light attracts bugs.
I would like to explain how that is just so wrong. Bugs attracted to light are moths and a few other flying bugs.
The rest of the bugs live and thrive in darkeness. Cockroaches, bedbugs, spiders etc.
In fact mosquitoes hunt at night and prefer to hunt in the dark.
I just had to put this out there.6 -
This is what they teach in management schools apparently
0 bugs - Dev doesn’t exist
1 bug - There’s a bug!
2 bugs - There’s many bugs
3 bugs - There’s so many bugs
4+ bugs - The app is full of bugs5 -
Project deadline = 7 days
Day 0: start coding
Day 1: few bugs and crashes
Day 2: fixed those bugs project is 30% done
Day 3: ok I have time... sleep
Day 4: sleep
Day 5: sleep
Day 6: 48h coding to finish the project on time.4 -
Fun fact for today
Do you know why we call computer bugs as computer bugs, and not just the formal word for it - "errors and glitches"
Some of you guys might already know this, but still worth sharing:
http://thenextweb.com/shareables/... -
99 little bugs in the code, 99 bugs in the code, 1 bug fixed...compile again, 100 little bugs in the code. 🐞
-
Company uses Trello to track bugs and features the devs are doing.
End of the week the PM: "So what bugs and features did you work on this week?"
If only there was a platform that we could track all these things... 🤦♂️1 -
Right.. I spent the hours leading up to the year change by adding a YouTube to MP3 downloader into my Telegram bot. After a bit of fiddling it turned out okay, and the commit for it was mentioned to the last for the year 2020.
I mentioned this in one of my chats, and users came in with more issues. Told them it's the last commit for the year and I'll keep myself to it. I did adjust the code a bit though to fix those issues, awaiting a commit after midnight.
Midnight passes and 2020 turns into 2021.
I commit the new features, and quickly implemented another one I already thought of as well, but needed its own commit.
Quickly afterwards it turns out that the /mp3 feature actually breaks the bot somewhat, especially on long tracks. Users add a slew of 10h songs into what essentially became a long queue of single-threaded bot action (or rather lack thereof).
I made the /mp3 command accessible to myself only like I did with some other administrative commands already. Still no dice, the bot rejected the commands but executed part of the /mp3 command anyway.
I look a bit further into the code and it turns out that while I was restructuring some functions, I forgot to make the admin() function exit the script after it sends the rejection onwards. This was a serious security issue and meant that all authentication was void. Fortunately the chat did not realize this - one of the commands that became available as a result was literally a terminal on the bot's system.
I fix the issue in 7 commits after midnight total, 3 of which were related to /mp3 and admin(). We're now 1 hour after midnight.
Happy New Year everyone... :')6 -
Do you know guys why a programming bug is called so? It's because the very first time a software crashed it was because of a bug ( a real bug stuck in a bus on the machine!) That caused that 😂 imagine if something else was stuck instead! Like someone'sfinger : hey I fixed that finger but still got 2 critical fingers and 4 small ones7
-
Working out how to continue an interview when the interviewee thinks Test Driven Development is fixing bugs raised by the Test Team5
-
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 -
The day a manager understand the link between short deadlines and amount of bugs, there will be celebrations across the world1
-
Job security:
- Create bugs purposely
- Discover the bugs after a while (if you discover it too quickly it will look suspicious)
- Fix the bug1 -
Fifty little bugs jumping in the code,
One tracked down and dev started to code,
Developer called the compiler,
And the compiler said
Hundred more bugs (& errors) found in the code
-
My first version of a website downloader is complete! I finally worked the bugs out. Now on to the second......3
-
Just got to experience this classic (again):
99 little bugs in the code, take one down, patch it around, 127 little bugs in the code... -
I said to my partner "BABE!! There are bugs on the screen!!!"
She screamed.
When she say the actual screen she wasn't pleased .-.2 -
...It relies on the BouncyCastle cryptography library instead of OpenSSL, yet replicates OpenSSL bugs to guarantee compatibility.2
-
Dijkstra said if debugging it's the art of remove the bugs from the code, programming must be the art of putting bugs in the code.1
-
Lately I've been taking my health more seriously than the bugs ! What about you guys ? How do you stay fit ?
11 -
If Debugging is the process of removing bugs, the Programming must be the process of putting them in.2
-
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 -
When you're teaching your friend how to code via text and miss how simple the bugs were sometimes...
4 -
Fucking hatttteeee airports... I'm a developer not in fucking sales.
My boss let's me fix bugs at the client5 -
I dreamt about bugs this night. Not software bugs, but actual bugs, like a centipede that enjoyed attaching itself to the inside of my palm and such... Not sure if dev related or not, not a good dream either way :/5
-
Worst: Realizing there were crippling and horrible bugs in software that got shipped to customers. Also realizing that we truly don't know the amount of technical debt that contributed to these bugs. My most terrifying comment from a colleague: That software was written on a weekend and the dev was getting 3 hours a sleep a night. One of the bugs I found I was fighting for almost a year to even find what was causing the bug.
Best: Finding those bugs and eradicating them. Having confidence that the bugs we know about are truly dead and gone. Til we meet again...next...3 -
Just realized being a developer means fixing bugs that were caused by fixing other bugs that were caused by fixing the other bugs.
3 -
Headphones, because working while your partner burn and scream in the hell of the bugs they caused is distracting1
-
"You need to learn Angular for a new project. You can do it in any free time you have."
Where "free time" is defined as:
Any time left in between working on priority tasks or bugs, bugs which have failed testing and the weekly array of meetings, tech sessions and meetings to discuss the progress in learning Angular. -
If debugging is the process of removing software bugs, then programming must be the process of putting them in.
-
Doing GUI agile testing with the QA before passing my code to test server. I do this 'cause the QA marked in the past a lot of bugs that aren't bugs because he didn't liked the wording (in spanish there's A LOT of ways to say the same thing), the color of a button or an icon, and this delayed the release of the code a lot of times. So, this way I can change things to avoid unnecessary bugs... if the QA is not so busy XD
-
Without requirements or design, programming is the art of adding bugs to an empty text file ;)......!
-
> somehow decides to fix two bugs at 3 a.m, since they looked simple enough
> fixes bugs
> also causes a memory leak in the same JS script
> next morning the app compiled but kept crashing (duh)
> obviously cant remember what happened
> hangover doesnt let me think, i.e forgets to check the Local History in the IDE
> spends an extra 2 hours. -
Instead of actually fixing bugs, most of my latest PRs have been adding "debug features" that make me look productive but really just enable my total unwillingness to actually fix the bugs.1
-
Sing: "110 little bugs in my code,
110 little bugs,
Fixing one bug,
Compiling again
Now there are 121 little bugs in the code"3 -
Best feeling?
Just leaving the office with a well-working codebase. And no bugs to fix.... until tomorrow morning. -
Life quote : Your Karma is directly proportional to the Number of bugs you get, when you are on call.
:D -
Just reported a minor tracking bug I found on WebKit to the WebKit bugzilla, and I have a few thoughts:
1. Apple product security can be kind of vague sometimes - they generally don't comment on bugs as they're fixing them, from the looks of it, and I'm not sure why that is policy.
2. Tracking bugs *are* security bugs in WebKit, which is quite neat in a way. What amazes me is how Firefox has had a way to detect private browsing for years that they are still working on addressing (indexedDB doesn't work in private browsing), and chrome occasionally has a thing or two that works, with Safari, Apple consistently plays whack-a-mole with these bugs - news sites that attempt to detect private browsing generally have a more difficult time with Safari/WebKit than with other browsers.
I guess a part of that could be bragging rights - since tracking bugs (and private browsing detection bugs, I think) count as security bugs, people like yours truly are more incentivised to report them to Apple because then you get to say "I found a security bug", and internal prioritisation is also higher for them. -
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
-
My day today? Fixing bugs caused by the Change to the Summer time here in Germany.
Congratulations. #nice2 -
Bugs are good in code. It shows that you're Human. You make mistakes. And you're willing to correct them.
But when they're someone else's bugs in a piece of code they didn't give a flying fuck about documentation, bugs can tick one off. The bigger the project, the better the documentation needs to be. And I'm not taking about java docs. Put proper comments in your code. Especially when it's not a personal project and you fully intend to leave the company. -
It not Christmas until you program a game you have be working on for the last few months. I've been gifted with two bugs today. Oh, what fun it is to fix bugs on a one horse powered laptop!2
-
The characters in Euphoria are living the life. Fuck, do drugs, get high, no feature to implement, no bugs to fix.5
-
Reading through the bugs list on Trello...
- change colour and style of button to make it more prominent
- change default for select box
- add a popup to explain the UI on 1st visit
- if I don't save the entry, show alert to user on exit
- remove the map button under the map that links via auto scroll to the map above it
- remove the settings options for the items we designed but you couldn't implement due to lack of time / budget / low priority
It goes on, seriously...
FFS1 -
I have a disagreement with my product owner (PO). Our team develops APIs in Mulesoft. We've got a release coming up and PO wants to release one of the APIs that has *some* working endpoints, but other endpoints in that same API have some open bugs.
Given that it's *unlikely* that those broken endpoints will be used, does it seem like good practice to release the API with known bugs in it to hit the deadline?
Understand that we're not just releasing the working endpoints. We're releasing all of it, bugs and all. PO's logic is that those broken endpoints won't be used therefore it's fine to send known bugs into production.
I just need some advice in dealing with this6 -
What’s your favourite coding joke?
Mine is:
Why do programmers use dark mode?
Because light attracts the bugs!14 -
i have seen bugs getting into prod but not the local language getting into prod. what language is this?
15 -
When spring arrives the mistyping bugs increases by 512% i sneeze every line of code, it's a torture.2
-
Is it possible to have an "epistemological bug crisis"? Because i feel like everything I referred to as bugs in my early career weren't true bugs, they were just bad programming or architecture flaws. I feel like real "bugs" are weird issues with the language, compiler, module, etc... that should work one way but work another way. Anyone else had that experience?
This gives rise to the secondary question: who perpetuates the idea that bugs are just "anything wrong with the current codebase"?3 -
did anybody encounter any bugs in the devRant app? If yes, I want to see the devs ranting about it 😂😂4
-
When your non-dev colleagues report bugs that aren't explained and they write the whole issue into the subject of an email.
-
Been ‘working’ on this game for the last 5 months now. I love making it but I haven’t gotten any where because there are too many bugs. Like, it’s all bugs.
I started the project when I started learning game development and with all the time I’ve put in it I don’t want to kill it.
Anyone else have a project that they are working on, where they don’t even make progress on it, they just fix bugs?2 -
That feeling when you find the god damn bug after 2 hours.. however, it made me better understand my code, so thank you tiny bug❤
-
If debugging is the process of removing software bugs, then programming must be the process if putting them in
-
Management fixes our slow running buggy code problem by exactly copying every file into separate version control depots so that Dept A does have to deal with Dept B bugs and Dept B does have to deal with Dept A bugs to the same files.1
-
This code is huge ! THAT MEANS IT HAS HUGE BUGS !
FIX AND PATCH !
FIX AND PATCH YOUR BUGS !
Basically the reason I want to work on a big codebase one day is to be able to scream that
Winks if you get the reference (just so you know, I didn't read it fully)2 -
The first company I worked for had a policy to not ship any release, service pack or hot fix as long as there were still open bugs with the severity "critical" or "blocker". They wanted to ship a service pack nonetheless, but without violating the rule and thus keeping their KPI unharmed. So the support guys got in touch with developers and asked them to lower the severity of certain "critical" bugs. They said we by all means need to write into the comments that the severity of those bugs has to be reset after the service pack was shipped, so that those important bugs would not be left behind.
- Support team violates the rules set up by themselves.
- Developers had the actual work of doing so (and the blame to catch).
- The Support team's KPI just remained unharmed.1 -
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 -
Scope creep is the worst, and it's always last minute which causes bugs, which causes unhappy scope creeping clients.. :-/
-
Me: Writes tests while fixing bug
Supervisor: "I'd suggest fixing other bugs and then picking up test cases"
Well the reasons we have so many bugs is that you let our off-shore devs just write code with ZERO code coverage!! -
Any of the several hundred (no joke) xss, csrf or sql injection bugs I've fixed in our legacy apps...
-
Currently in our 4th cycle of manual regression testing for a release and still finding bugs. Automated tests? What are those? That sounds an awful lot like it would take time to implement. Time that could be spent fixing the bugs and getting the release out the door.
When release dates take priority over quality.... -
At the place where I am interning right now, most QAs that file bugs are running code that is nearly 6 months old. 95% of the bugs they file don't exist anymore in the current code -_-
This is in spite of testing environments available with the latest code deployed :/ They just refuse to use them!1 -
My Project Inner Voice : "I'm not alone. I can hear them... I can hear the bugs voices... I can sense theirs feelings... I'm not alone... The bugs feelings... They're eager to ruin me... They're what make me useless and rejected!!"
-
Sometimes I wonder how big it companies with more then 500k net worth get away with bugs in their webapps.
In my company we also have bugs but I am the only dev and we won't hit the 100k Salesmark with our software.3 -
Never Ending Project
"What's make software development great?"
"What's it?"
"We must catch bugs all the time."
"Oh..."1 -
They're calling me the exterminator at work. I would take that as a compliment if it hadn't been me who introduced the bugs.
-
The worse bugs ain't those that show up on your terminal<If you got those kinda bugs-you're lucky>. But are those that don't show up at your terminal, but still give you the worse version of production.
-
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 -
99 little bugs in the code, 99 little bugs in the code. Take one down, patch it around 117 little bugs in the code.
-____________- -
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 -
"Bugs"
all these...
i got bugs
i got bugs in my room
bugs in my bed
bugs in my ears
their eggs in my head
bugs in my pockets
bugs in my shoes
bugs in the way i feel about you
bugs on my window
trying to get in
they don't go nowhere
waiting, waiting...
bugs on my ceiling
crowded the floor
standing, sitting, kneeling...
a few block the door
and now the question's:
do i kill them?
become their friend?
do i eat them?
raw or well done?
do i trick them?
i don't think they're that dumb
do i join them?
looks like that's the one
i got bugs on my skin
tickle my nausea
i let it happen again
they're always takin' over
i see they surround me, i see...
see them deciding my fate
oh, that which was once...was once up to me...
now it's too late
i got bugs in my room...one on one
that's when i had a chance
i'll just stop now
i'll become naked
and with the...i'll become one -
Debugging is removing various bugs from program code. So, programming is about creating and adding these very bugs to the code?👾1
-
Version 1 of any software is full of bugs. Version 2 fixes all the bugs and is great. Version 3 adds all the things users ask for, but hides all the great stuff in Version 2.
;) -
Today I am venting with a text I sent to my friend and colleague:
"Awh fuck when I tried to get all the pieces together - migration and elitism - there were bugs everywhere, even from places I thought I had sorted out. BUGS, BUGS never die! 🐛🐜🕷🐛🐞" -
!rant
You know I used to be fucked up in almost every aspect of life: academically, socially, financially etc. But I am happy I am able to fight back. After my college semester exams finished, I am so happy to enjoy such a great social life. Like I can go and hangout each and every day and night, whereas earlier I would be in my room all day and night, infact even my neighbors would question my existence. But now its so much fun to hangout, feels really great. :') -
Doing the application and the server make you feel like a god... but soon the Devil comes to visit. Damn bugs
-
If debugging is the process of removing software bugs, then programming must be the process of putting them in.1
-
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 -
When something is still broken after I fix it
When fixing one bug creates two more bugs
When I am too lazy to do anything at all
When I have to fix bugs in code I did not write
Whether the sun is shining or not,
whether it is hot outside or cold,
I always feel the same...1 -
Colleague didn't properly test a software deliverable...team wasted 2 days integrating the software due to bugs. 😭😭
-
Piece of trash software that doesn’t work as intended, guess what, after wasting countless hours solving bugs, more are to come, after you buy the trash ass code the application doesn’t work as the demo presented on the website does, trash ass bloated php 2nd hand full of bugs code.
IF YOU SELL SOMETHING MAKE SURE IT WORKS BEFOREHAND3 -
Why do C programmers prefer dark mode?
Because the light attracts bugs, and in C, they're harder to find.3 -
Wanna test the level of your patience go solve some bugs in apps(pro level apps).They take the shit out of u .
Top Tags
Weekly Rant
View