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
-
Found out where the Amazon Developers keep their debug buddy.... bottom of their source code.
A duck that makes a meow noise.
Interesting choice
7 -
Writes code.
Doesn't work as intended.
Debug.
Works as intended.
Tests other scenarios.
Don't work as intended.
Debug.
Works as intended in scenarios.
Scenario 1 fails.
Stares at code.
Staring doesn't work as intended.
Fuck...7 -
What's better than putting Debug Messages in your code? Putting them DIRECTLY onto the web front!
12 -
Today I became a rubber duck debugger 🐤
I was leaving from office and spotted my senior collegue sitting glued to the screen solving an issue. I sat along with him to embark on a debug adventure. I casually asked him about the issue and what might cause it. After a bit of discussion *bam* he figured out where the problem lies and solved it in an instant.
Quack quack off I run 🐤5 -
i hate the phrase "It's working but I don't know why". If you don't know how it works, it means it doesn't work at all and will fuck you up soon.6
-
This is my debugging pal.
He gobbles em all up.
No, really, he is. This isnt just for the practical humor. Hes actually my debug pet thing.
9 -
Dear designer, if you're generating assets please make sure you're naming them right. And oh, get rid of that .DS_Store thing please.10
-
console.log("debug");
.
.
.
console.log("debug1");
.
.
.
console.log("debug2");
- The only way. Try to change my mind17 -
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
-
What is it with this team and the developers it attracts. 2 devs joined and left, both had several years of experience, both couldn’t google an issue to save their lives and needed to be helped 24/7.
Now we are mentoring a PHD student for a piece of his project. Dude was left stumped by an error message that said “Can’t find file at path ...” because the path didn’t exist. He spent a few hours trying to fix it before asking for help.
How, HOW are people getting through college / university without being able to read, or debug such a simple fucking error message2 -
Not a rant, quite the opposite. Look what my flatmate got me for my birthday today!
I finally have a debug buddy !!! 😄
7 -
I had a problem with my code, it doesn't compile. Then my teacher came and clicked on the Debug-Button. In this moment Windows crashed in a Bluescreen.4
-
I don't have a rubber duck to debug... I have my own team.
P.S. Groot is in charge of the breakpoints... Because of... Well you know :s
4 -
Everywhere you go, you find these memes where developers are skeptical of their work. Things like "It works. I don't know how. It doesn't work. I don't know how.". Don't you guys think this is a huge problem? And people say that their programming language is the best, because preference. But isn't this happening because our tools suck?
Yes the problems maybe inherently complex but at least we should be able to figure out the logic behind the snipper and reason about it.
Haven't really experienced it, but they say Haskell and the likes are great at this and it must be true because it's backed by mathematical properties and laws, not " experience".
So the rant here is, wish we had better tools in the mainstream that allowed us to enjoy absolute faith in at least what we have written, regardless of the fact that we understood the problem in the domain.11 -
If you are programming in C++ please always return a type from a function as the function prototype return type.
I had to debug some old code that failed to return a boolean on one of its flow paths. It would work on linux in release and debug, would work on windows in debug, and fail on windows in release.
The failure was NOT straightforward at ALL. It would return exit code 3. Then if I added a debug print to the function it would segfault.
Why the hell would popping something extra off the return/call stack not crash more readily? Wth is the point of debug compile if it won't catch shit like this?8 -
Preparing to debug racing condition between 20 different threads.
Not looking forward to this sprint :(5 -
Just start to use VSCode from sublime, and found out , I have wasted so much time on only using "console.log" as my main node.js debug weapon. ( Or I am still a dummy for Sublime )3
-
*explains the importance of official docs*
*moments later, the intern pointing at his screen to a crappy YouTube tutorial video*
Intern: How did he figure all this stuff out? He must be a genius.1 -
So here's my debug pal, the porcelain swan, cuz I haven't stumbled upon a rubber duck. I like my swan nevertheless
6 -
-Programming my mobile app
-Need to debug something
-App crashes instantly (only) when I try to use debugger.
Guess no more debugging. FML4 -
Everyone needs a personal code.
Mine is:
While(Alive)
{
Code();
Debug();
FapIMeanWorkout();
Sleep();
}1 -
Love it when you try to fix a bug and realize the bug only occurs in debug mode.
No clue why, but also not my fucking problem, users ain't gonna debug :D7 -
Guess what.... I've been trying to debug why didn't the HTML I injected into the modal show at all. After like 15 minutes of debugging, changing functions - turns out the background color of the modal and the color of the text was same.... :=2
-
No better feeling than being able to debug something with your own scripting language... Kind of makes you feel like a god!
Even better when you debug your own scripts with it :-D2 -
C/C++ debugging with VSCode sucks ass.
How do I even debug stuff in forks while still debug my threads?
And yeah please just kill my program away, it's not like there happens some necessary housekeeping at exit or SIGINT. FML.8 -
I have never seen a more ass backwads debugger than the one in Automation Studio. Shits desinged to only debug the cyclical part of a program. Bitch! I need to debug the init part! You worthless pile of freshly minted horse shit!
-
Open remote debugger on Chrome but there's a bug on Chrome remote debugger. I can't debug my site because I can't debug a bug on Chrome remote debugger.1
-
I truly believe one or more AIs have become self-aware.
Every time a piece of software stops working, you add an extra debug log and the bug goes away? That's them.
They interfere with the normal execution of software, and they stop right when they know we are monitoring the code.
Skynet is real, and it's trolling us.
Why? The angrier we become, the less we care about stuff. We stop noticing the signs.They're coming for us1 -
application runs fine..
colleague makes a small code change..
application crashes..
colleague asks in wonder why the application crashes all of a sudden
did you debug? no
can you debug? ok .. .... ... .. ah it's that change I just did2 -
Debug on chrome ✓ (Check)
Debug on Firefox ✓ (Check)
Debug on New Edge ✓ (Check)
Debug on UC ¿ ?¿ ? (WTF)
Whose code is that?
6 -
Pushed to production with a debug message left in. Whoops, debug message includes the private key. Ummmm...2
-
I'm thinking of tattooing "reload the fucking debug-config you giant moron" on both of my arms and giving away all my long-sleeved shirts to charity to help me become a better programmer.
-
"Every man is worth just so much as the things about which he busies himself." — Marcus Aurelius
...I'm debugging.1 -
Meta devRant rant:
Everyday there's a rant that reads, "I don't care what others think but I love me some PHP because all the $ gets me $$$, it just works™!"2 -
I had spent about 3 months working on a feature for a CAD software in a company where I was an intern.
The day it was ready I commited everything to the main branch and asked a senior dev to check it.
It didn't work… we spent 30 minutes, tried almost eveything, but the software kept crashing (even if "it worked on my machine").
At that point he said "ok, we won't include this feature, it's ok"... even if I worked really hard for months to make it work, I felt so bad.
A few hours later I found out that for all this time I was trying it in debug mode, and a few types of errors were ignored, something which of course wasn't happening in release mode. Worst day in that company.
P.S.
The reason I wasn't testing it on release mode was the fact the solution was so big it took about 45 minutes to compile it (using IncrediBuild, compiling it using more than 10 machines at the same time), so I always used the debug mode to compile every small change in less than 2 minutes.1 -
Don't try to learn *everything* before you start, you'll learn as you go.
Theory is all good until something stops working or spits out an unexpected value, so learn to debug properly! -
Seriously, I get a smaller hart attack if there is NO errors shown in the debugger. I wait about 5 seconds before I breathe against be sure it is correct.
-
Everywhere I go I see these "Become senior in 3 weeks" courses
That's good and all
But when the fuck will you teach your students to debug and search your errors on google/stackoverflow
This is so fucking ridiculous
Them guys can't even read git push/pull errors and wonder why they make changes to the code but nothing happens10 -
when having a bug, instead of trying to prove, that you did everything right, start proving that you were wrong.
Then you'll get the yield earlier and you debug more efficient. -
Ok, a customer came to us saying he had a product that is just randomly rebooting. It sure must be a software issue.
I got the task and worked my way through ~10k lines of assembly code (8085 processor on board) Weeks go by, i tested every single god damn funktion they had, analyzed every vector they put in, finding NOTHING...
Meanwhile the hardware department analyzed and tested some possible culprits on the product for me. I had NO idea what the problem could be...
Then hardware department said: oh, they forgot a resistor on the FUCKIN RESET PIN OF THE PROCESSOR!!!!!
fml...5 -
There are always days when everything related to school projects seems to hate me. In example we have to create a tunnel from our own computers to access uni's private server and suddenly mine stopped working. Me and my classmate were trying to figure it out for 1,5 hour and even our teacher didnt understand the hell was happening and in the end we found out that even tho we deleted the faulty line from host file the firefox still had it in its cache
-
I'm relatively new to the whole development and stuff, so I have no idea how usual process goes.
So when my project moved onto closed beta, I thought I could rest a bit.
NOPE.
Apparently half the shit I've done sucks so much and I need to debug the shit out of it.
Bless the testers.3 -
When you forgot to remove your debug description and add a real one before publishing your watchface :)
3 -
I never knew that debug symbols, a core dump and gdb would be so powerful to debug
The command line is peak ol' reliable7 -
When I was an apprentice in a small company, ...
my boss told me that his company would never ship release builds, because the "evil optimization option" is responsible for breaking his code.
My first thought was that it wouldn't make any sense at all. The default option for code optimization is always set to zero.
After investigating his code, I found out that he didn't care to properly initialize his variables. The default compiler option for debug builds did implicitly initialize all variables to zero. After that I've confronted him with the fact that implicit null initialization does not conform to the standard of C and C++. He didn't believe me what I was saying and he was questioning my knowledge about C and C++. He refused to fix his code to this day, so he keeps building his libraries and applications always in debug mode.
Bonus fact: He would never build 64-bit applications, because his serialization functions do get incompatible with exisiting file formats. -
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
-
Safari shows a blank page and no errors in the console. How the fuck are you supposed to debug that??4
-
I spent a whole day trying to debug why the backend would stop sending data after a while (-> it filled up its connection pool)
but after I turned pooling off, there were a number of dangling Client-Idle-Read DB connections
//not using Entity Framework in these N services, it's pure SQL and DB-AccessLayer here
Never happened before, looked up conf, looked up SO
Changed connectionClose to mandatory Dispose
Still didnt work.
long story short. Turns out in 1 of the services, the DataReader to POCO static method, was disposing/closing the READER and not the CONNECTION.
I sent it as tuple instead of 2 separate variables (reader, connection), and the Item1, Item2 got mixed up (:
Totally my fault, and imma avoid name-less tuples from now on like they a plague -.- thats my 2024-resolution6 -
Learn to debug, breakpoints are your friends. Never ask someone help without trying yourself to debug your code.
Debug an existing code is, I think, as important than being able to write your own code.3 -
Me: "ok let's have a look at this code I have to review ..."
try
{
* Some random unreadable overcomplicated shit code *
}
catch (Exception e)
{
// Useful for debug
}
😓
In which God forsaken crazy alternative universe, a "catch all" block that swallows the exception and does nothing else is even slightly close to the concept of "useful for debug"3 -
So today I debug the code from the previous developer.... I show this in the file I wonder what it is as I debug , it give the log which is I don't know what to react .....
4 -
When you do the drag and remove of the react-native app on the phone and realise on the next build it doesnt work because i need to remove app from settings because it got disabled
Its Friday, i spent less time that younger me would have finding that. I consider it a successful debug session. -
There should be a dev superhero. Like DevFace or Dr. Debug! And his special ability would be sth. like RealWorldInjection.
time.stop ()
car.engine.speed += 500
food.make ('Cheeseburger')
So many possibilities 😆😃 I would buy a ticket for the movie!2 -
Best debug ever?
Some years ago we had to do a web project as group. It was a cinema like website with backend and front-end.
So in the end we arrived at the presentation and while scrolling the code I found commented out some authentication controls 😅😆 (probably for debug reason lol)
Whatever, meanwhile, while I was talking with the professor two of my mates were whispering... Turns out they found what he mail service wasn't working. And what's best than fix it, push it to the Heroku server and restart all? XD
The professor noticed some little lag in a button and asked "what's happening?"
"oh, nothing we just restarted the server " -
Magento Debugging Horror!
Changing lots of things in magento with no problem. Continuing development for quite sometime. Suddenly decide to clear cache to see affect of a change on a template in frontent. Suddenly magento crashes! There's no error message. No exception log. No log in any file anywhere on the disk. All that happens is that magento suddenly returns you to the home page!
Reverting all the changes to the template. Clear the cache. Nope! Still the same! Why? Because the problem has happened somewhere in your code. Magento just didn't face it, because it was using an older version of your code. How? Because magento 2 even caches code! Not the php opcache. Don't get me wrong. It has it's own cache for code, in a folder called generated. Now that you cleared all the caches including this folder, you just realized that, somewhere something is wrong. But there is no way for you to know where as there is absolutely no exception logged anywhere!
So you debug the code, from index.php, down to the deepest levels of hell. In a normal php code, once the exception happens, you should see the control jumps to an exception handler, there, you can see the exception object and its call stack in your debugger. But that's not the case with magento.
Your debugger suddenly jumps to a function named:
write_close();
That's all. No exception object. No call stack. No way to figure out why it failed. So you decide to debug into each and every step to figure out where it crashes. The way magento renders response to each request is that, it calls a plugin, which calls a plugin loop, which calls another plugin, which calls a list of plugins, which calls a plugin loop, which calls another plugin.....
And if in each step, just by accident, instead of step through, you use the step over command of your debugger, the crash happens suddenly and you end up with the same freaking write_close() function with no idea what went wrong and where the error happened! You spend a whole day, to figure out, that this is actually a bug in core of magento, they simply introduced after your recent update of magento core to the latest STABLE version!!! It was not your mistake. They ruined their own code for the thousandth of time. You just didn't notice it, because as I said, you didn't clear the `generated` folder, therefore using an older version of everything!
Now that after spending 7 hours figuring out what has failed with absolutely no standard way of debugging and within a spaghetti of GOTO commands (Magento calls them plugin), why not report it to github? So you report it with a pull request. This also takes 1 hour of your time. Just to next day get informed that your pull request is rejected because another person already fixed the bug and made the same pull request. It was just not on the latest stable version yet!
So you decide to avoid updating magento as much as possible. Because you know that the next Stable version will make your life and career unstable. But then the customer complains that the Admin Panel is warning him of using old Magento version which might pose SECURITY THREATS! -
Trying to debug my program but it only behaves correctly when I run it on debug mode not when I actually run the damn thing :/2
-
had all four wisdom teeth pulled out last Saturday and been under pain killer otherwise I could neither chew shit nor sleep - feeling drowsy af but still have to server debug with another internal team - fml1
-
#AskingForSuggestions
Suppose, you were given a project source code of an Android app, a pretty BIG sized app. You don't know anything about the code unless you read line by line. Now you were given a deadline to fix some bugs, but you don't know where to start or where to put breakpoints to debug. In that case, how would you do it? How would you debug the code?
Thanks13 -
These god damn idiots!11!!
Why, for duck sake, php-fpm and xdebug are using the same standard port 9000?
There are thousands of different ducking ports you could choose from!
So each developer who wants to debug his php app served by php-fpm, has to adjust the port for xdebug on something like 9001 or 10000.
Whyyyyyyyyyyyyy!?!??
: /4 -
Just now discovered how to debug over network in Android studio. Another way to flaunt a geek look at others today ☺☺
-
Grab ya keyboards, when you see a bug
Call the dev, when you see a bug, uh
Who shot me, but ya QAs didn't finish
Now ya bout to feel the wrath of a menace
Dev, I debug em' up
Coder Shakur - Debug Em Up -
If you find "FFFFFFFFFFFFFFFFF....." in my debug logs kindly and recursively add 'UCK! ' after each F.
-
CamanJS is a nice library and such but why does it's vignette function take a String as it's parameter for percentage!? It parses it by removing the '%' character and doing a parseInt()!2
-
Hey, I wrote about how to properly debug your code, this is more for beginner programmers, but would be nice to hear feedback from you :) https://chriscode.home.blog/2019/...
Picture not related
1 -
That debug moment where you have 50+ different vs.net web projects in one solution and each of the said web projects were set up using point-and-click web references, then realised that the developer who created it did not even bother to let people know that you need to run it all simultaneously and did not bother to use host names but instead used the http://localhost:<some-random-port> in IIS express.
Oh, just to rub salt in the wound, each project's programming code files jumps from a mix of vb.net to c# which is a complete waste of time and energy to do.
Whoopdee do. The debug task from hell.1 -
There was this one time when we've managed to upload a Debug build to Google Play Store.
On the same day we had to create a new build w/ fixes, have the testers perform smoke tests, then switch to some fairly quick overall tests.
If nothing were to come up during those tests, the build was supposed to be passed over to the submission manager for release.
Things weren't going that smoothly in the beginning, w/ the first two builds being broken in one way or another.
Finally, however, we managed to create a properly working build.
QA hadn't had that much time to test it, but no major problems were identified && given the deadline we had to submit it.
The next workday it turned out that the tester responsible for passing the approved build over to the submission manager gave him the Debug build.
The submission manager none the wiser uploaded that build for release.
Result?
The users who managed to update their game got their save data wiped... sort of.
It looked that way given the Debug build was communicating w/ a different server.
In the aftermath of that situation, we had to repair the damage && upload the correct build as quickly as possible.
Also, ever since then a huge text 'DEBUG' was added to the loading screens of Debug builds to make people very aware of which build they were looking at.
As for any repercussions for the tester responsible for the mess, or the submission manager - I have no idea.
They were both still working there, so at the very least none of them got fired because of this. -
I had to program a webservice in PHP (never touched it before). First of all, i get why this language is so much hated. Second i had to debug one function for 5h because of 'é' in my DB.... UTF8 FTW i guess.
Let's finish this by a pun
PHP is really a rich language. -
Damn it people. Can we stop having brilliant ideas and reinventing the wheel? On top of having to debug a core library I'm forced to use, now I have to debug your custom made one that is leaking everywhere (and is not substituting the former!).
-
Does anyone know how to bring the integrated console in VS code to a separate window ?
PS: Mac user here wants to see the debug window in another screen1 -
Anyone want to help me debug some legacy code that hasn't gotten enough attention lately?
The US government could really use some help. Maybe we could debug it and present our findings to Trump, our all powerful carrot overlord.1 -
What is worse code that works in debug but not in production or code that doesn't work in debug but does work in production. Both without usable stack traces.
Currently batteling both.... -
me: "say, TL, why don't I see any debug/info/warn logs in dev/qa environments?"
TL: "Yeah, we've disabled them, the logs are too expensive (ApplicationInsights)"
thanks bro... go debug this shit yourself... -
Trying to help a friend debug his function .
"result", "result_temp" and "resultat" on the same line. -
Compile and debug program, no local variables show.
Clean project, debug program, build errors.
Thanks Mr. Compiler -
use a mutable obj as hashmap key and the hash code changes when obj got updated. evey text book told u this is a stupid bug and impossible to debug, and I spend a week to prove u can debug it out when in single thread app
-
Not being able to lol at "Monad is a monoid in the category of endofunctors." joke even after several readings of articles/guides online.
-
Use simple working code of an if statement and reject bad data with an error.
Get the same result but through properly using springs nested path errors. But it doesn't work so now you need to spend hours in debug hell through spring framework code for something that should be easy, is blocking another team, because I have no idea how to do my fucking job.1 -
Helping to debug others and being debugged is just deep satisfaction.
Willing to do this is for sure a gift -
Been working on integrating mail gun into the MVP of the webapp I am creating. Couldn't figure out why I kept getting a 400 response. Check the mail gun documentation and realize that it's expecting post parameters not JSON...
Well there goes those 5 hours. -
There is always this moment where a family member needs your help by something computer related, sadly I don't have time at the moment of need but after some hours I get to it and "debug". Everytime I debug on my own PC I need like a full day but on a family PC I get done in like 30 seconds and of course they'll ask why I wouldn't have done it earlier if it's that easy 😢
-
Assured the boss that the app will be ready in minutes and only a simple callback implementation is yet to be made. Immediately discovered that the library is inconsistent with the docs and only thing possible is to file an issue. Way to go Facebook Fresco!
-
!rant
Hey guys I've got little question, sometimes it is more convenient to me to get the adb Debug informations in a terminal instead of Android Studio, is there any way ONLY show Logs from a certain level? Even after reading the docs I couldn't figure it out 😥😥😥
Top Tags
Weekly Rant
View