When I set out to fix my broken water temperature gauge in my 1988 Ford Bronco II, I didn't realize the journey it would set me on.
I knew that I wanted to do a little more than just replace the gauge. I wanted to connect it to the internet. I have made plenty of little projects that proved I could read a sensor or blink an LED, and those were fun, but they weren't really teaching me much beyond the basics. So for this project, I wanted to take a more intense approach.
I wanted it to be more than just a pet project — I wanted to learn the hard lessons about production-ready IoT software. I wanted to apply many of the same DevOps best practices I've been doing day-in and day-out in my role at Nebbia Technology: planning out features in a sane way, creating unit tests, using a continuous integration and continuous delivery pipeline, monitoring, and doing all of this with a production-first mindset.
I've found that DevOps practices like these have made other types of software development much faster and more predictable, and therefore easier and more enjoyable. I was looking to apply them to the fresh challenges of developing for the Internet of Things, and I wanted to do it so that I could accomplish a seemingly tiny, simple goal: know if my 30 year old Ford was going to overheat in real time, and then save that data to the cloud.
And I did it. I connected my 1988 Ford Bronco II to the internet, and did so in a way that I'm not entirely embarrassed about. Join me as I tell my story about the trials, tribulations, and most importantly, the lessons I learned in connecting a crusty old truck to the internet.