This Japanese Toaster Costs $270. It Only Makes One Slice at a Time

Perfectly made toast isn’t just an obsession in Japan. It’s a business opportunity.

Over the past few years, there’s been a quiet boom in the pursuit of expertly reheated bread, from high-end toasters and premium loaves, to cafes catering to connoisseurs seeking that satisfying crunch.

Joining the fray is the next best thing for sliced bread, a toaster designed for just one task: making a single piece of toast, flawlessly. Made by Mitsubishi Electric Corp., better known for its workaday refrigerators and rice cookers, the Bread Oven hit store shelves last month, retailing for about 29,000 to 30,000 yen ($270). While that might seem expensive, Japanese consumers are already used to paying top price for toasters; the popular Balmuda, which debuted a few years ago, sold for about $230.

Make Great Decisions Quickly With TOMASP

As technical leaders and managers, our job is to make the right decision most of the time. Hiring, firing, technology choices, software architecture, and project prioritization are examples of high impact decisions that we need to make right if our teams are to be successful.

This is hard. As humans, we’re naturally bad at making those types of decisions. I’ll show you how you can consistently make great decisions quickly using a simple framework called TOMASP. I made up the acronym for the purpose of this blog post but it’s inspired from many great books (see resources) as well as my personal experience of leading engineering teams for almost 15 years.

Yes, You Should Estimate Software Projects

I hear more voices saying there is little point in doing time-based estimations on how long building software will take, and thus we should just stop doing it. “Let’s just use story points and estimate complexity, but not the time” and “Let’s just try #noestimates” are suggestions people around me recently brought up. I’m personally skeptical of both approaches. While I do think that doing time-based estimates is really hard, it comes with so many benefits for those who keep doing it.

SLOs Are the API for Your Engineering Team

Key Takeaways

• Establish a perimeter: SLOs give you the ability to push back when demands from other parties exceed your capacity to deliver what the business has deemed most important.
• Reach agreement faster: SLOs make interacting with other members of the organization more effective and less unpredictable because all parties have already signed off on the goal.
• Focus on what matters: SLOs mean the arguing can stop. Everyone knows what’s at stake and can make good decisions based on real data without having to waste time debating priorities.
• Drive production excellence: SLOs offer leverage and autonomy to invest in your team’s ability to meet the agreed-upon goals.
• The knob goes both ways: SLOs help you realize when it’s time to tinker and time to hunker (down) and focus on greater resilience.

If your job involves direct leadership of engineering teams, managing how and what they deliver, you’ve surely come across situations where the pressure to deliver features won out and led to poor service reliability. You’ve probably had your team’s workflow disrupted by interference from senior managers about minor individual issues. Or, you’ve seen or heard execs questioning your team’s planned work to reduce technical debt or improve your delivery processes.

Stevey’s Google Platforms Rant

I was at Amazon for about six and a half years, and now I’ve been at Google for that long. One thing that struck me immediately about the two companies — an impression that has been reinforced almost daily — is that Amazon does everything wrong, and Google does everything right. Sure, it’s a sweeping generalization, but a surprisingly accurate one. It’s pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn’t let me show it to anyone, even though recruiting loved it.

Moving Past Shallow Incident Data

Here is some data: the last incident your company experienced lasted 54 minutes. What insight does this data reveal besides a) an incident happened, and b) it lasted 54 minutes (at least according to someone interpreting an event as an incident)?

What else could we glean from this data? Hrm. What if we found that someone marked down when this incident was “detected”? Now we have more data!

What You Need to Know About Continuous Integration

The most popular software applications on the planet have a few things in common. They solve a real problem, they’re (usually) easy to use, and they offer a best-in-class customer experience. Sounds simple, right? Even if you’re just starting your career, you probably know that the opposite is true. In most cases, the “best” apps are often sophisticated projects that require ongoing testing and software updates.

Everything is Amazing, But Nothing is Ours

Back in 2015, I wrote a blog post called Dropbox: the First Dead Decacorn. At the time, it was the most widely shared take I’d ever written. I learned several things from writing this piece, and none of them had to do with Dropbox: I learned, for instance, that a great way to get people to click on your blog post is to make them mad. I also learned about a company called Social Capital, after my soon-to-be-colleague Ray reached out to me about what I’d written. I’m certainly thankful I wrote it.

