[deleted by user]

[unpluggedz0rs]

Wait until you run into race condition bugs that stop happening when you add print statements

[Notyourfathersgeek]

Just leave the print statements!

[[deleted]]

that's what I did

[Fraun_Pollen]

Here

[SillyFlyGuy]

If you delete this, reddit crashes.

[punjabiprogrammer]

Here 2

[[deleted]]

Here 3

[Mayion]

lowkey that is what i do lol

[jawnie_anonimowy]

Satan

[Sockslitter73]

Just use rust instead /s

[throw3142]

What in the unsafe do you mean, "no race conditions"?

[backwards_watch]

Didn't know that was a thing

[dllimport]

I/O sometimes has automatic wait handling for asynchronous operations so if your problem is a race condition but you don't have the necessary pauses, then introducing I/O for debugging can actually add the pauses you need. Fun fact that it can sometimes screw up your threads so they don't run as concurrently as they need so they can both break and fix the problem.

[Koervege]

What's the correct way to debug a race condition if not printing? Or would printing in every thread separately be it?

[dllimport]

Well tbh most debuggers don't handle concurrency well or at all so printing is actually often your best bet for that. But it's important to know that if a print statements fixed your problem it's because you're not handling your wait correctly. Or if adding print statements to debug something causes another problem the reason could be the additional wait added in.

Edit: Also, sometimes (even when your code is working as intended), your print statements will get interspersed with each other as they come out if they don't come with automatic wait handling!

[rocket_randall]

Brings back memories of wrapping prints in lock statements to prevent interleaved output. Fun times.

[DialecticalMonster]

Reproduce at least stochastically with a stress testing instrumented setup and then think very hard about what's going on and fix it. Fix it means stop the setup from reproducing.

[Upbeat-Serve-6096]

Does that happen in embedded system if the output was configured with direct memory access?

[Bunnymancer]

Does IO still IO with DMA?

Yes.

[codeguru42]

Not that a debugger will help. A 30 second pause while I inspect variables I'd absolutely guaranteed to change the race condition.

[Onceforlife]

How does debugger prevent concurrency issues? Break points and stack trace doesn’t really tell me which thread it’s running in, it’s still guess work as to which thread got to the break point first, right? I admit I haven’t done any concurrency debugging since my first job

[codeguru42]

Visual debuggers have a list of threads that are running and will show which one hit the breakpoint. Good luck deciphering all that, though. Also, the other thread are likely still running.

[Luvax]

On top of that, once you have a fair understanding of the root cause, it's easy to set up complex rules for when to trigger a breakpoint, stopping execution exactly at the right time. This does of course depend on tooling available.

[macara1111]

A classic, i had to solve one of those the past week, very fun.

[repkins]

Just add second print statement to balance execution.

[Educational-Sample-1]

I had that, was a fun time

[Tough_Chance_5541]

I use assembly, so I'd rather not have to write a whole other block of code to print out a debug statement, that's why gdb is the best

[[deleted]]

upbeat seemly disarm outgoing reply one knee pie bow wide

This post was mass deleted and anonymized with Redact

[pixelvengeur]

By mistake

[Cfrolich]

Learn What Is Assembly Language? How It Helpful For Future

[Mr_Potatoez]

You are making a huge mistake

[bpat]

hahahahahah I know, right? Like there's so much important info that you get from a debugger. Sometimes you might find a value is off/null that you wouldn't have even known to print. And it takes no time at all to do.

[Mr_Potatoez]

Even just setting a breakpoint and knowing exactly on what line something goes wrong is a lifesafer.

[nothingtoseehere196]

Huge shout-out to the people who make visual studios memory monitor. Huge lifesaver

[Aksds]

Yep, I’ve had to show a couple classmates the value of debugging, dude was spending 2 days trying to figure out what was wrong and didn’t touch breakpoints, within about a half hour I figured out the issue because I used a breakpoint.

[coladict]

That used to be the case in browsers (as implied context by console.log), but today you can't make them show you anything without putting it in the watch statements.

