I'm launching the London Observability Engineering, and I’m scheduling speakers and topics right now, so if you have something to share about Observability, I'd love to speak to you!
Here are a few topics I'm thinking of covering:
Next-gen instrumentation with eBPF & OpenTelemetry, GenAI in Observability, implementing observability for legacy systems, API observability, and data observability.
The reality is that RPA, AI, ML, etc ... are still years away when it comes to the industrial sectors (e.g. manufacturing, energy, oil & gas, etc).
Sure there are many PoCs, smaller projects, but in my experience, working on data centric projects with a few fortune 500 industrial companies, none of these technologies have been successfully implemented in production.
Perhaps for some back office & business-level applications, but certainly not for any production related use-cases (e.g. predictive maintenance).
My take is that RPA by itself is useful as most big companies have mind blowingly manual processes in their back offices (or even worse they don't have mapped their processes).
The combination of RPA with AI/ML, usually called "Intelligent Process Automation" is merely dropping some OCR or NLP engine here and there to help in points of the workflow when there is no other possiblity other than some person reading a document and trying to come up with the next step. Calling this "AI" is a stretch.
The hardest part of successful RPA implementation IMHO is in not automating stupidity.
It’s too easy to send EY or whoever in to replace some god awful process by “Larry in AP” with a “bot” that just replicated what he does - no matter how pointless any step might be.
The moment I read the news of the acquisition I took off my Fitbit Charge HR2 (it was my second Fitbit device) and I deleted my Fitbit account. I have no illusions this will change anything and I did it entirely on principle.
I’ll probably get an Apple Watch but I’d prefer something eink and “dumber” with just clock, heartrate, steps, stairs and GPS, no accounts and no forced uploading to their servers would be ideal.
I love the FitBit device though. If there’s some opensource way to keep using it without Google being involved I’ll probably try that.
I switched to a Garmin Instinct a few months ago. My Charge 2 died and I wanted something with GPS and decent battery life. I charge my watch every 10ish days (I pair it with my phone only after an activity to see the details, not otherwise).
I personally find it great that it has a rugged screen with buttons instead of fancier things like a touchscreen, payment options etc.
Kinda expensive and not very open for an eval kit. The only somewhat difficult part is implementing the pulse oximetry signal chain and analysis software. Everything else is basic integration.
My wife switched over to a Garmin fitness tracker. She'd been having technical issues with her old Fitbit anyway, but the Google acquisition made it so she didn't even consider a new Fitbit as a replacement.
I didn't stop using it, but I made a different decision about what watch to purchase because of it, because a) divesting my health data from Google's vacuum seemed wise and b) I no longer trust Google to support hardware/services long term.
I switched to an Apple Watch last year when I got one for my mom because of the fall detection, so that I could know how to use it and support her. The rest of my family still has Fitbits and I still prefer Fitbit for what it does (and the battery life). That said, in the wake of this announcement two people just got an Apple Watch ordered as an upcoming birthday gift because I don't think having Fitbits is a good idea anymore.
Google is not a company that respects their users. It's that simple. Apple doesn't respect developers, but it does respect users. Google respects neither. I'd say the current situation in tech is not especially positive for users generally, but having a product tied to Google, Facebook, or Amazon would be your worst case scenario, and I'm actively trying to excise these products from my life.
Not yet, but it looks like I will. I had no idea of the acquisition till this post. A shame because I think the Fitbit is fantastic and my current device is years old.
I'm launching the London Observability Engineering, and I’m scheduling speakers and topics right now, so if you have something to share about Observability, I'd love to speak to you!
Here are a few topics I'm thinking of covering:
Next-gen instrumentation with eBPF & OpenTelemetry, GenAI in Observability, implementing observability for legacy systems, API observability, and data observability.
What else should we talk about?