These days, most of my work is very related to the online world. Building web sites, reviewing web applications, integrating with web services, coordinating people who are far away from each other, etc. Whenever I find a new tool or service or an innovative, interesting idea about working online, I share it in this category.
OctroTree – Google Chrome extension for browsing GitHub code repositories. I promise you, this is one of those things that you wouldn’t believe you lived without before. Fast, convenient, with support for private repositories (via API access token), GitHub Enterprise, and keyboard shortcuts. Absolutely essential for anyone who is on GitHub!
It’s after bits like this one, I think I should spend more time reading documentation:
METHODS
Create
Create a new transaction.
This routine should _never_ be called by anything other than RT::Ticket. It should not be called from client code. Ever. Not ever. If you do this, we will hunt you down and break your kneecaps. Then the unpleasant stuff will start.
TODO: Document what gets passed to this
RT::Transaction->Create() developer manual for Request Tracker 4.2.
Use the powerful CakePHP 3 ORM in any of your #PHP projects!https://t.co/rwQcsRHQWd
— CakePHP (@cakephp) May 20, 2015
AWS Official Blog covers the upcoming leap second shenanigans in “Look Before You Leap – The Coming Leap Second and AWS“:
The International Earth Rotation and Reference Systems (IERS) recently announced that an extra second will be injected into civil time at the end of June 30th, 2015. This means that the last minute of June 30th, 2015 will have 61 seconds. If a clock is synchronized to the standard civil time, it will show an extra second 23:59:60 on that day between 23:59:59 and 00:00:00. This extra second is called a leap second. There have been 25 such leap seconds since 1972. The last one took place on June 30th, 2012.
Not all applications and systems are properly coded to handle this “:60” notation.
SingleHop – a cloud-based hosting company – created this infographic on the cost of loss for when your backups aren’t up to the par. This should work well as a reminder, especially if printed out and hung on the wall in front of a sysadmin (but also somewhere, where the management can occasionally see it too).