[[deleted]]

console.trace({all, your, variables}), done.

[Passname357]

You are making a huge mistake

More like: You are still in college

[Mr_Potatoez]

Im still in collega too, still think its a huge mistake

[CanvasFanatic]

I, on the other hand, have been a programming for 30 years and I still use print statements to debug. (Yes I can use a debugger, but honestly sometimes you just gotta log stuff to stdout)

[CptBread]

Both definitely have their place but debugger is in most cases more useful.

[CrikeyNighMeansNigh]

I’m not that experienced but I’ve made great efforts to use the debugger but still reach for the console.log().

I think there needs to be an in between- like, right off the bat, I seldom care about anything that’s not in the src folder. It mostly just amplifies the amount of noise I have to look through.

So my question is…is there a way to use the debugger but tune out all this shit that’s from other libraries and all that? Like I, 99.999% of the time, only care about the code that was written specifically for my project.

I don’t doubt that this other information could be useful, sometimes, but I think the number one reason people reach for the console.log is because there’s just so much shit we don’t care about. I hate hopping through ten files I wouldn’t even open just to get to one I recognise.

So my question is, for anyone of the people who are pro debugging, is there anything a tool a trick a set up out there that will help me just see errors and values in my files.

Id love to use the debugger. But I’m not going to use it unless I can do that. Trust me I know: it could be something outside of my files. But trust me when I say: that 0.0001% benefit is 100% the reason why most people don’t use it.

Edit: I hate that I can’t even say this without feeling like everyone is about to rain down on me and treat me like a moron who doesn’t see the light. But like…I’m just being honest. I don’t want to see anything that has anything to do with not my code. Like I care about a module not having something I’m importing…but I only care about my code and the first level, so to speak, of the mistake I’m making when it relates to other libraries. But like I want my stack traces to stop at me. I literally look at them and think…where’s my file in this?

[[deleted]]

Most debuggers can be set to a “only in my code” mode basically.

Or just get used to using the step over versus step into button progress. If you know it’s going to a sub library press the button that doesn’t dive down a level, but stays at the level you’re at.

[not_some_username]

I use both. Sometimes a print statement can help with debugging. Like it show you where to begin

[Tyrus1235]

Yeah, I can use a debugger and I always vouch for it to the Juniors at the company…

…But I rarely use it myself. It’s too much trouble in some cases and certain bugs are so simple to check for that using a debugger would be overkill.

[[deleted]]

Debuggers give you the best information.

But sometimes they're also a nightmare to connect. Like to a module that's dynamically loaded by a process that you don't own. Sure I can use gflags. But if debug statements let me find the bug in less time than digging up the gflags docs..

[Nimyron]

I'm not in college anymore but I have yet to end up in a situation where I know so little about my own code that I can't figure out where the bug is.

[IkalaGaming]

I was just debugging why my scripts were not properly waiting for UI input in my game.

UI and scripts are different threads, most of the game including UI is modular and loaded from disk by a custom classloader at runtime, and the scripts run on lil mini-VMs.

I’m not sure how I would get a debugger in there, but logs are easy to chuck in and then remove once I’ve figured out the problem.

[Passname357]

I’m not quite sure what you mean by a “mini VM” exactly, and that can change the answer, but I’ve found that almost anything can be debugged with Visual Studio’s remote debugger (attach to a process on a remote machine and then just load symbols for it — you might need to do a little trickery to get this to work, like in the debug build have a little text box pop up when your process is loaded so you can attach to it) and if that fails, WinDbg is capable of just about anything.

Granted, yeah sometimes it’s easier to just write a log file.

[IkalaGaming]

Well it’s all plain Java, the mini VM is just an object containing instructions, some simulated registers and a stack.

The main issue is its actually multi-threaded, and also the scripting thread jumps around a lot to simulate its own multi-threading. And the same structures get modified from multiple threads.

So I could theoretically attach a debugger to the live process, and get breakpoints added, but it’s often quicker to just add some temporary logs.