WeWork Is The Past. This Is What The Future Of Co-Working Will Be.

Top highlight

Welcome to the beginning of the end for traditional office leasing.

Kristin Wilson Oct 9 · 6 min read

Photo by Tom Parkes on Unsplash

WeWork rode its reputation as an “innovative” tech company all the way to a $47 billion valuation in August, only to crash weeks later in spectacular fashion. Yet, while Adam Neumann’s downfall makes for a good headline, contemplating the company’s next move is a waste a time.

How We Run Skillshare

Matt Cooper Sep 19 · 11 min read

The Skillshare team in a recent design sprint

I have the opportunity to meet with other CEOs on a pretty frequent basis. I’m part of a CEO group in NYC that meets monthly for breakfast, attend a few other networking groups that meet several times a year, and each of our investors has an annual portfolio company meeting. A consistent topic of discussion and sharing of best practices is the cadence of how we run the business — annual/quarterly/monthly routines, planning, communications, check-ins, goal setting, etc.

Death, Injuries and an Amputation: Is ‘Resident Evil’ Hollywood’s Most Dangerous Franchise?

Stuntwoman Olivia Jackson nearly died on the set of 2016’s ‘The Final Chapter.’ Her colleague was killed. And over the course of the billion-dollar series, many others have been injured. What happened — and who might pay for it?

It was raining on the day of the shoot. That morning, Sept. 5, 2015, Olivia Jackson mucked around on the lonely stretch of road outside Pretoria, South Africa, where Resident Evil: The Final Chapter was filming. None of the other crewmembers, decked in gum boots and rain jackets, seemed to think they would be shooting that day. Jackson, a 34-year-old veteran stunt performer, had been scheduled to film a fight scene. Instead, at the last minute, she learned that she’d be doing a tricky stunt on a motorcycle.

A forty year career.

The Silicon Valley narrative centers on entrepreneurial protagonists who are poised one predestined step away from changing the world. A decade ago they were heroes, and more recently they’ve become villains, but either way they are absolutely the protagonists. (Although, perhaps the role of protagonist is expanding a bit.) Working within the industry, I’ve worked with quite a few non-protagonists who experience their time in technology differently: a period of obligatory toil required to pry open the gate to the American Dream.

Writing Docs at Amazon

Scott Follow

Feb 10 · 8 min read

Recently, Ben Bashaw published a good article about the way that Amazon (almost uniquely) uses written documents to make decisions. This was posted to Hacker News and a lively discussion ensued. While I was at Amazon, I wrote or contributed to dozens of documents that were presented to Jeff Bezos. In the HN discussion, I was asked for some clarity on the do’s and don’ts of these documents, so I figured I’d write something up in longer form than a comment.

Building a First Team Mindset – Jason Wong’s Blog

Imagine a world where you bring together the top leaders in your organization to solve the company’s most pressing challenges, and, instead of coming together as a core group to solve that problem, they approach the exercise as a collection of factions that are more concerned about their and their team’s self interest than solving the company’s needs. It sounds tragic, but also probably like another day at work for a lot of folks, and it’s why I spend a lot of time building a First Team mindset amongst the leaders in my organization.

Compensation for remote employees

If you can employ anyone, from anywhere, what should you pay them? What is fair?

There are a few ways to go about this: You pay everyone the same, independent of location; You pay people according to local rates; or you make up your own scheme.

TL;DR: Pay well to hire great people

What companies are doing today

Companies that do not hire remotely, tend to pay local rates. They are competing for talent directly with other local companies, and have to adjust rates to be able to hire great people.

Context over control: the future of remote work

Lately, I’ve been reading quite a lot of reports on the state and the future of remote work. While I think it’s great to finally see some open resources about what still looks a very underexplored field, I couldn’t find any unique insights or anything more interesting than some generalized polls or surveys. Yet I think we still know very little about this subject and there’s a lot to be uncovered in terms of strategies, frameworks, and models. This write-up (and more generally this blog) is an attempt to provide insights and more qualitative thinking on such topics.

Microsoft’s LinkedIn loses appeal over access to user profiles

