My Next Job
+Thick Apps Still Lose
+ +Thick apps won mobile. Fine.
+On laptop (and desktop) it's not so clear. What is better, thick or thin? +I tend to live mostly in thin land, although I use some thick apps +regularly, like Twitter's Mac client and Apple Photos.
+Every so often I give a big native app a try: Excel instead of +Google Sheets, Mail.app instead of Gmail, Reminders +instead of the barebones Tasks built into Gmail. (I can't bring myself +to try Word). But it's disappointing to see how those fancy apps keep +shooting themselves in the foot!
+Take for example this Excel error message. Excel is whining that it +can't verify my subscription the first time I ran Excel untethered +(version 15.11.2, for what its worth). Sure you can click through the +warning, but would a newbie know to do that? At best off-putting, at worst +downright disorienting. Why warn me of this at all? And why in a modal +that stops me dead in my tracks?
+It seems thick apps should win. They rock the unplugged use case. An even +better situation is flaky networks -- tethered, conference WiFi, +travelling. UI's deal notoriously poorly with intermittent or partial +outages. A thick client, relying on that connection only for hitting +API's, can hide the network.
+Another place they should shine is the UI itself. They should be fast, +beautiful, and featureful. Too often they're not. For example I find +Mail.app to be clunky, difficult to customize, and its keyboard shortcuts +few and poorly done. Gmail is pretty good!
+Finally there's the upgrade problem. Thick apps need conscious effort from +their users before their work sees user time and they get feedback. And +that's what drives innovation. Long cycles means slower (less) invention. +One example I love is Gmail's "undo send" feature. Boy, you sure do miss +that when you need it and it's not there! That should be on every thick +client by now, but I don't think it is. I do know that Gmail has it and +Mail.app still doesn't.
+Maybe the Internet can help. Look at Chrome with its awesome auto +updates. What makes this work is solid engineering and exceptional quality +control. I've never seen behind the Google curtain, but I bet there's no +magic, just a lot of good engineering that leads to good software. Like: +good design and code reviews, tons of test coverage across many scenarios, +diverse and well-instrumented canaries, and thorough performance and +resource use testing. If Google didn't all of that so well, then we +wouldn't accept frequent pushes. Without the frequent upgrade cycle, +Chromes feature cycle would languish.
+Electron is another bright spot. This is the framework that gives +Slack and GitHub's thick clients their fit and finish. It makes these feel +like true native apps, even though they are mostly web controls with +JavaScript the covers. Right-clicking still doesn't do what I want, and +text controls are finicky, but it's close. But what those rough edges buy +you, and the software producer, are frequent, reliable, and clean +upgrades.
+My natural preference would be for thick apps. If they were done well, +I'd use them.
+My Next Job
Sef Kloninger
diff --git a/index.html b/index.html
index fcbef8b..07a3fee 100644
--- a/index.html
+++ b/index.html
@@ -12,7 +12,7 @@
-
+
Skip to main content
@@ -75,7 +75,109 @@
I listen to a fair number of podcasts. The Accidental Tech
+Podcast is my favorite by a mile. It's the one that I look forward to every week. It comes out on
+Thursdays, often right when I'm leaving work. It's a sign that
+the weekend is right around the corner. I'll get some of the reasons why out of the way quickly, the reasons
+particular to me and my tastes. But what I appreciate more than the content of ATP are the
+hosts and the care and they take to produce a good show. Although they joke about how much of the show is devoted to feedback,
+it's one of my favorite parts. It shows that they listen and are
+learning. And they share that learning with all of us. A recent
+example was six minutes or so into Episode 570 when I learned
+how home power battery systems, when full, signal this by changing
+the frequency of AC power as a signal to solar panels to back off.
+Fascinating! I like the members-only specials. It's OK with me that these are only
+available to members.
+I like how candid they've been talking about ad revenue drying up
+recently and they could use the extra revenue channel. these
+episodes are a nice way to reward members. They've managed to
+do these without compromising the core show. The best thing they ever did on ATP was getting a sponsor to send John
+toasters to review. And review he did! I didn't appreciate how
+many bad toasters there are, and how they can be bad for so many
+reasons. My favorite reason was poor knob feel. Nice work John, Marco, and Casey.
+Please keep it up for a long, long time.
Sef Kloninger
@@ -346,74 +448,6 @@ YouTube is one of the worlds foremost platforms for social commentary,
education, and free speech. And it's plenty of entertainment too. Sounds
like fun. Thick apps won mobile. Fine. On laptop (and desktop) it's not so clear. What is better, thick or thin?
-I tend to live mostly in thin land, although I use some thick apps
-regularly, like Twitter's Mac client and Apple Photos. Every so often I give a big native app a try: Excel instead of
-Google Sheets, Mail.app instead of Gmail, Reminders
-instead of the barebones Tasks built into Gmail. (I can't bring myself
-to try Word). But it's disappointing to see how those fancy apps keep
-shooting themselves in the foot! Take for example this Excel error message. Excel is whining that it
-can't verify my subscription the first time I ran Excel untethered
-(version 15.11.2, for what its worth). Sure you can click through the
-warning, but would a newbie know to do that? At best off-putting, at worst
-downright disorienting. Why warn me of this at all? And why in a modal
-that stops me dead in my tracks? It seems thick apps should win. They rock the unplugged use case. An even
-better situation is flaky networks -- tethered, conference WiFi,
-travelling. UI's deal notoriously poorly with intermittent or partial
-outages. A thick client, relying on that connection only for hitting
-API's, can hide the network. Another place they should shine is the UI itself. They should be fast,
-beautiful, and featureful. Too often they're not. For example I find
-Mail.app to be clunky, difficult to customize, and its keyboard shortcuts
-few and poorly done. Gmail is pretty good! Finally there's the upgrade problem. Thick apps need conscious effort from
-their users before their work sees user time and they get feedback. And
-that's what drives innovation. Long cycles means slower (less) invention.
-One example I love is Gmail's "undo send" feature. Boy, you sure do miss
-that when you need it and it's not there! That should be on every thick
-client by now, but I don't think it is. I do know that Gmail has it and
-Mail.app still doesn't. Maybe the Internet can help. Look at Chrome with its awesome auto
-updates. What makes this work is solid engineering and exceptional quality
-control. I've never seen behind the Google curtain, but I bet there's no
-magic, just a lot of good engineering that leads to good software. Like:
-good design and code reviews, tons of test coverage across many scenarios,
-diverse and well-instrumented canaries, and thorough performance and
-resource use testing. If Google didn't all of that so well, then we
-wouldn't accept frequent pushes. Without the frequent upgrade cycle,
-Chromes feature cycle would languish. Electron is another bright spot. This is the framework that gives
-Slack and GitHub's thick clients their fit and finish. It makes these feel
-like true native apps, even though they are mostly web controls with
-JavaScript the covers. Right-clicking still doesn't do what I want, and
-text controls are finicky, but it's close. But what those rough edges buy
-you, and the software producer, are frequent, reliable, and clean
-upgrades. My natural preference would be for thick apps. If they were done well,
-I'd use them. I listen to a fair number of podcasts. The Accidental Tech
+Podcast is my favorite by a mile. It's the one that I look forward to every week. It comes out on
+Thursdays, often right when I'm leaving work. It's a sign that
+the weekend is right around the corner. I'll get some of the reasons why out of the way quickly, the reasons
+particular to me and my tastes. But what I appreciate more than the content of ATP are the
+hosts and the care and they take to produce a good show. Although they joke about how much of the show is devoted to feedback,
+it's one of my favorite parts. It shows that they listen and are
+learning. And they share that learning with all of us. A recent
+example was six minutes or so into Episode 570 when I learned
+how home power battery systems, when full, signal this by changing
+the frequency of AC power as a signal to solar panels to back off.
+Fascinating! I like the members-only specials. It's OK with me that these are only
+available to members.
+I like how candid they've been talking about ad revenue drying up
+recently and they could use the extra revenue channel. these
+episodes are a nice way to reward members. They've managed to
+do these without compromising the core show. The best thing they ever did on ATP was getting a sponsor to send John
+toasters to review. And review he did! I didn't appreciate how
+many bad toasters there are, and how they can be bad for so many
+reasons. My favorite reason was poor knob feel. Nice work John, Marco, and Casey.
+Please keep it up for a long, long time.The iPhone's SIM Tray Went Away Too Soon
+ My Love Letter to ATP
+
+
+
+
+
+The iPhone's SIM Tray Went Away Too Soon
The Bee Puzzle
Thick Apps Still Lose
-
- My Love Letter to ATP
+
+
+
+
+
+
+
+
+Comments
diff --git a/rss.xml b/rss.xml
index 2cc0830..9d398c9 100644
--- a/rss.xml
+++ b/rss.xml
@@ -1,5 +1,88 @@
-
Comments
+ + + + + Comments powered by Disqus + + +