3 ms·
I'm just one person, and I'm probably not even the target demographic, but if you're taking feedback: I full-on laughed out loud reading your landing page for
by catapart 2y ago
I'm just one person, and I'm probably not even the target demographic, but if you're taking feedback:
I full-on laughed out loud reading your landing page for the "old way"/"new way" comparison.
It reads, to me, like "old way: easy to follow, if cumbersome, flowchart", "new way: 4 separate abstract drawings that are actually impossible to follow and do not imply any specific process is occurring."
Obviously, I'm probably in the minority here. Just some food for thought, if you're interested in that kind of thing.
- deleted 2y ago[deleted]
- JOnAgain 2y agoYou’re not alone. I don’t get the contrast either.
- localfirst 2y agono its what i thought too and i felt like this is a tough problem especially when you get into enterprise space with a dozen heterogeneous stacks and outdated vendor APIs if it was this easy then we would see a ton of layoffs but you can't because all these individual pieces and their idiosyncrasies cannot be streamlined and its cheaper to just have human interfaces. So many cases I've seen where "hey this doesn't work the way it should because the vendor hired bunch of Indians who are paid by the hour didn't bother to spellcheck or use proper patterns because why would they when you pay them to bill more hours" We'll see more and more result of negligent managers throwing third world labor at critical systems and its impact on the economy down the road. This is something only fixable by other humans and not any AI or SaaS
- bolei1007 2y agoThanks for the feedback! It's harsh but very valuable!