(Reuters) – A federal appeals court on Monday rejected LinkedIn’s effort to stop a San Francisco company from using information that users of the professional networking website have deemed public.

The 9th U.S. Circuit Court of Appeals let stand an August 2017 preliminary injunction that required LinkedIn, a Microsoft Corp unit with more than 645 million members, to give hiQ Labs Inc access to publicly available member profiles.

Why you shouldn’t use pie charts – Tips for better data visualization

I was talking to a colleague the other day who told me about a conversation they just had with a customer. The customer had asked “Why can’t I create pie charts in Funnel?” and my colleague’s response, jokingly, was “Our product team really doesn’t like pie charts”. While it’s true most of us are no huge fans of pie charts, the reason we haven’t invested in supporting a pie charting option is because we believe they are rarely a good fit for the problem they’re intended to solve.

How to Design Your Office for Improved Productivity and Purpose

Design creates culture. Culture shapes values. Values determine the future.
–Robert L. Peters

When’s the last time you thought about office design? Would you be proud to show your office to family and friends? Are you comfortable in your workplace?

The average full-time employee works 1,800 hours per year, most of which are likely in an office. Here at Bonusly, we recently redesigned our headquarters, which got us thinking about how our space impacts the team. That meant adjustable desks, modern chairs, updated layouts, and new technology. And it all started when we asked ourselves, “How can we design our office for productivity and purpose?” Now we’re sharing our lessons with you!

The Secret to a Great Planning Process — Lessons from Airbnb and Eventbrite

This article is by Lenny Rachitsky, a former product lead and head of consumer supply growth at Airbnb, and Nels Gilbreth, former Head of Global Revenue Strategy at Eventbrite.

It’s almost the end of Q3, which means annual (and quarterly) planning is just around the corner. If you’re like most people, this sentence just filled you with dread.

We’ve been through dozens of planning cycles after spending 10 years at Eventbrite and seven years at Airbnb, so we’ve seen firsthand how messy and challenging it can be. Sometimes we were still working on our annual plan — three months into the year. Other times a half-assed plan was rushed through approvals, only to be abandoned entirely after only six months. For most of us, by the time planning ends we’re left with bruised egos, misaligned plans, and a lack of buy-in.

Could Climate Change Really End the World?

End Times

Species are going extinct and the climate is warming rapidly — yet at least materially, humans are doing better than ever. Welcome to the environmentalist’s paradox.

Bryan Walsh Aug 16 · 7 min read

Photo: Josh Edelson / AFP / Getty Images

Asteroids, supervolcanoes, nuclear war, climate change, engineered viruses, artificial intelligence, and even aliens — the end may be closer than you think. For the next two weeks, OneZero will be featuring essays drawn from editor Bryan Walsh’s forthcoming book End Times: A Brief Guide to the End of the World, which hits shelves on August 27 and is available for pre-order now, as well as pieces by other experts in the burgeoning field of existential risk. But we’re not helpless. It’s up to us to postpone the apocalypse.

New Productivity — Benedict Evans

We are in the middle of a wave of interesting new productivity software startups – there are dozens of companies that remix some combination of lists, tables, charts, tasks, notes, light-weight databases, forms, and some kind of collaboration, chat or information-sharing. All of these things are unbundling and rebundling spreadsheets, email and file shares. Instead of a flat grid of cells, a dumb list of files, and a dumb list of little text files (which is what email really is), we get some kind of richer canvas that mixes all of these together in ways that are native to the web and collaboration.

The Single Most Important Internal Email in the History of Amazon

I never planned to do a series of articles, but this write-up almost came as a natural follow-up to the post I wrote last week about Context over Control and the future of remote work. Last week I explored the ground rules of the future of work. Specifically, I talked about how and why the fundamental prerequisites of work have changed. Here I’m taking a step further and describing some of the literature behind today’s organizations’ communication systems. What they’re made of, why they can be so impactful in today’s organizations, and how they’re related to the concept of remote working.

Five years of home office – a recap

TLDR; Read how I cope with working remote.

As it is en-vogue nowadays to talk about remote working and one’s

experiences, I thought I am gonna join the flock.

This does not mean that this resembles anyone else’s experiences, but I

still think there are some tidbits worth sharing in here.

I joined Elastic five years ago without any prior

experience in remote working.