Some motherboards have a tiny piezoelectric speaker soldered on, which replaced the larger speakers that used to be used. It’s becoming less and less common though.
I hate it with a passion. The manual doesn’t list that the CPU led and MEM led are lit when the +5V rail is too low from too much load on it from the USB devices.
though thinking about it I should probably figure out WHY that’s a problem
Yeah the LEDs can be confusing. I like the fancy systems that have an eight-segment LED display (those basic ones that can show numbers and some letters) that show an error code. My work PC (a Lenovo ThinkStation) has the error code display on the front of the PC so you don’t even have to open it to determine the issue.
Now I’m wondering if my board supports one. I think it’d be cool if my big fancy custom cooling loop gaming build sounded like it’s from the early 90s.
Most boards still do. I have a couple x570 boards lying around that do, and my friend just got an x670e board that has one. They all have the setting in the BIOS for the POST beep as well, and you can set it up in your OS to beep at a specific frequency/duration for notifications.
Dude, literally me. Whenever my friends or my brother’s friend come to my room, I opened up a few terminals with only one of them is actually for coding and they thoight I could hack someone’s Facebook account or something LMAO.
Watch a Video or read something because it really is an invaluable tool. But here’s a crash course:
Debuggers, or IDEs, let you step through your code in slo-mo so you can see what is happening.
Set a breakpoint - Click to the left of a line of code so a red dot appears. Run your program, and the IDE will execute to that line, then pause.
Look at variables’ values - While the execution is paused you can hover over variables before that line to see their value.
Step through the code - See what happens next in slo-mo.
Use “Step Into” to enter into a function and see what that code does.
Use “Step Over” to not go into a function and continue in the current spot after the function has done its business.
Use “Step Out” to exit a function and pick up the execution after it has run. Use this when you’re in too deep and the code stops making sense.
See whats in the heap - The heap will list all the functions that you’re currently inside of. You can jump to any of those points by clicking them.
Set a watch - Keep a variable in the watch so you can see what its value is at all times.
Set a condition on the breakpoint - If the breakpoint is inside a big loop, you can right-click on the red dot to create a conditional breakpoint, so you write something like x===3 and it will only pause when x is 3.
There are many other things an IDE can do to help you, so def look into it more if you want to save yourself a lot of insanity. But this is a good starting point.
If you’re developing for the web use F12 to open web tools, and when an error happens, click the file/line number to see that point in the Sources tab, and you can debug there.
Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.
Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.
Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days
I have used them occasionally. It’s sometimes easier to use logging because you can dump an enormous amount of information and quickly then look through it if you already know what kind of information you want to look at. Debuggers are better when you have no idea what the hell is going wrong and need to get a little bit of info from everything instead of a lot of info from one thing.
I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
this is gold lmao
Ok, so, I thought I was crazy when I said “debug it” and my coworkers were like “you can read that shit?”
My colleague literally once said to me “i can’t read bleep bloops”
Heck I remember when you had to read “bleep bloops”. POST codes came in beeps, and that’s how you knew why the computer wouldn’t start.
Sometimes I miss em, wish it gave those in addition to the modern indicators. Then I could just tell without even looking.
Do modern PCs even support IBM-style speakers any more?
Some motherboards have a tiny piezoelectric speaker soldered on, which replaced the larger speakers that used to be used. It’s becoming less and less common though.
My current mobo has LED post codes.
I hate it with a passion. The manual doesn’t list that the CPU led and MEM led are lit when the +5V rail is too low from too much load on it from the USB devices.
though thinking about it I should probably figure out WHY that’s a problem
Yeah the LEDs can be confusing. I like the fancy systems that have an eight-segment LED display (those basic ones that can show numbers and some letters) that show an error code. My work PC (a Lenovo ThinkStation) has the error code display on the front of the PC so you don’t even have to open it to determine the issue.
Yes. My latest mobo has the pins for a POST speaker, but didn’t actually come with one. Installed it though and it works.
I didn’t even bother checking on the last box I built. I know I’ve got at least one proper speaker and one piezo in a crate somewhere.
Now I’m wondering if my board supports one. I think it’d be cool if my big fancy custom cooling loop gaming build sounded like it’s from the early 90s.
Most boards still do. I have a couple x570 boards lying around that do, and my friend just got an x670e board that has one. They all have the setting in the BIOS for the POST beep as well, and you can set it up in your OS to beep at a specific frequency/duration for notifications.
My b350 board supported that style of speaker. Newer machines apparently use the start button led in some cases.
You really just threw “generic Chinese name” into some translator didn’t you lol
Good my colleagues think I am Hackerman that can hack through time!
Dude, literally me. Whenever my friends or my brother’s friend come to my room, I opened up a few terminals with only one of them is actually for coding and they thoight I could hack someone’s Facebook account or something LMAO.
Yes I live in Southeast Asia
Kung Fury will never not be amazing
That image goes so incredibly hard
Father, I want to see the face of VBA god
He’s the only man I know, the only man I want to be.
Lesson learned: aim for the manager spot to order those folks around
I’ve been coding for a long time, and I think I’ve worked with all these archetypes. Too real.
“Can reveal the face of God using VBA”
This one got me good. I became a VBA king being in one of those locked down environments.
I love this!
How do you code a house I can love i
OMG, of all the memes I read all day long, this had to be the one to actually make laugh hard.
I am Samir
Thanks for unlocking my account everytime I forget my password!
But does anybody ever thank me for never forgetting my password? Noooooo. Grumble grumble.
We’ll shit imma be out of a jerb with this competition.
Ten years into casual programming and I still don’t know how to use a debugger.
It can be useful sometimes. Same for print. And logfiles.
It’s easy, you just step, step, step, step in, or wait, over, or, oops.
Watch a Video or read something because it really is an invaluable tool. But here’s a crash course:
Debuggers, or IDEs, let you step through your code in slo-mo so you can see what is happening.
There are many other things an IDE can do to help you, so def look into it more if you want to save yourself a lot of insanity. But this is a good starting point.
If you’re developing for the web use F12 to open web tools, and when an error happens, click the file/line number to see that point in the Sources tab, and you can debug there.
That sounds really cool
Thank you for writing this out
The only real time I use a debugger is to tell me what line a default occured at.
I believe in a conspiracy theory that nobody uses debuggers.
console.logcounts as “a debugger”, right?Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.
Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.
It does for me!
Does this include C programmers? I’ve definitely found GDB to be indispensable in the past (or maybe that’s what they would want you to think).
After decades of print debugging I finally got dap up and running in vim. It is very nice. Would recommend.
I use them daily. It makes it so much easier to work with an existing code base
Yep. Once you get the hang of it, you will cringe to think of all the wasted effort that came before. But getting the hang of it takes dedication.
Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days
I have used them occasionally. It’s sometimes easier to use logging because you can dump an enormous amount of information and quickly then look through it if you already know what kind of information you want to look at. Debuggers are better when you have no idea what the hell is going wrong and need to get a little bit of info from everything instead of a lot of info from one thing.
I work with 20 year old legacy spaghetti code, the debugger has become one of my most treasured tools.
I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.
Grep log will outlive us all
I can record a video tomorrow if it helps?
XHTML 1.1 is much more elegant than HTML 2