Code Story episode
S3 E16: The Enterprise IoT Blueprint: Scaling Smart Building Data Pipelines with Microshare’s Ron Rock
Nov 3, 2020 · Season 3 · Episode 16 · 35 min
Sensors on Steriods
Born and raised in Philly, Ron Rock put himself through college, working at Denny's as a midnight chef. He is a life long entrepreneur, and started his first business when he was in his 20's. He's married with 3 adult children, of whom he is very proud of. He spends a lot of time restoring old furniture and cars. In fact, when he was a kid, he was the guy all his friends brought their 10 speed bikes to to be fixed - which of course, changed to cars as they got older. Basically, he has always been building things either at work or at home.
Post his other successful startups, one of which he sold to Accenture, he was intrigued by the space at the intersection of cloud and mobile, in the enterprise. He set out to combine disparate data sources that employees were required to use - digital signatures, smartphones, salesforce - after enterprises spent the last many years having locked everything down.
When he started to pursue this, he noticed that iOt sensors were going to put his core mission on steroids. Four years ago, his company pivoted to be solely focused on iOt & commercial real estate - to create smart, clean, safe - and connected - facilities.
This is the creation story of Microshare.
Sponsors
Wyld Gallery
Podcorn
Links
https://www.microshare.io/https://www.linkedin.com/in/ronald-rock-2b52499/https://kitcaster.com/ron-rock/
Leave us a review on Apple Podcasts
Amazing tools we use:
If you want the best publishing platform for your podcast, with amazing support & people - use Transistor.fmWant to record your remote interviews with class? Then, you need to use Squadcast.Code Story uses the 1-click product ClipGain, sign up now to get 3hrs of podcast processing time FREE
More episodes
Keep listening
Topics
Explore related conversations
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.
Scaling an engineering team from 5 to 50
How to scale a startup engineering team from 5 to 50 people: when to add managers, how communication breaks, what process to add at each size, and what to leave alone.
Startup engineering team structure that actually ships
How to structure a startup engineering team: the models that work at 5, 15 and 40 engineers, how to split teams, and the org mistakes that quietly slow delivery.