5 ms·

We're 20 years past the point where you can expect everyone in tech to trace every instruction down to machine instructions. Higher level languages abstract awa

We're 20 years past the point where you can expect everyone in tech to trace every instruction down to machine instructions. Higher level languages abstract away the need for it, and for the most part, we can rely on the authors of those languages to make many of the decisions that impact performance. The rest of us learn about these details on posts like this. It's not a sad fact, in fact it's probably one of the most useful things that's happened in tech. It frees people to think about other problems.

metafunctor 4y ago
Not sure if you were around 20 years ago, but you sure couldn't expect everyone in tech to understand machine instructions as well as the layers above, all the way up to corporate politics. But some people, yeah, they could do it. That has not changed.
deleted 4y ago
[deleted]
TillE 4y ago
I barely touch assembly in my day to day work, but I do understand on a fairly deep level how a computer works, which I feel is extremely important and very frequently influences how I write high-level code. Certainly one can bang out code their entire career without ever having a clue how machine code works, but I really wouldn't advise it. At worst it leads to total ignorance, and at best you accumulate a disconnected set of "best practices" as inscrutable lore handed down from on high.
- ZephyrBlu 4y ago
  What do you consider "high-level code" and in what way does deeply understanding how a computer works influence your approach?
  - iopq 4y ago
    In college, I optimized the array removal routine from O(N^2) to O(N) by using INVARIANTS But it probably ran in like 100us anyway
    - aspyct 4y ago
      Ugh, invariants... Anyway, complexity stays relevant, no matter what language you use. That's the real deal.
      - iopq 4y ago
        It only stays relevant if the JavaScript is too slow. In the case of removing two elements from an array of length 8, it's not too slow to remove them one by one since, again, it runs in microseconds
- Aeolun 4y ago
  You go as deep as you need to. My day job involves writing tons of Javascript and there is zero need for me to dive into the underlying processes until something goes wrong. So far the lowest I’ve ever needed to go was the node source.
- iopq 4y ago
  When I did web dev it was more important to know how the WEB BROWSER works, not how machine code works it's not useful to know how the browser allocates memory or garbage collects it, it's more useful to know that it has web sockets. Don't get the idea that things you know are relevant to other people.
ryanbrunner 4y ago
If you're not raining about how your code translates to logic gates, you're not a competent programmer. /s Abstractions are good, and while we should be careful not to completely trust a brand new abstraction, high level languages are established enough that we don't need to worry about it.
ivanhoe 4y ago
20 years ago ASM was just as cryptical black magic to most of programers as it is today... try perhaps 40 y/a...

metafunctor 4y ago

Not sure if you were around 20 years ago, but you sure couldn't expect everyone in tech to understand machine instructions as well as the layers above, all the way up to corporate politics. But some people, yeah, they could do it. That has not changed.

deleted 4y ago

[deleted]

TillE 4y ago

I barely touch assembly in my day to day work, but I do understand on a fairly deep level how a computer works, which I feel is extremely important and very frequently influences how I write high-level code. Certainly one can bang out code their entire career without ever having a clue how machine code works, but I really wouldn't advise it. At worst it leads to total ignorance, and at best you accumulate a disconnected set of "best practices" as inscrutable lore handed down from on high.

ZephyrBlu 4y ago
What do you consider "high-level code" and in what way does deeply understanding how a computer works influence your approach?
- iopq 4y ago
  In college, I optimized the array removal routine from O(N^2) to O(N) by using INVARIANTS But it probably ran in like 100us anyway
  - aspyct 4y ago
    Ugh, invariants... Anyway, complexity stays relevant, no matter what language you use. That's the real deal.
    - iopq 4y ago
      It only stays relevant if the JavaScript is too slow. In the case of removing two elements from an array of length 8, it's not too slow to remove them one by one since, again, it runs in microseconds
Aeolun 4y ago
You go as deep as you need to. My day job involves writing tons of Javascript and there is zero need for me to dive into the underlying processes until something goes wrong. So far the lowest I’ve ever needed to go was the node source.
iopq 4y ago
When I did web dev it was more important to know how the WEB BROWSER works, not how machine code works it's not useful to know how the browser allocates memory or garbage collects it, it's more useful to know that it has web sockets. Don't get the idea that things you know are relevant to other people.

ryanbrunner 4y ago

If you're not raining about how your code translates to logic gates, you're not a competent programmer. /s Abstractions are good, and while we should be careful not to completely trust a brand new abstraction, high level languages are established enough that we don't need to worry about it.

ivanhoe 4y ago

20 years ago ASM was just as cryptical black magic to most of programers as it is today... try perhaps 40 y/a...