4 ms·
I really like the point about considering cloud computation costs. It would be great if individual developers could get feedback like, "This patch caused X% CPU
by 549362-30499 9y ago
I really like the point about considering cloud computation costs. It would be great if individual developers could get feedback like, "This patch caused X% CPU cost per request, resulting in Y% monthly cost increase to keep projected usage below alert trigger levels." I also like the note about the headless abstraction, although I think it could gain some strength by talking about AWS Lambda or the actor model.
But, I think the dedication to writing perfect code without executing it is misguided. It's 2018 - we have interactive debuggers, excellent profiling tools, and unit tests. Most developers have a computer with 4+ cores and 8G+ of memory. It would be foolish not to take advantage of that.
- DrScump 9y agoOne thing I hate about the modern disregard for resource consumption is that I can't tell whether a given app or program is merely sloppily inefficient, or if it's ma!ware-laden. (Too often, it's probably both.)
- lykr0n 9y agoJava has this built in, sort of. Your application OOM'ed? Here is a heap dump, please tell us what happened and fix it.