justin․searls․co

Tabelogged: 博多らーめん ShinShin 天神本店

I visited this restaurant on April 19, 2019, and gave it a 4.5 on Tabelog.

Name: 博多らーめん ShinShin 天神本店
Description: 天神、西鉄福岡(天神)、天神南/ラーメン、居酒屋、餃子

Which Google translates into English as:

Name: Hakata Ramen Shinshin Tenjin Main Store
Description: Tenjin, Nishitetsu Fukuoka (Tenjin), Tenjin Minami/Ramen, Izakaya, Gyoza

Tabelogged: かつ良

I visited this restaurant on April 10, 2019, and gave it a 3.0 on Tabelog.

Name: かつ良
Description: 下北沢、池ノ上、世田谷代田/とんかつ

Which Google translates into English as:

Name: Katsurai
Description: Shimokitazawa, Ikenoue, Setagaya Daita/Tonkatsu

Tabelogged: 麺酒処 ぶらり

I visited this restaurant on April 10, 2019, and gave it a 3.5 on Tabelog.

Name: 麺酒処 ぶらり
Description: 日暮里、西日暮里、三河島/ラーメン、つけ麺

Which Google translates into English as:

Name: Noodle Bar Burari
Description: Nippori, Nishinippori, Mikawashima/Ramen, Tsukemen

Tabelogged: クラフトマン SENDAI

I visited this restaurant on April 10, 2019, and gave it a 4.0 on Tabelog.

Name: クラフトマン SENDAI
Description: あおば通、広瀬通、仙台/イタリアン、ピザ、ビアバー

Which Google translates into English as:

Name: Craftsman Sendai
Description: Aoba-dori, Hirose-dori, Sendai/Italian, Pizza, Beer bar

Tabelogged: Rojiura Curry SAMURAI. 下北沢店

I visited this restaurant on April 10, 2019, and gave it a 4.0 on Tabelog.

Name: Rojiura Curry SAMURAI. 下北沢店
Description: 下北沢、東北沢、新代田/スープカレー、カレー、カフェ

Which Google translates into English as:

Name: Rojiura Curry Samurai. Shimokitazawa Branch
Description: Shimokitazawa, Higashikitazawa, Shindaita/Soup curry, curry, cafe

Merge Commits artwork

Tech Done Right: Code Style

Merge Commits

Noel Rapin invited me on Table XI's podcast for a third and final time. I got a chance to discuss my thinking on Standard Ruby's design, just a few months after launching it.

Appearing on: Tech Done Right
Published on: 2019-01-30
Original URL: https://www.techdoneright.io/54

Comments? Questions? Suggestion of a podcast I should guest on? podcast@searls.co

Merge Commits artwork

TalkScript: Don't Mock Me

Merge Commits

Nick Nisi invited me to his TypeScript podcast to discuss my unrelated talk about mocking best practices in the JSConf edition of Please don't mock me.

Appearing on: TalkScript
Published on: 2018-09-05
Original URL: https://podcasts.apple.com/us/podcast/episode-17-presentations-vulnerability-and-solving/id1072291074

Comments? Questions? Suggestion of a podcast I should guest on? podcast@searls.co

You make less money than you used to. Blame your iPhone.

For years, economists have been puzzling over why, despite unprecedented technological innovation since the dawn of the Internet, productivity is flat. Really, nobody seems to know why! Look no further than this week's news to find a consensus opinion that the just-around-the-corner cure for lagging productivity numbers is—wait for it—more technological innovation.

Productivity is a curiously-named economic measure that essentially boils down to "amount of money you generate for your employer over time." And because the promise of most technology is to enable people to do work faster, we should expect technology's useful impact to be measurable, even with an (oversimplified) equation like Labor + Technology = Productivity.

But something has clearly gone wrong. If we work backwards, we already know productivity is flat. And we are equally certain that technology has improved over the last twenty years. That leaves just one variable for which a negative value could explain the productivity gap: maybe we're literally doing less useful work every day. Reflecting on my own experience, I'd go a step further and ask, what if recent technological advances are actually decreasing our productivity?

To be continued…