Computer science is about everything except I/O, and application development is about nothing but I/O.
— Justin Searls
We absolutely need experts who focus exclusively on product, on engineering, on policy — those demand high-quality, dedicated specialists — but we also need people — I've taken to calling them technologists — whose expertise cuts across those three domains. Someone needs to put the pieces together. Someone needs to navigate the digital world (for a business, a project, any institution) without blind deference to vertical experts, and without monkeying dumb Silicon Valley tropes or giving credence to breathless LinkedIn thoughtleadering. Someone needs to see the full set of options that is available to reach a goal, and that requires playing across these domains.
The Utilization Saturation and Errors (USE) Method is a methodology for analyzing the performance of any system. It directs the construction of a checklist, which for server analysis can be used for quickly identifying resource bottlenecks or errors. It begins by posing questions, and then seeks answers, instead of beginning with given metrics (partial answers) and trying to work backwards.
Systems performance is an important skill for all computer users, whether you're trying to understand why your laptop is slow or optimizing the performance of a large-scale compute environment (for example, Facebook's datacenters or the Netflix cloud). Systems performance is the study of application, operating system, kernel, and hardware performance.
Scriban is a fast, powerful, safe and lightweight scripting language and engine for .NET, which was primarily developed for text templating with a compatibility mode for parsing liquid templates.
The world's most widely used web app scanner. Free and open source. Actively maintained by a dedicated international team of volunteers.
It's useful to look back through the change history, read original design documents, and understand why a component was built the way it was. But you also need to look closely at how the component integrates into the system today, where it can easily have taken on additional roles.
See also: Hyrum's Law