Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Japanese watch maker Tokyoflash has a reputation for its head-turning and uber-cool designs. Its latest incarnation however goes beyond the purely aesthetic and serves a more practical purpose – helping you determine when you’ve had one too many Sake.
Tokyoflash have taken their Kisai watch and added a breathalyser to it, giving it the name Intoxicated. The watch, which the Japanese company is offering for $99 in its launch promotion, can be recharged through a USB port, and just in case you are just a little bit tipsy and happen to drop it in your drink is water resistant to 100 feet.
As well as the watch facia turning a different colour when you blow into the breathalyser – green when you’re sober and red when you’re blind drunk – it features a built in reaction test. This sobriety game tests your hand-eye coordination, requiring the user to try and stop a moving line smack-bang in the middle of a target.
We certainly don’t suggest you use the Kisai Intoxicated to determine your ability to drive – zero alcohol is the only safe level – but you might use it to decide whether you’re in a fit state to send that late night email to your boss complaining about your pay and working conditions.
Email and social sobriety tests are not new. Google Labs launched Mail Goggles to help users avoid those late-night “regrettable” emails, requiring users to answer maths questions before the email is sent.
In a similar vein the Social Media Sobriety Test, a Google Chrome and Firefox extension locks down your social media accounts – such as Facebook and Twitter – between certain “after-hours” which means that in order to use those sites you need to pass various field tests such as using your mouse to follow an object round your screen.
James Barnes, StatusCake.com
James Barnes
Share this
More from StatusCake
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026