TODO update

content/notes/twitter/8871771245/index.md

@@ -4,4 +4,4 @@ tags:
 - imported
 - from-twitter
 ---
-I made an installer: open .webloc files in windows http://github.com/jphastings/WinWebloc/downloads
+I made an installer: open .webloc files in windows https://github.com/jphastings/WinWebloc/downloads

content/notes/twitter/93033369390170112/index.md

@@ -1,7 +0,0 @@
----
-date: "2011-07-18T19:04:18Z"
-tags:
-- imported
-- from-twitter
----
-Don't be tempted to use either the steam or sauna rooms. "Danger 440V" applies to the whole room. http://instagr.am/p/H-DA8/

content/posts/tumblr-jpinjapan/2009-08-02-a-crazily-busy-first-day/index.md

@@ -16,7 +16,7 @@ First off we wandered around the Imperial Palace gardens. The outer section, whi
 
 These are some of the most beautiful gardens I've seen (having a Mum who worked in an Arboretum, that's saying a lot!) - one entire section was a grassland ecosystem moved piece by piece into the Palace's grounds because their original habitat was to be destroyed to create a residential district.
 
-The entire gardens were both stunning and surprisingly informative (with the odd museum and even English translations on info-posts) - there will be plenty of photos [on flickr](http://flickr.com/photos/jphastings) when I have the time!
+The entire gardens were both stunning and surprisingly informative (with the odd museum and even English translations on info-posts) - there will be plenty of photos [on flickr](https://flickr.com/photos/jphastings) when I have the time!
 
 Next stop was the Yasukuni Shrine to meet Ai, a small park dedicated to War Victims built in 1836 (over 2.5 million are commemorated to date - kamakazi bombers are recorded as telling each other they'll meet again at Yasukuni). It also included the first ever Western style bronze statue of the military commander who first pushed a modernization (ie. westernization) of the Japanese army, earning him a wound, which took over 4 months to kill him, courtesy of the samurai.
 

content/posts/what-makes-a-good-tech-team-great/index.md

@@ -53,13 +53,13 @@ I believe that context is critical to everything in life. I’m sure there’s a
 
 The only true way to build a shared context is to discuss things, often at length and sometimes without specific direction. Putting time aside to chat to your colleagues — from all over the business — will give you an idea of what’s important to them and how best to work with them.
 
-“Naming things” is one of the [two hardest problems in computer science](http://web.archive.org/web/20230822235603//twitter/#/codinghorror/status/506010907021828096), and naming them well is _critical_. One word can have many different meanings — some specific to our company — so when you commit words to lasting documentation or code make sure you choose your words carefully.
+“Naming things” is one of the [two hardest problems in computer science](https://web.archive.org/web/20230822235603//twitter/#/codinghorror/status/506010907021828096), and naming them well is _critical_. One word can have many different meanings — some specific to our company — so when you commit words to lasting documentation or code make sure you choose your words carefully.
 
 As engineers we spend a lot of time doing this, even in something as transient as short-lived script variable names. You never know when someone else, or an older you, will need to understand what you were trying to do.
 
 Making code “self” documenting is, for us, frequently the best form of documentation. The further an explanation gets away from the thing it’s documenting the less likely it is to be ‘in-sync’, and the more work the reader has to do to figure out what was meant.
 
-Self-documenting code is incredibly useful, but when it comes to “best practice” we’ve found that a set of separate, community maintained [guidelines](http://web.archive.org/web/20170521072344/http://deliveroo.engineering:80/guidelines/) makes for a great space to both discuss and refer to the approaches we take to common problems.
+Self-documenting code is incredibly useful, but when it comes to “best practice” we’ve found that a set of separate, community maintained [guidelines](https://web.archive.org/web/20170521072344/http://deliveroo.engineering:80/guidelines/) makes for a great space to both discuss and refer to the approaches we take to common problems.
 
 We also structure our unit tests to demonstrate the specific cases we expect our code to be used in, and the expected outcome. This gives us a reliable shared basis for talking about our code.
 

todo.md

@@ -18,6 +18,7 @@ Things I might work on within my personal blog's software.
   - [x] Fix goodreads links (point to blog)  
   - [x] Fix instagram links (~~point to blog~~ delete; they're cross-posts anyway)  
   - [ ] Show (internal) replies to this note
+  - [ ] Remove 'instagr.am' posts (they're already imported as cross-posts)
 - [ ] Import from Omnivore daily  
 - [ ] Facebook import?
 - [ ] Record new webmentions on publish