Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How often do you need to know what it's doing?


Usually when something doesn't go as quick as you were hoping, profiling is unhelpful and you have to take the python bytecode to bits to find out what the hell it's doing inside.

That happens quite a bit these days for me.


Oh, and this. For sure. Why is everything so slow?!


> Why is everything so slow?!

Urf tell me about it. Does my flipping head in.


I used to play around with 3D graphics in real-time on the 486. I needed to know exactly what was going on to even get 30 fps.

I managed to get one of Michael Abrash's (ID software)loops to run 0.5 clock cycles faster, which I was pretty proud of.


When you are attempting to do a very specific thing. Not going to go into what that might be, unless you're curious, but sometimes you do need to know exactly or as close to exactly how your code is operating.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: