Most of this is motherhood and apple pie, it’s a good list to use regardless of your underlying infrastructure.
useful for building command shell with completions
Reuven Cohen has an interesting post on cloud computing and it’s origins in the darknets of eastern europe in the mid-90’s. It makes a certain sort of sense, criminal enterprises face a much harsher environment than most IT organizations with greater need for not just geographical redundancy but jurisdictional diversity so that operations can continue in the face of multiple attacks. I have occasionally thought that fast flux hosting as practiced by various botnets might be a useful source of techniques for solving certain forms of scaling problems. Of course legitimate uses are hampered by the need to ask permission, and to not divert resources from their rightful owner; but scenarios where users are asked to ‘help out’ their favorite sites by hosting caching proxies or edge-of-cloud application-servers.
Thanks to James Urqhart for the link.
How to install gitosis on your server.
It’s a truism of knowledge work that more time and energy is expended in communicating about the work that is being done than is used in actually performing the work.
As generations of technologists have discovered and rediscovered, to be truly good at what you do and perceived to be so by your customers and coworkers, you must not only do what you do, you must document it clearly so that what has been done is known.
O good, a clear tutorial on something I’m not very good at but need to do on a regular basis.
This article gets to the very core of what I want to talk about at Industrial Intellect. Knowledge is becoming one of the key factors of production. Both the explicit knowledge that is captured in documentation, design and in organizational communications. But also the implicit knowledge that workers build up about how to access knowledge, and what the exceptions are, and what customary practice has entailed. Automation makes this problem worse, it is much more difficult for somebody to step in to a strange codebase without a native guide, than to be introduced to it by coworkers who at least know the reasons for the awkward constructions and bizarre syntax.
A fairly comprehensive starting point; good to hand to smart people who are curious about linux.
