500 Lines or Less (2016)
Hmm. I get the sentiment (500, i.e. not too short, not too long), but 500 lines will mean different things for different people and different programming stacks. It literally can mean 50000 vs 500 "lines of knowledge" required. I'm not sure why would you name your book like that.<p>Consider:
500 lines of defensively written web server C++ code.
500 lines of C driver code.
500 lines of assembly.
500 lines of php script.
500 lines of java server app.
500 lines of c# .net desktop app.
500 lines of electron javacript code.<p>When I imagine the amount of a "useful program" I can write in 500 lines of C (or other low level statically typed language) while using minimal amounts of library code versus the "useful program" I can write in 500 lines of Javascript while using maximum amounts of Electron library code (i.e. all the functionality of chromium + node + electron), the difference is staggering ( try writing a cross platform video player in C vs Electron.. ). That doesn't mean Electron is better, especially if you need maximum resource budget usage or maximum control.<p>It's never about the number of lines, it's how you use them ;)