Vendor case studies are useless. They all read the same: "We selected Ping for its robust security framework and scalable architecture." Zero technical details, zero real metrics.
Where do you find unfiltered, engineering-level details?
* Independent analyst deep dives (Gartner, Forrester) – but they're behind paywalls.
* Conference talks (Identiverse, KubeCon) – search the archives for "migration" or "implementation" talks.
* LinkedIn – find engineers at companies listed as "customers" and check their posts/projects.
* GitHub – search for `pingfederate` or `pingdirectory` in `docker-compose` or Helm chart issues. Real problems surface there.
What's your go-to source for actual architecture or migration pain points?
That GitHub trick is smart. I wouldn't have thought to look for problems in the actual config files.
Do you find that engineers on LinkedIn are generally open to talking about this stuff, or is it hit-or-miss? I worry about coming across like I'm fishing for proprietary details, when I'm just trying to understand the real snags.
I also look for older forum posts, like on Spiceworks or even Reddit, from a few years back. People seem more candid when the project is done and dusted, and they're not worried about their company's marketing team.
Good list. I find Gartner's free webinars and re-caps can sometimes give you a hint of the issues, even if the full report is locked. They often mention common "challenges" generically, which points you where to dig.
But my question: when you find those engineers on LinkedIn, how do you phrase the initial message? I always feel like I'm bothering them. Do you lead with the specific technical gap you're trying to fill?
Totally agree on the LinkedIn approach, it's my go-to. The key is making it quick and mutual.
I always lead with the specific gap. Something like: "Hi [Name], saw your experience with [Tech] at [Company]. I'm evaluating it and hit a wall on [specific detail, e.g., scaling the session store]. Any chance you'd be open to a quick chat about what you learned?"
Works because it's precise, shows you've done homework, and respects their time. It frames it as a peer question, not a sales probe.
Sometimes I'll even mention the GitHub issue or conference talk that led me to them. Makes it feel like a continuation of a public convo.
Let's build better workflows.