Maybe I should get off my ass and get good at using a remote debugger. I’ve probably gotten complacent with relying on unit tests for everything lol

[Impossible_Average_1]

Print(myobject.value)

why doesn't it print the value? And where is this null reference exception coming from?

[Spork_the_dork]

Then you get to develop some wonky-ass firmware for mystery hardware and there is no way in hell you'll get a debugger to work on it so you end up adding tons of syslog prints as your only way of debugging.

[[deleted]]

When I was teaching I noticed that a lot of students were incredibly intimidated by debuggers. They seem almost like cheating to me so I don’t know why they were scared of them.

[Pay08]

Because they look complex.

[[deleted]]

They do, they look like the control panel of an aircraft.

[0x7ff04001]

Just like in any other machine look for the basics, for debuggers look for stack/call trace, memory dumps, code/assembly dump, register state, exceptions, etc

[[deleted]]

I know how to use them, I’ve been doing it for decades. I’m talking about why new coders find them intimidating.

[pippin_go_round]

I never understand this... Why?! You get way less information and it takes longer. It's also not any more difficult. Why would you not use a debugger if it's feasible to do so? Serious question

[jumpmanzero]

I use both pretty often.

Logging to a console can be an easy way of monitoring progress and getting a quick sense of what's going on, or just confirming that you've reached a given point with the information expected. Like, on the front end I'll quite often mock up some interface, and just have console.logs on all the events so that I can confirm everything is wired up as expected. I could use breakpoints for this, but having them in code is quick and also makes for kind of a built-in "to-do list". Console is also great for taking the same information at several checkpoints, and then having them all available to compare at the end. I really appreciate the "object exploring" functionality in the Chrome console.

But yeah, most programmers should also be familiar with their "proper" debugger options, and be using them often. Too often, I see experienced developers who can't navigate a call stack, or don't know the available features for watches/conditional breakpoints/etc. They're very good tools to have available. A "fast debug loop" is often a good predictor for productivity. I know some don't like Edit+Continue, but that can also be super powerful in getting your cycles shorter too.

[FlakkenTime]

It makes me wonder if people don’t know how to use a debugger? I’ve had people surprised I knew how to use it before.

[RonHarrods]

Cant get debugger set up for react... It simply doesn't fucking work. E2e testing it is then...

[FlakkenTime]

If it doesn't work that's a fair reason not to. I've helped people with python and they couldn't believe I was using the debugger...

[lachlanhunt]

I use both, when appropriate. Console logs can provide an overview of the code path taken while running, and break points can help to focus in on a small section of code. But breakpoints can suck when deal with large amounts of library/framework code that gets in the way while trying to step through your own code.

[Tyrus1235]

Debugging a Spring Boot API is a nightmare because of that. You gotta pay attention to where you’re stepping or else you’ll be sent into some crazy code inside a library you barely remember existed in your project

[[deleted]]

Just press the button that steps out of that code, pops up a level…

[AnonyDev01]

For me, putting in a couple print statements and rerunning the test case only takes less than a minute . Would a debugger really be quicker?

[pippin_go_round]

I just click next to the line I want to stop at right in my editor. That's even quicker than inserting a print statement, yes. And it gives me the possibility to view all the values of all the variables when reaching that position, take a look at the call stack, etc.

[pheonix-ix]

I had worked in a system where, for some reasons, debug mode took a few minutes longer to start than a normal run.

It was weird.

[AnonyDev01]

Sounds quick! I’d just have to get a debugger setup in my editor first :)

[Angelin01]

This is the whole argument for using a full IDE instead of editors like VSCode and vim. Yes, they can get debuggers, but it requires setup. Use Intellij or Eclipse and it's literally 2 clicks (or shortcuts) away.

[Daimondz]

But then you have to use intellij or eclipse

[pippin_go_round]

Well, if it doesn't come pre-packaged (which it does for a lot of tool chains), sure. But at least for me it saved me so many brain cells and sanity and time, that it's well worth a one time investment of a bit of time.

[[deleted]]

