Mainly a senior iOS engineer, but love to dabble in web development and robotics/embedded-systems in my spare time.
Father to four amazing children, and husband to a beautiful wife.
Checkout my stuff:
lumley.io
github.com/will-lumley/
| đ Website | https://lumley.io |
| đť Github | http://github.com/will-lumley/ |
My garage remote died a while back, so I rebuilt the opener using an ESP32, a relay module, and HomeSpan (an open-source HomeKit Accessory Protocol implementation).
No vendor cloud, no subscriptions, no locked-down âsmartâ hardware. Just a simple, local, secure garage controller that works perfectly with HomeKit.
Wrote up the full build + wiring + firmware details here:
https://lumley.io/blogs/smart-garage/
A few weeks ago, my garage remote died. Completely. No LED, no click, no signs of life even after replacing the battery. Normally, this would be annoying enough, but my house relies heavily on HomeKit. Lights, blinds, cameras, fans - everything responds to Siri⌠except the garage. And now, even the dumb remote wasnât working. But instead of buying a $90 replacement remote or a $250 HomeKit-enabled garage opener, I had a different thought:
Fatbobmanâs Swift Weekly #0107 is out!
A Trip to the Apple Store for Repairs
đĽ Hot Reloading SwiftUI Apps
đ Mobile Testing Strategies
đ¤ Automate with Swift Subprocess
đ˘ AsyncCombine
and more...
https://weekly.fatbobman.com/p/fatbobmans-swift-weekly-0107
thank you to those who selflessly shared their wisdom with us: @danielchooper, Jinkai, @kharrison, Tjeerd in 't Veen, @JacobBartlett, Bruno Valente Pimentel, Alfonso Tarallo, @mattiem and @wlumley
đ New blog post!
AsyncCombine: Because Async Code Shouldnât Be Ugly
I built AsyncCombine to bring back Combineâs expressive syntax - sink, assign, CombineLatest, and more - but powered by Swift Concurrency.
Why? Because observing an @Observable classâs properties from a SwiftUI view is easy - but doing the same from another ViewModel got way harder and messier once @Published disappeared.
Check out my article that goes over how I solved it.
When Swift first introduced Combine, I loved it. The syntax was expressive, pipelines were easy to follow, and @Published made state changes feel almost magical. But as Apple pushed us toward Swift Concurrency, I decided to bite the bullet and migrate one of my apps away from Combine. The migration worked; async/await is powerful, predictable, and in many ways simpler. But I quickly noticed something, parts of my code just werenât as easy to read anymore. A neat Combine one-liner became a few clunky async calls. And to make things worse, I couldnât rely on @Published to observe changes between view models anymore.
Apple to Europe: âYour laws are bad for us, therefore we are withholding unrelated features from your citizens and do everything possible to lobby against your laws.â
Apple in the USA: âWe only follow the laws and orders of our authoritarian government, there is nothing we can do against it.â
This is the whole of academia in a nutshell.
Slightly unhinged and very incorrect, but probably still useful
actor: lock
isolation: which specific lock
nonisolated: no lock
Sendable: thread safe
non-Sendable: not thread safe
async: I might wait
await: I'm waiting, maybe just for a lock
Task: thread
compiler: pedantic, paranoid code reviewer
donni saphire
fatbobmanďźä¸ĺĄčĺďź
Holger Krupp
Dare Obasanjo
Dave Dawkins (D. Harrigon)
Matt Massicotte
stuxâĄď¸
uwu1ba