6 ms·
Yes, the difference between coding (writing software) and engineering (making informed trade offs about system design) is effectively bound up in analyses like
by voidhorse 1mo ago
Yes, the difference between coding (writing software) and engineering (making informed trade offs about system design) is effectively bound up in analyses like those supported by concepts like pareto efficiency.
One should keep in mind though that not all problems have a neat solution. Many spaces have multiple efficient points that still need to be chosen from, and many pareto optimization problems actually become NP hard computationally when the problem is large enough.
- ksclk 1mo agoSay someone wanted to transition from coding to engineering. What path would you have them take? What should they learn?
- voidhorse 1mo agoI would say start with software architecture books for large or highly distributed systems. This will get you thinking beyond code level to system component level with subject matter that's familiar. From there I would round things out with general systems theory books and even dabble in some non-software engineering texts just to get a sense of how people reason about designing systems and evaluating trade-offs. That's just my two cents on it.