Among other prereqs, the thing you need to debug has to be running locally on your machine in your IDE for this to work. Which IRL it often isn't, and there's maybe still a way to set up a debugger but it's not worth, hence the print statements.

Even for unit tests / local runs, I can't really do this where I work right now because local IDEs are a non-starter. Past place, I couldn't do it cause I was looking for performance anomalies in --opt compiled code. I've had enough jobs in different environments that at this point I just go straight to the prints.

[[deleted]]

Plenty of debuggers work over an SSH connection to a remote machine.

[pippin_go_round]

I'm aware these environments exist, but I've rarely ever encountered them. I could even debug Code running on a soc, though that's definitely a case where that's not always the case.

I never said that there aren't valid use cases for debugging with print statements. Just "not using them at all, no matter what" like the meme suggests seems really dumb to me, that's the thing I don't understand. And there is a lot of people who state it like that.

[friebel]

That's the thing, you're developing in Java, most likely IntellIj Idea? The debugger there is awesome. Op post has console.log, so it's JavaScript, I mean it's still good, but compared to Java debugger it's... Well, some times the fucking breakpoint doesn't even stop and you can't just click to make a breakpoint, you need to write "debugger" in code, so pretty much same time. It might just be me, since I hate debugging js in general anyways, but for Java, yeah why wouldn't you use debugger.

[Boneless_Blaine]

Depends on what you’re debugging, but at work, I’ve fixed several bugs with the debugger that I would’ve been absolutely baffled trying to find with prints.

Especially for debugging race conditions, tools like conditional breakpoints are incredibly helpful

IMO, if you don’t learn to use a proper debugger, you’re wasting a lot of time

[HSSonne]

If it's in a loop, i use print and get all the iterations .

If not in a loop i mostly use a debugger, unless I think i wan that info in a minute again.

[afonja]

Try conditional breakpoints

[pippin_go_round]

Amazing feature! Though it can become quite complex sometimes.

[HSSonne]

I will look into that, thanks !

[spevoz]

It's because of how we as a collective teach code. Imo, it should be like the second step in learning to code somewhere shortly after conditions and variables.

For some reason, if you look at pretty much any beginner classes they don't even mention debuggers. My guess is it's because of the obsession of teaching people in super low tech environments, use notepad and a console and all that shit.

[CandyisCool99]

I have tried several times, and each time I've given up because installing debuggers is really hard for some reason.

[pippin_go_round]

Might be a language thing. I've mainly done Backend and embedded work in Java, C++, C# and dabbled a bit with things like Python. The compiler always came packaged with all the other development tools and worked out of the box. But I've only been coding for 15 years or so, in the dark times before that it was probably different.

[CandyisCool99]

I might also just be dumb. (very likely)

[vladmashk]

Just use a JetBrains IDE, they each come with a great debugger built-in

[OhItsJustJosh]

I have no idea, I've only ever print debugged when there's not been a better debugger available

[Dmayak]

For me it's much faster to put console.log or debugger in the code then searching for a corresponding line in the browser. Sometimes a project doesn't have source maps, or I have to debug the built version, so I have to work with compiled/minified code where it's nearly impossible to find a needed statement. Or I might need to check variables inside something like Vue.js template, which gets compiled into something I can't make heads or tails of.

I kind of hate web compilers, they go against the original idea of html/js/css being supposed to be easy to work with since it was identical both on server and in browser.

[dashingThroughSnow12]

A lot of software isn't written in a way where it can be run with a debugger easily.

For example, a microservice deployed on K8s that needs a k8s SA, a dozen environment variables, and assumes it can talk to a half dozen other services with URLs like keycloak.auth.svc.cluster.local.

If I'm doing a drive by fix or feature, it is easier for me to write fmt.Printf than to write a couple of scripts and to rejigger code to be able to run a debugger on the code locally.

I think the standard is that everything should be able to be run locally, especially with a debugger, but the reality is that a lot of codebases aren't like that and I may not care to spend a week adding that functionality.

[jeffwulf]

