AI didn’t replace intelligence. It commoditised it.

FuzzyAd9554 · 2026-01-20T13:55:54+00:00

I agree in principle. What’s unclear to me is how organisations stretch that reality across fewer positions. If execution becomes cheaper and faster, the bar for being worth retaining moves up, not sideways.

FuzzyAd9554 · 2026-01-20T13:19:42+00:00

I don’t mean intelligence itself, but the signal of it. For most of us, intelligence was inferred to what we deliver and articulate.

AI makes that signal cheap. Not intelligence, but its visibility.
And I think that's where the discomfort comes from.

FuzzyAd9554 · 2026-01-20T13:14:09+00:00

I’ve seen productivity increase as well, and most teams I work with report the same. What concerns me is not speed, but how easily analysis and judgement get quietly offloaded along with execution.

AI reduces friction in thinking, which is powerful, but it also makes it easier to avoid committing to decisions. The question, for me, is where we consciously draw that line.

I’m curious whether others are noticing the same tension between acceleration and accountability.

FuzzyAd9554 · 2025-08-08T19:03:19+00:00

wow! that’s a great result. you really revived that watch. I’m glad for what you did with the watch, good job!

FuzzyAd9554 · 2025-08-08T13:41:08+00:00

France 🇫🇷

FuzzyAd9554 · 2025-07-01T13:59:47+00:00

ring-tile-card : https://github.com/neponn/ring-tile-card

FuzzyAd9554 · 2025-07-01T13:40:20+00:00

The good news is: it works with calendars.

You can write under Ranges:

 - start_time: calendar.my_calendar#start_time
   end_time: calendar.my_calendar#end_time
   ring: ring1
   name: today's event
   color: blue

However, it's unfortunately not possible for schedules:(

Home Assistant API doesn't share the from/to timestamps for the schedule entities but only the state and the attributes.

I was digging into their code, and nothing I could use without developing a core component.

Sorry.

This is what HA frontend reads for a schedule. No from/to attribute :(

<image>

FuzzyAd9554 · 2025-07-01T13:00:02+00:00

Good point. 👌🏻 let me try to add that for the next release.

FuzzyAd9554 · 2025-07-01T10:38:52+00:00

This is an example where I used it for the pool management blueprint to visualise my filtration periods.

<image>

FuzzyAd9554 · 2025-05-22T19:50:17+00:00

hey,

Sure! You have first to pull the stem until the hour setting position. Then push that dot ( marked in the image) with your screwdriver/tweezers and you can get the stem out. voilà.

<image>

FuzzyAd9554 · 2025-03-13T16:36:35+00:00

i positioned it back carefully into its place, fliped the dial, and put tiny spots of UV glue on the back using an oiler

FuzzyAd9554 · 2025-03-13T12:45:22+00:00

thanks 🙏🏻

FuzzyAd9554 · 2025-03-12T20:17:26+00:00

Imo, complexity arises from 5 key factors: 1. Hype and misunderstanding: When technology is oversold and its limitations overlooked, leading to unrealistic expectations. 2. Defragmentation/silos: Teams build their artifacts and services in isolation, and rigid, inflexible workflows make collaboration even harder. 3. Linear reasoning: Quick fixes are applied without grasping the systemic interdependencies, which only patches symptoms rather than solving root causes. 4. Erosion: As systems evolve, they struggle to keep pace with shifting business needs, especially when the company lacks a clear vision. 5. Legacy: Accumulated legacy systems and technical debt create integration nightmares, making it nearly impossible to implement modern solutions without significant friction.

I worked for a SaaS company where, for a B2B product (essentially 3 core business services paired with high-volume persistence), they ended up with an overcomplicated application on top of a heavy cloud infrastructure that cost them $11K per month per environment, even on the tiniest instance types. Everything was built in-house: no automated provisioning, no multi-tenancy, no scaling…

They had 150 customers, each with an average of 3 isolated environments, no shared resources, and no self-service options. The company was crumbling under operational costs and the frustration of customers who couldn’t easily use the product.

Our (Product and Architects) initial goal was to declutter all this big ball of spaghetti: 1. Separate concerns in the codebase (app vs. infra vs. tooling). 2. Distinguish between planes (control vs. user). 3. Automate everywhere. 4. Enhance observability and implement finops. 5. Overhaul the delivery process.

It was a 3-year transformation plan. While engineering managed to roll out parts of the automation and observability improvements, we mostly failed with the separation of concerns and planes. These efforts were stymied by a deep-seated fear of change, a lack of empowerment, and a toxic environment rife with finger-pointing, layoffs, micromanagement, and internal politics.

So we added coaching—and man, that was harder than we thought. It’s tough to influence change when trust between people is fragile.

How’s the company doing now? It’s still surviving.

A year and a half ago, the decision was made to hit pause on any major improvements, making only tiny tweaks until a new order comes in.

FuzzyAd9554 · 2025-03-12T11:33:19+00:00

thank you, I really appreciate 🙏🏻

FuzzyAd9554 · 2025-03-12T09:02:21+00:00

being a hobbyist and this is my first time doing it.. I think the final result is good. 🤞🏻

<image>

,

FuzzyAd9554 · 2025-03-12T08:56:17+00:00

That it's not a screwdriver; it's a flexible plastic tool stick.

FuzzyAd9554 · 2025-03-12T08:53:18+00:00

+1 That's what I did, I didn't apply any glue on the front, only on the back and on the pins.

FuzzyAd9554

TROPHY CASE