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
-
Me: Sometimes I talk to myself while debugging.
Me: OMG 😱, me too..
Me: Lets try pair programming next time.9 -
When my colleague asks for help when debugging, I like to start of with setting a few breakpoints.
5 -
Who needs rubber duck debugging when you can do paper duck debugging?
Or is that concept too... Farfetch’d? 😎
13 -
My roommate was sleep talking last night. She said: "It doesn't work!"
I wonder if she was debugging in her sleep...4 -
We're not a family of devs. So the situation may seem weird to them.
My sister saw me doing the rubber duck debugging and venting my programming frustration with an innocent little duck. Eye-to-eye. And now, she thinks i'm in need of serious help.11 -
*Stages of debugging*
1. That can't happen.
2. That doesn't happen on my machine
3. That shouldn't happen.
4. Why does that happen?
5. Oh, I see.
6. How did that ever work?3 -
Six stages of debugging:
1. That can't happen?
2. That doesn't happen on my machine?
3. That shouldn't happen?
4. Why does that happen?
5. OH, I SEE!
6. How did that ever work?1 -
When you escape outside from everybody, and the nature gives you its best debugging buddy!
Sorry for the quality, it was dark and that's the best I could do with it.
It scared the shit out of me at first :D
6 -
Motherfucker.
After about six hours of debugging I finally figured out that the error I'm getting is happening CLIENT SIDE AND NOT FUCKING SERVER SIDE. Yes, I've been debugging everything on the SERVER SIDE.
MOTHERFUCKING FUCK.FML.9 -
The six stages of debugging:
* That can’t happen.
* That doesn’t happen on my machine.
* That shouldn’t happen.
* Why does that happen?
* Oh, I see.
* How did that ever work? -
Inspired by some other devrantter. I finally got myself a debugging buddy. It's been a month since I bought it and I can't wait to see it growing even bigger!
12 -
I feel that people are quick to blame PHP for a lot of things. But come on, you have to admit it has the most straightforward debugging workflow:
Take a ritual knife out of your desk drawer
Sacrifice some blood to the PHP gods
Clean the knife -
Manager: I’m getting a strange error now….it says CORS? Any idea what that means?
Dev: Ezpz, just a matter of how many goats to sacrifice and incantations to recite
Manager: Are you serio—
Dev: Bring me my debugging pentagram7 -
!rant
My gf loves rubber ducks so much, I'm just waiting for her to learn coding just for the debugging process :D
6 -
Rubber duck debugging - Batman style!
Gonna be necessary today I guess, but always keep in mind when you feel desperate while debugging: The night is darkest just before the dawn!
6 -
The most difficult thing about debugging isn't fixing the bug, it's all about finding the bug. -Mr Robot6
-
The problem with working on a debugger for a living is that you can end up debugging a debugger debugging a debugger that is remotely debugging a debugger which is debugging a program...
...only to find out there's a bug in the first debugger and you need to debug it.
4 -
The long awaited DevDucks arrived! New partners in debugging :D
++ to devRant, those capes are really neat.
10 -
Nature gave me a real life 🦆 debugging friend. He wasn't really helpful though. He flew away shortly after. Probably got a call from a more desperate dev.
3 -
Just found a great talk on JS: "Essential JavaScript Debugging Tools", thought other people, especially the ones currently just learning it, might enjoy it.
The whole channel is a sub recommendation anyway, as they always publish great talks and videos for webdev and more.
https://youtube.com/watch/...
5 -
When I started programming Batch Files I decided to go big and and make an Batch Program with a fully functional UI system. Just when I had finished the first menu I kept getting a "goto was unexpected at this time" or something like that. I did everything I could to see about debugging until I finally cleared my calender and spent the next week debugging. A week of debugging goes by and I see someone coding in color rather then black and white at my school. I walk up to him and ask. "What language is that?" To which he replies "Batch". I asked him how he got Notepad to be in color and he simply pointed to the top left of the screen and it said Notepad++.
I get home later that day and look up "Notepad++" and download the first thing I see. I install the .msi file and I see a language bar at the top of the screen. Set it to batch, and drag my .bat file into the program to see six of my dividers are red bars. I look this up and see there's another spacing option "echo.", I replace my current spacers with this and the whole thing starts working. Fml, that's a week I'm never gonna get back3 -
If YouTube thinks that it's going to coerce me into getting a YouTube Red subscription by inserting a commercial in the middle of a video, it doesn't know very much about me!
I have developed a very useful skill after debugging code day after day. It's called, "patience".9 -
When debugging and testing programs with huge databases, i acidentally start breaking Records in this company.
Had my biggest curl command with 5000 UUIDs (which just made my terminal crash, never happened before), my longest curl request (over an hour) and now Github ... what were your most ridiculous proportions in coding?
7 -
So my co-worker loves to tell us to comment our code, for obvious reasons.
But now I'm debugging his code, and guess what.
No comments.
Okay, maybe two comments in two different queries, but they were not that helpfull.
So now I have to debug his code, and I have no idea what I'm even supposed to look for!10 -
My lecturer went out and bought us all rubber ducks to encourage our "rubber duck debugging". Honestly the highlight of my semester.
3 -
Debugging a system error with a good team of fellow developers/devops people is fun.
We had an issue on Friday where we were getting a pretty cryptic error in our error reporting system. A couple of developers and I got together with a couple of devops people and we worked it out well as a team and figured out a pretty complex issue in a reasonable amount of time with everyone playing a solid role.
Nobody tried to steal the show and everyone listened to each other's ideas on what the problem might be. Through and through a great debugging session and made me think about bad ones and good ones I've had in the past.4 -
My day in one sentence: I found about 20 ways in which my code doesn't work as expected.
I hate these days, where you spend 80% of the time debugging and always find tiny new bugs.5 -
I'm so scared of the people on stackoverflow that my method for debugging a problem is to write up a question by which time I'm shocked into finding a solution. I'm just too scared of being ridiculed by some narcissistic dev (who obviously never makes any mistakes, ever) or, heaven forbid, having my question down voted and closed.5
-
I hate it when my manager lurks around when i am debugging and keeps giving random unsolicited advices. I spend more time explaining him why what he is saying does not make any sense than debugging.3
-
My mentor at my current internship helped me improve my debugging skills. He's a great dev and has really good debugging skills. He showed me his ways of approaching things and how I should go about solving difficult problems.
I think he never directly helped me when I got stuck. I ask him like 'I have this confusing problem, can you help me out?' and he's like 'well yes, but actually no" and he almost always tells me that I can figure it out myself. And I do figure it out, eventually.
Now, I seldom feel the need to go to him. I guess that's a good improvement. :)3 -
Maybe it's an unpopular take, but I don't get why so many people keep whining about debugging. If you hate debugging so much, why would you become a programmer in the first place? Wouldn't you be miserable most of your working time?9
-
“Debugging is actually all about finding the bug. About understanding why the bug was there to begin with. About knowing that it’s existence was no accident.”
Mr.robot1 -
Debugging an assertion for hours that keeps failing on 19 == 20 , and you just cannot figure out why it returns 20, until you realize that it in fact returns 19 and the constant in the test case that you screwed up at the start reads 20.7
-
I practice what I call "Aggressive Oriented Programming" or AOP.
Whenever I'm investigating a bad bug, working on a project that I really hate, or dealing with messy code written by a messy developer, I often find myself resorting to an [internal] state of violence.
It's not like I scream and smash my screen (although sometimes I want to). It usually consists of a few git blames and some curse words in print statements for debugging. This is just my way to vent.
5 -
When you spend 3 hours debugging a site's CSS to see why an area isn't showing up...
...only to load it on another computer and find out that the only issue the whole time was that one of the CSS classes tripped an Adblock filter.2 -
Why are people complaining about debugging?
Oooh it’s so hard.
It’s so boring.
Can someone do this for me?
I honestly enjoy debugging and you should too..
if it’s not your code, you’ll get to understand the code better than the actual author. You’ll notice design improvements and that some of the code is not even needed. YOU LEARN!
If it’s your own code (I especially enjoy debugging my own code): it forces you to look at the problem from a different perspective. It makes you aware of potential other bugs your current solution might cause. Again, it makes you aware of flaws in the design. YOU LEARN!
And in either case, if it’s a tricky case, you’ll most likely stop debugging at some point, refactor the shit out of some 50-100 line methods and modulize it because the original code was undebuggable (<- made up a new word there) and continue debugging after that.
So many things I know, I know only because I spend days, sometimes even weeks debugging a piece code to find the fucking problem.
My main language is java and i wouldn’t have believed anyone who told me there’s a memory leak in my code. I mean, it’s java, right? We refactored the code and everything worked fine again. But I debugged the old version anyway and found bugs in Java (java 6.xx I believe?) which made me aware of the fact that languages have flaws as well.. GC has its flaws as well. So does docker and any other software..
Stop complaining, get on your ass and debug the shit out of your bugs instead of just writing it in a different way and being glad that it fixed the issue..
My opinion.3 -
College: This is the debugging mode This is a breakpoint. Here you can see the variable values.
Work: print "asfadadadda" and variables and delete lines until it throws a different exception8 -
Just went out from a 12+ hours session of debugging.
After removing bits of code until there was almost nothing left, sweeping through StackOverflow, step-debugging into thousand-lines framework source code, running tests, considering filing a bug to Android...
turns out I had a
getFragmentManager()
that should actually have been
getChildFragmentManager().
2 -
The taxi driver has Rubber Duck setting in front of him looking forward to the traffic... Another level of debugging...
-
I practice stress-debugging.
It means that while I'm debugging and still in the phase where I have lots of ideas about what possibly went wrong (thanks to my loyal diagnostic team of ducks), I intentionally increase my discomfort level, forcing my brain to work faster and solve the issue. I don't drink, eat, or go to the loo no matter how desperately I need to, until the bug is fixed.
My colleagues and managers think I'm insane or a closet masochist but nevertheless, they acknowledge it actually works for me.
How weird is that?1 -
After hours of debugging my js script, I finally found out that all my trouble came from a variable that contained the string “true“ instead of a boolean value. I kinda hate javascript now...6
-
I spent two days of debugging for a typo. Literally two characters were switched.
Took my coworker 3 seconds to find it.1 -
Colleague while reviewing my latest commit.
Him: Hey, RemusWasTaken, why did you leave this debug log in here?
Me: That function won't work unless I leave that line exactly there.
Him: It can't stay, come here so we can fix it.
Three hours of debugging later, this Friday afternoon.
Him: Okay, I give up. Let's leave it there for now.
Me: I did the same thing yesterday. Time well spent.
Nodejs is weird sometimes, or we are incompetent devs.5 -
I built a chrome extension that brings a digital rubber duck to your browser for debugging, companionship and laughs - the perfect companion for a dev. :)
The logo was inspired from Devrant's ducks too, and the project is open source.
You'll find the GitHub repo here - https://github.com/rameshaditya/...
Do give it a star if you like it, that would make my day! :)3 -
Just spent two freaking hours debugging, only to find out that the api address has changed and no one had bothered to tell me. :|1
-
Sometimes, when bugs get a bit out of hand... You have to counter them with better debugging methods 🐥
2 -
I just won this debugging buddy at a children's carnival. I must name him. I'm taking suggestions. The winning suggestion gets ++ on their 20 latest rants.
18 -
fuck sakes
sometimes I feel like debugging is really just next level spell checking
took an hour to find my egg -
Debugging, an art of detecting a crime which you may have done back in time with an urge to puch your own face after discovery.7
-
So I had been debugging this code for the past 2.5 days without much sleep and couldn't figure out why it wouldn't work.. Turns out I was passing the wrong variable to a method -_-
On the bright side, while debugging I was able to optimise the code and now it runs waaay faster 😎
Now, time to go into hibernation 😴1 -
When you're debugging a seemingly stupid bug, which CANNOT be your fault, and you will NEVER learn anything from it.... until you actually solve it, realise that it was so obvious all along, and learn a ton in the process.
-
Debugging is fun again.
@dfox, @trogus
please make Kotlin cape. I wrote 2 emails already and asked about this. please. Even React has separate cape. 😂
-
Few weeks back, late night, busy watching online series and suddenly, junior pings me and asks for doubts related to implementation design and then implementation in nodejs (which I touched long long ago). And, me being attracted towards debugging, and kind heart to help the junior(hihi kind heart), helped to completely resolve the issue by texting and screenshot of logs sent over message.. just to mention. Time was around 2-3 am.. my most effective time period..
-
There are times where I would be debugging during one of my (high school) classes, and I would finally find that bug that I've been looking into for days, and I would then involuntarily yell out something like "Oh! That shouldn't be there!", and everybody would start staring at me. It really pissed off the teachers.1
-
Got a rubber duck for christmas, and it reflects my personality perfectly. Some mean debugging ahead... *mwahahaa*
5 -
I used to have a girlfriend but then I once used her as a duck for rubber duck debugging and now I'm single..! :/2
-
Debugging your JavaScript Code for 2 hours and trying out every imaginable solution because it works on the demo page but not your site... and then you find out the fking library had a bug and the Readme.md contained a cdn link to an old version and the demo page was up to date... arrgghh2
-
I hate debugging document oriented data types..
Can't even sysout easily like primitive data types.
Need a debugging duck.1 -
The worst type of debugging: Programming an MCU without a Serial Monitor.
Some Context: I've spendt today about 3h+ on getting an attiny 45 to read 3 digital values on 3 pins. So for every test I wanted to make, I needed to put the MCU inside a socket put this socket on a arduino and flash it. Then extract it from the socket and put it on a breadboard for testing.
After getting headaches for nothing making any goddamn sense, I ended up noticing that one input pin is a multiplexed reset pin with the reset having top priority and no way to change it. So whenever this pin should have read a low signal, it got held in reset! FML -
I'm I the only one who talks to an imaginary friend when debugging 🌚🌚
In my defense my imaginary friend helps me see things in a different perspective and most times I end up fixing my bugs2 -
So i came up with indoor plant debugging
1. Keep a plant near your code
2. if you are writing a shitty code plant starts dying
☠️
6 -
You know you need to stop debugging and sleep when you start rearranging your comments in the hope that your code will work!
-
I am so f'ing stupid. Half an hour of debugging, only to discover the problem was a simple typo. this feels bad.4
-
If Debugging is the process of removing bugs, the Programming must be the process of putting them in.2
-
Debugging a previously employed intern code for hours (poorly written JavaScript). Found out they were comparing the exact string value of the input boxes. #smh
5 -
Here's my new function:
/**
* Output Debugging information and Die
*
* @return hopefully
*/
public function odd()
{
//stuff here
}
Hopefully, you don't have to ODD too much when you write code... like I have to do right now
fuck sakes1 -
Do you guys often talk out loud when coding/debugging ? I find myself doing that and it has actually helped me find mistake or understand things8
-
Just spent 10 minutes debugging why my game is launching with the console presets and UI only to see that I set my configuration to Console...
Well done...2 -
So I upgraded my project to a new version of unity.
And my character stopped jumping.
And then it started jumping.
And stopped.
And started.
After 2 hours of debugging I found out that the RigidBody2D editor fucks up physics.
WTH2 -
Debugging is fun sometimes.
Especially when said bug fills up RAM, sends a bunch of guff to VRAM, and pins a core at 100%, rendering my computer near unusable in mere seconds.
(I accidentally load the same texture maybe a hundred or so times) -
I remember debugging a large C++ application a while back. I had been doing quite a bit of backtracking when I found myself looking at a line of code commented with "this is the code you are looking for". Scary.1
-
If debugging is the process of removing software bugs, then programming must be the process of putting them in.
-
Spent 4 hours debugging to figure out I needed to hit the enter key smh.
In my defense 3 other software engineers looked at the problem and couldn’t figure it out.
In my offense I only solved this problem by talking to the engineer who made it.1 -
Debugging lesson learnt
The place where you think you can't make a mistake is the place you make a mistake. -
I think rubber duck debugging is too old now. The next big thing is stress ball debugging. Squish your ball(s) till you get the solution to your problems.3
-
"Debugging is anticipated with distaste, performed with reluctance, and bragged about forever."
This is so true. -
!ok
A guy just told me that printing variables to check for errors is better than debugging!
I am done talking to him 😂6 -
Getting back to the cpp applet I started somewhat recently (Vanilla + Gentoo kernel version checker)...
Me: "debugging c plus plus code"
Dictation: "f***ing c++ code"
...
Well, it's not too far off. -
When your code misbehaves in production and you need all the ducks in the world to fix the problem😂😓
(Marshmallow doing some serious debugging!)
1 -
My colleague just said let's buy debugging drugs instead of ducks. I don't know if it's utterly brilliant or insanely stupid.2
-
Debugging is a must have skill for every developer. I used to consider debugging to be a pain. But when I did it for fun it made debugging a bit easier to me.
Take debugging as a challenge and enjoy doing it, it will make your life a lot easier
1 -
What is the longest time any of you have been debugging one problem?
For me it was at my first internship where I was creating a multithreaded qt application. I had a problem that took me two weeks to figure out. I was trying to call a function from a qt thread when it wasn't the main thread. Took me two weeks to figure that out since it was my first time doing multithreaded applications, and the fix was dead simple.
Any similar stories?1 -
"Programming, and especially debugging, sometimes brings out strong emotions. If you are struggling with a difficult bug, you might feel angry, despondent, or embarrassed."
- Allen B. Downey, Think Python1 -
Today, in "Typos that wasted hours of debugging"...
PHP...
>:(
PHP is such a bitch when it comes to unset variables, why didn't it trigger a warning or something when I tried to $typo[$index]?? I may be missing something and my head starts to ache.
Fixed tho', lesson learned.4 -
3 hours debugging for one colon. Welcome to the shadow bugs in Go. This was one of the most satisfying fixes. And a great introduction about shadowbugs.
-
Me: I've spent 2 hours on this problem, this is exhausting, I need to take a break...
*10 seconds into the break*
My Brain: I think I know what the problem is
Me: Onto another 2 hour coding/debugging session!
Who needs breaks anyways1 -
What is the most straightforwardest solution in the entire history of the world..??
My head : Putting prints all over the fucking universe ..
If at all debugging was algorithmic like that.. -
Debugging is not about process, it's about end.
(I just finished two week long debugging session - approx 5 hours a day. It was nasty bug appearing only with optimalizations in embedded C, you can imagine joy when it came to life tonight. So now I am resting at pub with glass of cider knowing I am loosing needed sleep but I simply do not care right now. Sweet careless.)2 -
Programmer friends are good debugging rubber ducks because even if they don't understand you, they'll never admit it
-
While debugging a service on a linux server...
Log-level info: no really useful information and no hint about the bug
Log-level debug: OMFG TAKE THAT 2GB LOG FILE
Why all the time 😧 -
Finished compiling my biggest project to date. It compiles fine, but does not output anything.
Time to spend the night debugging and overeating. -
Every time I see the word "duck" here, I wonder if it's autocorrect...
Stop debugging you motherduckers! -
Spent hours debugging and realise Object should have been object. Thanks documentation and Unity error messages!!1
-
After weeks of working on my esolang interpreter in Rust while learning the language at the same time I'm finally at a point where I'm able to do the first test...
Only to realize IntelliJ Rust doesn't support debugging 😴2 -
If debugging is the process of removing software bugs, then programming must be the process if putting them in
-
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 -
Agree or disagree?
I disagree.... When debugging, I'd like to breakpoint here (inside the DAO class) and see the results.
4 -
Story time!
I spend few hours last Friday debugging piece of code I wrote. It was based on working code, also authored by me. It was stuff for sending some data to transmitter, all in Python, nothing horrible or tough.
I wasn't able to understand, why older piece of code works (e.g. data are transmitted) and newer don't even when function bodies were same (I was desperate, so I copied-pasted my own working function there). Both function were in same file, bot syntactically correct, newer one was definitely running but still no transmigration from there.
And then it came, enlightenment at Friday afternoon. I forgot to actually push my prepared packet to radio. Older one was encapsulated in transmitter function and newer one wasn't. I was so focused on possible error in packet creation I forgot to send it?! Seriously?! Unfortunately yes.
Moral of the story? When debugging something, try step back (or up in my case) for a while. -
I think I'm a good hackhands expert.
If there's something I don't understand, I pause the session, and I do my research.
If a client is learning, I'll pause whenever they have a question, and explain in depth so they get the concept.
But the asshole that I worked with today just didn't understand how debugging works. I try one fucking thing that doesn't immediately work (after I already identified the root of his problem), and, as I PAUSED and start adding debugging for him, he ends the session and leaves first a one star review saying nothing, and then a three star review saying "couldn't fix my problem"
Fuck that guy. -
When after 2 hours of debugging you realize that the reason only GET calls work to your local instance of API and POST calls don't is the fact you have VPN turned off. God damn those externally defined CQRS settings.1
-
Debugging a Velocity template issue the other day where I was presenting a firm to the user to fill in some data. Whenever the user had entered in one or more lines, a 'true' kept showing up cryptically before the form. Drove me fucking nuts because there was nowhere in the template code that was printing before the form input.
Turns out it was the output of a $list.add(...) being rendered to the screen.
Spent 40 mins on that shit.
😐🔫 -
I miss bug hunting... Baking new features is far less fun than debugging all sorts of weird issues across all the layers of the setup. Devops has its charm, but still I find myself looking for problems more often than tinkering with devtools.
I wish there was a "debugger" role in my company.7 -
I need a new rubberduck for debugging problems. Does color or size depend on language and dificulty? Or do i have to look for the stats of the duck itsself?1
-
le me wanted to watch anime after 10 hour work
"Hmm let's just open my work in a new tab"
"Wtf it's 500"
> read logs
> problem with webpack build
> after 3 hour debugging loaders, environment variables, decided to use a shady, less documented library I found in the first minute debugging called better-x instead of x i'm currently using
> works
> fml why don't I try it earlier, 3 hours lost gg -
Nothing better than debugging 7000+ lines of css code when the theme had Grunt setup by default. (Old theme needs update because of client reasons)
Luckily the dev did a good job of adding comments. So I got that going on for me.
Trying to stay more positive this week.4 -
"Debugging is like being a cop in a crime movie where you are also the killer!!!" - William Shake-de-bug-speare
-
Visual Studio is the worst. Ever. I was about a half hour digging into debugging my code, and I was about 8 layers deep into the API, with breakpoints to anchor me to each level. With no warning, Visual Studio crashed and I lost all my breakpoints, and I didn't know which file I left off in. I had to completely restart the debugging process. Visual Studio deserves to burn...4
-
Spent most of the day at work debugging a script which imports client data from their old system into our system. Someone made a change to a for loop which was looping through a period length by days, doing whatever it needed to do for each day. Unfortunately they changed the increment value from 1 day to 86400 days... probably thinking they were dealing with seconds not days. A day well spent.1
-
Tell me what is value of a "," ( comma) in programming?
Because
I spent a whole day debugging errors one after another and atlast the main reason of all errors leads to a fking comma 😑8 -
I was doing some debugging and wanted to print "hello" to know how many times it is run but mistyped it to "hellp", which is quite fitting
-
Dam your shit! When it's working one minute and then fucked up the next 😢
Laravel API project, need to do some serious debugging, whereas my rubber duck 🦆 -
Debugging - being the detective in a crime movie where you may be the murderer, your friend may be the murderer, or you might both be unknowing accomplices for the other
-
Primary debugging tool while working with PHP: print_r();
Primary debugging tool while working with Angular: Developer Console logs
Primary debugging tool while working with Node JS: Node Terminal.
What's yours?3 -
Debugging buddy: stuffed php uniphant
Debugging drink: pipping hot tea
Debugging stick: chocolate bar1 -
In ROBLOX, There is something called a microprofiler that is used for debugging. It is the only option for figuring out the source of lag (buffering). While using the microprofiler, my computer's frame rate drops rapidly, to as low as 20 fps.
1 -
In my experience programming, there's nothing scarier than fixing 29 errors, fixing the 30th error, debugging the script, and seeing you just made 70+ errors by fixing the last 30 errors.
-
Today I finally found the bug that I was debugging the whole infra for last 3 days. Actual culprit was the first guess, which I ignored. But these low of long debugging makes me feel alive again.1
-
"Debugging is similar to being a detective in a murder mystery when you are also the killer and are unsure of whether you are resolving the case or hiding your traces!!".
But seriously, why does debugging have to be so challenging at times? It appears as though the code is attempting to trick us in some way. And let's not even talk about those mysterious error messages that have no meaning at all. Is a bit more explanation necessary, code? Give us a break, please!2 -
What a lovely Sunday morning...debugging a double free on a GTK+ software I'm writing! It will take me ages to find it xD
-
To all React developers out there:
have you ever used the "so famous" Redux Time Machine Debugger capabilities?
Every now and then I see articles praising that as "one of the greatest things in Redux", but I either didn't understand the feature enough to see usage, or my applications are "way too CRUD"(?) to warrant time-traveling debugging.
Please, someone enlighten me :)3
Top Tags
Weekly Rant
View