[budman1]

change that 10% to 0.5% and I would agree. i am 62, worked in low level coding and hw interfacing. 'routinely' not even; i would say on occasion, needed to look at a bit, or even more rare, had to write a bit (like a small module)

[spoiler]

Curious, what do you normally use? I had to write a few timing sensitive MC drivers and the only way I knew how onto do that reliably was using assembly. But granted, it wasn't _often_, just more than I expected (especially for someone who doesn't normally do that low level stuff, this was for an art project)

[budman1]

sure. timing sensitive stuff. < 50 lines. jump back to C as soon as the critical stuff is over.

'performance stuff'. i try to solve it in C for a bunch of reasons; others readability is one. almost never need to do more than a short macro of assembly embedded in C.

the actual most use of have for assembly is "what is happening here.." and need to ask the debugger for the assembly for some deeper understanding.

Some years, did these things 5 times, so maybe 20 hours. Other years, never.

As far as "sit down and write some assembly to solve problem X", the answer is never. (except when X is right in the middle of the above items)

[shric]

Yeah, my father is now 70, I do remember he wrote assembly language in the late 80s but not since.