debugging. So it's not like we're in Visual Studio and you hit a breakpoint and it pops up and there's the source
debugger. And I asked him about that.
The debug interface really revolutionized a lot of the design tools.
and debugged the spec.
So how do we debug them?
No way to debug an ARM6 if it was buried in SOC.
I'll debug and organize later.
So I need to debug that and figure out why are two people not getting along.
So this is Lovelace debugging one of these error pop-ups here with a crowbar, which is the only way you can debug the analytical engine.
Somebody did debug this for me, though.
It's called "CODE: Debugging the Gender Gap." And it's about the challenge of the absence of women in tech.
I liked writing and debugging programs.
And we have been debugging that problem.
You're debugging things and you're making these marginal gains.
stepping through in the debugger, incredibly tedious that that can be." And he sort of cautioned that, "Simply reading source code without firing it up and watching
it in the debugger can be misleading in the sense that you can go a long way reading source, but you can also get stuck. You can get bored and convince yourself that
然后包括coding的一个debug
I put a tiny bit of debug in.
That's how crude our debug was at the start.
And I did proper integrated debug so that we could debug the processor when it was buried under an SOC.
But we didn't put Thumb and debug on that.
You get reasonably adept at debugging all four, but I had more experience in MIPS, so MIPS stuff would come my way.
It was something about the difference between debugging something and some other word that I didn't understand.
Simple tweaks like to optimize your own debugging flow to really optimize your iteration speed can have a huge difference in the long run in how
And so computers had to be regularly debugged in the early days of computing, which meant removing moths from the lights that they were attracted to.
and then an ability to try to iterate and to debug things when things go wrong, and to try new things.
If instead, you could debug that and try to figure out how to alleviate some of the stress in the family, it made it a happier place for everyone.
So he got to sit down with the machine and debug programs and look at the programs in the manual and say, "I could do better than that."
- Yeah, debugging can be real torture. It can be really, really difficult.
I actually kind of like this kind of a debugger.
You can also ask same question when you're debugging, as well.
Say you're building an Android app and you're debugging this photo sharing flow that's a few clicks away from the home screen.
tools that are first developed and tested and debugged by scientists and engineers and other professional thinkers
Another way to read code that comes up more in debugging two people mentioned.
at an early stage, we can start to debug before we put something into motion, right?
So what this means is an individual user is able to write and debug a program in minutes, not hours
So your colleague says, help me debug this, or what's your opinion on this?
Another reason why you might want interpretability is to be able to debug your system.
And so that really started the ARM ecosystem where people could write a debugger once and interface to a lot of different chips, because it
Tools to do monitoring, tools to make debugging easier, tools to just glue the system together.
But right now, the instrument is being debugged to try to figure out what's going on with the radar.
serial cable to another machine, and you can connect to that other machine and remotely debug the crashed machine.
And that leads to different pressures and different sort of perspective-- like when you give birth and you have to debug a fishing site the same day
Literally you could bring a sleeping bag and sleep on a floor in the closet and use their computers to try to debug your code.
there, and they actually listen to you, and they debug your thoughts.
Vint Cerf: Clearly, I have some work to do to debug the architecture.
- Yeah. I actually do use Grok 4 Heavy for debugging. For like hardcore debugging that the other ones can't solve, I find that it's the best at. And... it's interesting
- Well, about half your day is going to be spent debugging, and most of the time is going to be spent in call stacks that are in pure assembly language because there's no source level
And finally, we did get a catch in the actual stress debugger that I was talking about earlier, where it happened to somebody with a debugger connected. We were able to go through,
But it's, like, tell my debugger the following context relevant information.