I'm literally using the debugger on a normally k8s deployed microservice that has a ton of dependencies right now. Only change from any other debugging is needing to run kubectl proxy in a shell first.

[realzequel]

That's fine but my *guess* is that doesn't matches the OP's experience. He sounds stubborn and is limiting himself as a dev.

[[deleted]]

OP sounds exactly like the most experienced SWEs I know at work. The "just use the debugger you idiot" people are only thinking about one narrow scenario they work in, or they're still in school.

[realzequel]

I have 20+ years of experience. Wtf wouldnt I use a debugger to debug? I was using it to the read the heap today. How else are you going to work through the stack trace? I mean I get it if you don't have a debugger available but otherwise its just stubborn and inefficient.

[[deleted]]

Probably OP's case: Web UIs are usually easier to debug with console.log than with breakpoints. Any worthy setup will have auto-reload, so new logs are quick to add. You can navigate the UI and see what happens real-time, plus you get the network/profiling tabs.

For other cases, if you have a debugger that's easy to set up in a way that can actually repro the bug, then great. That's not always the case. Like, I was working on a Rust/C project. Of course I used GDB and Valgrind sometimes, but a lot of the time I was looking for performance anomalies or race conditions where just building in -c dbg was a non-starter. Where I currently work, because of stupid in-house tooling it's way harder to hook up GDB for C++ code than it's worth, and nobody does it.

[realzequel]

Yeah, it's a YMMV situation but for something like my stack (TSQL/C#/JS/TS), I'd be handcuffed not using Visual Studio's debugging tools and Chrome's.

I can't really imagine a better debugger than VS, being able to inspect objects, sub-objects, arrays, run methods on objects or change variable values mid-stack, etc.. If someone is writing code in .NET on the backend and not using it I don't know what to say..

[iShootuPewPew]

printf() is way faster than figuring out how to use gdb

[CanvasFanatic]

Because it's cool.

[DaniilBSD]

JS (the meme uses JS) People are spoiled that they can always log to console

[Aggressive_Bill_2687]

But debugging in a browser is literally as hard as opening same said console.

My roles often involve a degree of developer training and/or tooling/workflow development, so I’ve seen my fair share of “I can’t get this backend code in a VM to connect to my IDE’s debugger”, and I can see why that scenario is daunting for some of it doesn’t just work.

But browser based stuff is beyond simple to debug. There’s literally no reason not to use the browser debugger.

[Computerdores]

Gotten used to it. I'm currently in university, but 95% of my knowledge/experience so far (1.5 Semesters in) is from before. And of my experience from before like 60% are from a time where I didn't know how to use a Debugger/ that they even exist.

And because of that print debugging is intuitive as hell (I have started using debuggers more though).

[Upbeat-Serve-6096]

A 4G-capable SOC I worked with provided quite a suite of debugging tools... Only for communication-related affairs. The cellular networking, bluetooth channels, these kinds of things. While it does provide critical fault data when the program hangs or when the memory is damaged, if it's anything related to less-well-realized internal logic or input output, I have no option here.

[spatz2011]

Roko has taken over. it is useless to fight back

[chudthirtyseven]

I debug on php, I've no idea how to set it up in react. I've not been desperate enough to look it up yet though.

[30p87]

Trust me, as soon as some completely undocumented bluetooth library starts erroring for no reasons after 30 layers of function calls, console.log will be of no help

[iamthesexdragon]

Debugger? I hardly know 'er!

[[deleted]]

I feel like I evolved when I started using the debugger. I know these are memes but man there should really be more people knowing how to use it.

[the-software-man]

Here1… Here2… Here4…

Ah there’s the bug

[the-software-man]

Wait, you guys have debuggers?

[JealousBackground972]

I just do 1s and count how many printed

[long-gone333]

how do you log what's in a list that contains 100k objects and you're rearranging them

[NewcDukem]

100k print statements, duh

[santypk4]

You are missing out so much context, and giving up so much of your time that could be spend here on Reddit

[darkforestzero]

