3 ms·
This is coming from the perspective a person who is not a web programmer, but who has done lower-level programming. Memory leaks and other things (security iss
by hereforphone 5y ago
This is coming from the perspective a person who is not a web programmer, but who has done lower-level programming. Memory leaks and other things (security issues included) are going to naturally come from focusing the education entirely on upper stack subjects. One must understand the complete machine in order to actually make things solid. The complexity is making that increasingly difficult to do these days unfortunately.
- nmaludy 5y agoWarning, im feeling synical this evening... Completely agree! I find that a lot of developers don't understand how things work under the hood or how things fit together. This always comes back to bit them. Same can be said for modern infrastructure engineers / DevOps / sysadmins.
- democracy 5y agofwiw we operate on layers and layers of someone else's code, that's not possible to understand how each dependency works, what's its performance, etc. And also do it for each new update of such libraries. Unless you develop in some very closed environment maybe, but for a modern java/js project that's not possible. The reasonable approach is to load test the mostly used workflows, optimise if necessary - anything else would be fixing imaginary issues, working on non-existing problems, etc - there is normally no time or money for it.
- NeutralForest 5y agoI agree with the sentiment but at the same time, there is so much to learn now. Especially w.r.t the web, there are so many layers of abstractions and frameworks, you might even do "things right" on your end but have memory leaks hidden under all that abstraction. At the same time, writing everything yourself isn't possible because of time/money/life constraints. I also think the web is terribly bloated though.