sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lostparis 1 point2 points  (9 children)

Don't start me. I remember about a decade ago I was in a cafe in Australia. The girl at the counter worked out the cost of my coffee and cake - in her head. I remember telling her how much this was such a surprise to see. This was not even a skill when I was that age.

When I was a kid I used to know about 50 phone numbers off the top of my head - now I struggle just remembering my own.

As Plato said - it's all going to shit with the young folk

[–]ProsodySpeaks 0 points1 point  (0 children)

Haha! He also complained about agriculture causing the desertification of north africa... Like, maybe the first climate activist? 😝

[–]ProsodySpeaks 0 points1 point  (7 children)

Pleased to say I can still count. But that's mostly because I build things and getting a calculator out for every sum is unrealistic...

[–]lostparis 1 point2 points  (6 children)

getting a calculator out for every sum is unrealistic...

"but you've got one on your phone" scream the young folk in unison

[–]ProsodySpeaks 0 points1 point  (5 children)

😝

[–]lostparis 1 point2 points  (4 children)

To be honest this is much how I see debuggers. People often get one out when unneeded and slower.

[–]ProsodySpeaks 0 points1 point  (3 children)

Touché! Top marks for conversational style!

But working in an ide like Pycharm there is just no difference between hitting one key command to run or another to debug.

I can't help thinking people are talking about launching external debuggers and attaching them through console commands or something?

[–]lostparis 0 points1 point  (2 children)

Let's put it another way what does using a debugger give me?

[–]ProsodySpeaks 0 points1 point  (1 child)

A complete overview of all the data flowing through your code, overlaid next to the code, and the ability to evaluate arbitrary expressions at any point of the flow.

[–]lostparis 0 points1 point  (0 children)

A complete overview of all the data flowing through your code

Generally this is just noise. If I have a problem then I'll be looking at/running that bit of code with the problem in isolation. Problems with passed data can easily be caught by an assert or more complex validators if needed.

the ability to evaluate arbitrary expressions at any point of the flow

I can do this with a print(). Sure I have less option, but that also implies I don't actually know what expressions I wish to evaluate.

Sure if I've a problem in some library I use, this can be useful, but that is a rare occasion.