Miguel Palhas

The worst part of ESP32 home automation?

Every 2 hours of progress followed by a week waiting for that one AliExpress part I forgot I needed.

Patience is part of the build.

What I like straight out of the box from EverySmartHome:
– Quality case I can open without breaking anything
– Extra GPIO for whatever I want
– Standard, documented hardware
– Somehow skipped UK->EU customs (a first for me)

Already a strong start.

Just got my Everything Presence Sensor. Haven’t plugged it in yet, but shoutout to EverySmartHome for ticking all the boxes on open source home hardware.

Feels solid, well-designed, and built for people who actually want to understand and extend what they own.

Picking up #Elixir again lately.

Still love the language—but after a few years with #Rust, I’m realizing just how hardwired my brain is to strong types.

Everything feels slower without rust-analyzer's instant feedback.

Working with testnets sucks:

- No gas
- No cheatcodes
- Bad RPCs
- Can’t hide contracts

So we’re fixing that.

Speed hack: cut @ethui.bsky.social’s debug build times by 40% using mold linker + Nightly parallel frontend + cranelift.
Rust compile times are evolving fast!

YouTube video by Duct Tape A local first approach for web3 development

Gave a talk at @ethprague.bsky.social on building #Web3 with a local-first mindset using @ethui.bsky.social. It's now live on YouTube in case you want to check it out!

Happy to have been at @ethprague.bsky.social last week, showing how @ethui.bsky.social brings a local-first approach to #web3 development: faster feedback loops, no deploys, and real UI prototyping,

Don’t miss my talk tomorrow at 3:30 during @ethprague.bsky.social. Web3 dev made simpler, with @ethui.bsky.social .

YouTube video by ThePrimeTime Making A Game GOOD - The Standup EP 3

@cmuratori.bsky.social always delivers.
This one’s a deep dive into design thinking, complexity, and why we tend to overbuild systems: www.youtube.com/watch?v=nCxU...

“If it compiles, it works” is such a powerful thing in #Rust.
Picked up #Elixir again recently, and I really miss the Typestate pattern.

Don’t miss my talk on 29/05 at 11:30am during @ethprague.bsky.social.
Web3 dev made simpler, with @ethui.bsky.social.

Managed to speed up @ethui.bsky.social's from-scratch debug builds by 40% (1m20s → 50s).

The keys?
- Mold linker
- Nightly parallel-frontend
- Cranelift

Demystifying the North Korean Threat There’s more to the DPRK than just Lazarus Group.

Not your usual crypto read, but this one’s sharp:

First time with #Bevy this weekend.
Made a quick Space Invaders clone:
🛸 space-invaders.naps62.com

Give it a spin — good way to descompress after shipping code

Lately I’ve been diving deeper into game dev.
Unity/Godot/Unreal are the usual suspects—but writing games in pure ECS with Rust (via Bevy) just hits different.
It’s low-level, expressive, and kind of addictive.

@alchemyconf.com got me back into Elixir.
Forgot how nice the syntax feels — but wow, my brain is now fully conditioned to Rust's type feedback loop.
Strong types are addictive.

If Ethereum development is to scale in 2025, it needs:

- More powerful local tooling
- Trustless Safe UIs
- Less reliance on public testnets
- Local-friendly subgraph alternatives
- A modern OSS contract-verifier

What would you add?

I’ll be at @ethprague.bsky.social on May 27, talking about @ethui.bsky.social. See you there?

#ETHPrague #ethui

Most wallets can’t handle anvil rollbacks or dev-only cheat codes. @ethui.bsky.social fixes that.

serde(default) would actually be a footgun for us.

because it means json files with missing fields would potentially match multiple versions of the enum (since it'd just fallback to default).

setting a fixed version number ensured each file has an explicit non-ambiguous version number

This is what we went with, but the cherry on top was to be able to ensure versioning through type-safety (i.e.: prevent us from changing the struct and forgetting to update version number, which would break on user's side)

not quite all the way, but this helped a lot: github.com/ethui/ethui/...

Bevy (rust’s game engine) initial examples seems deceptively simple, but there’s some truly great engineering behind it. Their ECS implementation is elegant to a level I didn’t expect.

Any good patterns out there for handling data migrations in desktop Rust apps? I want to update structs but automatically migrate and deserialize any prior data users may have in their FS.

Recently integrated the actor model into @ethui.bsky.social using the kameo crate. While #Elixir is still king here, Rust keeps impressing me with how it balances great developer patterns and runtime performance.

The @ethui.bsky.social's codebase is over 2 years old now. Every time I look at an older snippet, I can clearly see how much my Rust skills have improved. Past-me, we need to talk.

The new @ethui.bsky.social 1.14.0 update improves the JSON view for message signing. JSON content is now displayed in a more structured, easy-to-read format. Learn more: ethui.dev/blog/ethui-1...

Bevy’s query system feels like magic to me. No lifetimes, pure types, dependency-injection for free.

#Rust and #TypeScript are still my go-to solutions for almost everything these days. Rust for safety & performance, TS for productivity & ecosystem. The perfect duo? Maybe.

With @ethui.bsky.social, manage unlimited wallets side by side. Test and prod, peacefully coexisting—no more juggling profiles.