Automations are like magic to end-users. They inexplicably make life easier.
But for the admins who build them, they can feel closer to rocket science. So it’s no wonder that some orgs take a set-it-and-forget-it approach. Why fix what isn’t broken?
But you never want to wait for something to break to get your attention. Crashed automations can cost your org – if not financially, then at least in data quality or time. (p.s. This is also true for integrations, which are even more delicate since they require third-party access to your data!)
Gang, I think it’s safe to say: this is not your typical summer.
Coronavirus continues to run rampant in the country (if you’re in the US). We’re still somewhat in a lockdown, and things are a little chaotic!
Still, I’ve always found summer to be the best time to slow down and get organized. That’s especially true when it comes to the database: this is when I begin wrapping my head around all the projects I keep putting off!
You ever find yourself trying to explain something technical to someone, and feeling as if you’re speaking another language?
Good. So it’s not just me.
Being in a technical role, and the only person who understands some parts of that tech, means I get the job of explaining to people why things work the way they do. I’m a nerd about bringing people into my work, so I’m happy to do it.