4 ms·
The point is that if you understand how the high-level code you write gets translated to what runs on the actual CPU and memory then you write more performant h
by jebarker 2y ago
The point is that if you understand how the high-level code you write gets translated to what runs on the actual CPU and memory then you write more performant high-level code by default the first time round. So you can get to market just as quickly. Doesn't mean there's not more speed or memory optimizations you can make later but you just raise the bar generally.
- epolanski 2y agoplease make a general simple example of how knowing memory and cpu applies to overwhelming majority of people out there glueing APIs together.
- jebarker 2y agoI'm not ignoring your request, but I need to think about it a little as my day to day work isn't just pasting together APIs. If the only thing an engineer is allowed to do is paste together a fixed set of APIs then they may well be completely limited.
- fragmede 2y agoKnowing how the underlying system - CPU ram network db - works is the difference between using an ORM or SQL query to do SELECT * FROM db across the network, and filtering it locally with program code, and using a WHERE clause in the SQL, a pattern I've fixed for multiple startups.