Yes Understanding the algorithm, the states, the model, the constraints, the dependencies, the properties,... at all times is what makes you an engineer. Tech

Yes Understanding the algorithm, the states, the model, the constraints, the dependencies, the properties,... at all times is what makes you an engineer. Technical standards and publications about real life issues (like mutex, db management,...) often use pseudo code, because the actual implementation doesn't matter. Pseudo code is also relevant because languages change anyway. And in some companies and industries, several teams use totally different codes you won't know of. Coding right away is possible. But it's not the same job. You can be paid big for actually thinking through your code, and not just writing it.