Without clear documentation, organizations risk confusion, duplication of efforts, and inefficient data storage. Making documentation a priority ensures a seamless workflow.
Over the past however long it's been since my last infrastructure blog post, I've been doing a ton of work across various organisations and my own personal setup to get things up to a more acceptable standard. Rather than do small posts for each infrastructure overhaul, I've decided to bundle it all into one, to hopefully demonstrate how each experience feeds into the other and vice versa. For ease of reading, I'll break each infrastructure into its own section and let you jump between them at your leisure.
Every Phone Should Be Able to Run Personal Website
Back in 2009, anynone with a Nokia could have a personal website running on their own phone. Sadly this amazing piece of tech was never widely adopted. Today’s phone are far more powerful than those Nokias both in performance and battery backup and still we don’t see anyone running a server on their phone. Why?
I think this was never implemented on phones because there’s no incentive for large corporations to work on something like this.
It’s 3am. Paul, the head of PayPal database administration carefully enters his elaborate passphrase at a keyboard in a darkened cubicle of 1840 Embarcadero Road in East Palo Alto, for the fifth time....
The CNET Lesson: Content Pruning Is Dumb For News Content, Don’t Do It
Discussing the dumb thing CNET did in an effort to please the Google Gods: Don’t cull old news content to improve your SEO ranking. That’s your history!
Incident Management: How Organizational Context Can Help
Catalog, a new feature on incident.io's platform, can give teams the dynamic contextual awareness needed to effectively and efficiently respond to incidents when they occur.