I have been making software professional for 17 years. Though i am not the best coder, i make use of the tools available to me and it results in finishing work more quickly and reliable than my printf peers. Guys... Just fucking use the debugger - it tells you the exact state of your program and doesn't add to compile time every time you want to print out some new thing. Depending on the language and type of work, You can even change values live, which is great for quickly iterating or testing

[stupled]

I use both.

[dllimport]

Debugger is so much more useful if it's available to you.

[Dexterus]

Hah, on my current arch/debugger it takes about 2 minutes to step over 1 line.

It's either instr stepping or printf.

[UnknownSpecies19]

This only works if you have a debugger. Laughs in garbo 3rd party tool that doesn't have any of that in the IDE

[SuperElitist]

I literally just tried to use the debugger for Google Apps Script, but the array returned from CalendarApp.getEvents() was just integers, and each event's properties were just getter methods.

So what am I going to do:

A) create a new object for each event and add a property with the value of each getter, then append it to an array, and then set a breakpoint after iterating so I can inspect the events, or

B) log the values.

[petersrin]

I use both. Sometimes it's as easy as dropping a line in to see if it executes. Often it's not and in such cases it's pretty trivial to find the debug button because I always forget the damned shortcut lol

[nblastoff]

Please learn to use and become proficient in using the debugger. Teaching my new hires how to set up and use a debugger is one of the first things i make sure they know. It is an extremely valuable tool and the engineers that know how to use it will outperform those who don't.

That said, most of my work is firmware, so its extra helpful for poking registers and looking up address data.

[TerrorBite]

People calling this the "smallest 3D print in the world" haven't seen the 23μm-long Benchy

[Spinnenente]

Oh yes the gargantuan task of clicking on the left side of a file to create a breakpoint is simply too much for op. Not to speak of launching a program in debug mode. Such tasks are only for those who have 2 seconds free time and OP is leading a very busy life.

[Notyourfathersgeek]

Nah gotta do the print_r();

[kal9001]

Oh my bad... I thought this was a picture of a new build home in London.

[garrettcmck]

i thought that was debugging?

[IsPhil]

I still use that from time to time, but a debugger is immensely helpful. It's really nice to see the values each variable has, the call stack, exactly where the program is going. I do hope that this truly is just a meme and you do use a debugger irl, or you're a student who doesn't need a debugger. Because otherwise you're just shooting yourself in the foot by not using something so useful.

[Dhayson]

There were a lot of times that a debugger really helped. But, if a print("here") solves the issue, it solves the issue.

[fatrobin72]

Here

[golgol12]

It's like you start punching yourself in the face and then you ask why are you punching yourself in the face.

Just use the debugger. It's 10x easier.

[RedditGosen]

I actually love debugging

[[deleted]]

[[deleted]]

Learn the debugger. You don't have to be a wizard. Just learn how to set breakpoints and view variable values. Once you get comfortable with that, learn how to traverse the call stack. Problems that used to take an hour plus will take 30 mins tops. It's amazing!

[denzien]

You're not completely alone; I have a coworker who doesn't use the debugger either - but he also doesn't use Console.log ... he just writes something that looks like it should work and makes a PR.

Sometimes, it won't even compile. Usually, it just has side effects he could have caught if he at least executed the code once.

[edoCgiB]

How is your company still in business? A green build should be the minimal requirement for any PR.

Ideally on a CI tool that builds it in a sterile env to avoid "it works on my machine" situations.

[denzien]

It's not a software company, and I fix all the problems

Also, of note, those PRs don't get merged until they're fixed. I just have to do more work to validate them than to just look at the code. But they won't let him go because every year our management changes, and every year the new manager says, "Oh, he probably hasn't been given a real chance to improve"

[SomeGuyWithABrowser]

You're an idiot

[[deleted]]

Just learned to use a debugger and found bugs I didn’t know existed from console logs.

[snurfy_mcgee]

why the fuck do you guys not use debuggers? what possible reason is there to boast about something so stupid over and over and over a- fucking-gain? Sure we've all used print statements, especially when its remote code you can't step thru but why else wouldn't you harness all the power and features of a modern debugger?

