Palmetto Technology Group (PTG)’s Post

Blameless was founded over five years ago, but we believe our mission of bringing reliability excellence to everyone matters more today than ever before! Learn about how we're tackling the challenges of 2023 and beyond in this new blog post: https://lnkd.in/gwJ-Vmxu

"A well defined problem is half solved" - Charles Kettering While working on a personal project and weighing the pros/cons of different solutions I had to stop my self and fix some of my bullet points. In one of the cons sections I had written "not very dynamic". While true it completely missed the point of why I was chalking this up as a con to the solution. I rewrote that same con as "Since tests are likely to use the same endpoint over and over again there needs to be a way to identify that a specific request maps to a specific response independent of the test thats running. Uploading a single manifest before any tests doesn't support this common use case." One of those cons is half-solved...the other is not.

We are told to try to avoid assumptions, so we aren’t a butt. But not all assumptions are created equal. Some assumptions can be helpful. Here are seven assumptions that are good for you and you should start using immediately. Like this one… ASSUME THERE IS SOMEONE ON THE ELEVATOR WAITING TO GET OFF BEFORE YOU GET ON. The number of times I almost get plowed over because the person waiting to get on the elevator doesn’t pause to see if someone is getting off is frightening. It’s a 50/50 proposition that someone is waiting. You can wait five seconds until the door fully opens to see if someone needs to get out. Waiting five seconds will save a potential collision and embarrassment, but waiting five seconds will not save you from being noticeably late. Assuming this will make you appear more courteous. Whole list in first comment.

And here are the complete parts following the second operation.

🤝 Everyone at incident.io talks to customers 🤝 No matter their role, everyone is encouraged to build relationships and help out whenever they can! And before our new VP of Engineering, Norberto Lopes, joined the team, he witnessed this firsthand. As a customer of ours, he quickly learned that here, "talk to the customer" isn't just something we say, it's a core part of how we operate! Check out the full conversation to learn why this was one of the major reasons he ultimately decided to join incident.io 👇

The life of an IT pro summed up in three simple steps! When things go awry, we know how to bring them back on track. We could call this the art of IT troubleshooting. 😄💡 Do you agree with this?

Smooth installation, minimal power-off time, and top-notch professionalism- that’s what we’re all about.

I just posted my first short story on Medium! Check out Part 1 if you're interested.

Professionalism in all aspects - If you want reliability, rely on Lawrence.

To give you an idea of all the work needed BEFORE we actually get to building a solution. It ain´t simple, but it´s worth it.