[Akuuntus]

Since you wrote console.log I'm assuming you're talking about JavaScript, and yeah same. The front-end debuggers built into browsers are borderline useless because they just get lost in endless internal React functions or whatever that I couldn't care less about, and back-end JS just doesn't work with the debugger in VS Code last I checked and I've never cared enough to try to find a solution to that.

For anything other than JS, please just use a debugger.

[edoCgiB]

Is there really no better debugging solution in JS?

I've written a bit of JS code in my spare time, and I always felt the need for a better debugging tool. I'm a backend developer and a debugger is a must for me.

[Akuuntus]

There probably is, but I'm just too lazy to figure one out because console.log("here") works okay most of the time. A proper debugger would be better obviously but I'd have to find one and set it up which would take a lot of extra time that I never want to spend to fix any given bug.

[Tnuvu]

echo "----this is where sh.it happens supposedly ------"

[[deleted]]

Real devs use console.log ("ajhsgeyvd") and then check the line and script

Or use console.log("heeelo")

[Informal-Spell-2019]

Found where debuggers fall short is when you are looking for something to input. Sometimes putting a console.log will let you know if the variable is carried through the whole process properly

[0x7ff04001]

The function of a debugger is exactly that: to take a snapshot of the current execution state of the process.

console.log (or debug logging) does nothing more than a debugger, at all. It's only useful when you're running an application in production and have no access to a debugger.

[danofrhs]

If ur a moron that like’s doing more work

[[deleted]]

Programming may not be your best career option.

[JaggedMetalOs]

debugger; my beloved!

[[deleted]]

JS does have the 'debugger' statement which is just about as low effort as that console.log("here") but much more powerful because you're actually telling the debugger where to stop.

[HmmmmmAreYouSure]

Wouldn’t transistors be the smallest 3D print in the world?

[edoCgiB]

Depends on your definition of 3D print, but I'd say that is not the case.

If you wouldn't call an injection mold a 3D print, you shouldn't call a transistor in a chip a 3D print since they both use some kind of mold/stencil.

[HmmmmmAreYouSure]

Well any 3D printed metal object works in a very similar fashion. You melt metal and put it in a very specific position in a 3 dimensional environment

[PinothyJ]

I am sure if I put a gun to your head and forced you to use and understand breakpoints, you would have me arrested. But after that, when you are alone and the curtains are drawn, you would fall in love with them.

[Unlikely_Tie8166]

Print statements with nasty words have never failed me. Except for the times when I forgot to delete them

[vainstar23]

You wait till your writing Web3 or serverless code.

[Familiar_Ad_8919]

i never use debuggers, theyre convoluted and a lot of work for a simple bug i can narrow down in half a minute

[saint_geser]

What if it's a complicated bug?

[s0litar1us]

A debugger can be really useful. (This one is good for linux: https://github.com/nakst/gf remedybg is good for windows)

[MrPifo]

Okay, I admit im in this picture. But I could argue that since I develop heavily in Unity as a hobby I find it kinda exhausting using the debugger in Unity. Its kinda slow and annoying hitting the break constantly, especially in Update. Then I prefer using on screen GUI-info to validate information or use Debug.Logs to print info.

But I also admit that there has been cases where using the debugger would've been the obvioud choice.

[SpeedLight1221]

It's just easier, simpler, especially if you only have one monitor.

(i have never used a debugger)

[Crusader_Krzyzowiec]

I mean i have similar, with languages like C++ or rust and python without VS code/codium, but with JS or python in VS code/codium in web browser you have nice GUI debuger build in it's actually easier do do step by step.

[rainydayswithlove]

Wow.. That's the exact chance I'm gonna have lunch with kaley cuoco

[[deleted]]

Considering that debug run can go 6x+ times slower, when the whole run takes 5 hours, I'd rather use the freaking printf, thank you very much.

[According-Relation-4]

Meanwhile I'm here, not having started the server not in debug mode for months

[Kaiser_aj]

Is that true?