257 karma · joined June 20, 2023
Every single thread or post about anything adjacent to cars or public transportation devolves into this. There is hardly any nuance, little effort is made to respond in good faith, and there are insults and insinuations thrown around all the time. Anyone perceived as being on the “wrong side” is instantly given a label and mocked. You don’t even have to be overzealous about it. Even the most benign comment will have someone piling on usually. “Just one more bus bro”
Or maybe they think that the proposed solutions are worse than the problem.
All of it is a scam. I head these people off early if I see them walking around my neighborhood.
One of the biggest problems is that they didn’t try to actually interface with other teams to sell why Backstage might be something they want to use. Instead they got it 20% populated with low hanging fruit, and the rest of the company is blissfully unaware that it even exists.
In any case thanks, this will help me in the future I think.
How can you say this nonsense so uncritically?
To your point, I would say that it’s “easy” rather than strictly helpful. There is a plugin I maintain internally that can be invoked by calling “helm <thing>” if I go through the necessary steps to have it installable by the helm plugin command. Under the hood it’s just a small binary that you can put in your $PATH and it’ll work fine, but there are tons of developers and PMs and other people at the company who don’t know what a path variable is, or how to set it, or what a terminal is, or what shell they’re running, or who know that they can do “helm X” and “helm Y”, so why not “helm Z” for my plugin, etc … It would be a hell of a lot easier to just ship the raw executable, but to those people and execs and mangers and stuff, it looks good if I can show it off next to the native stuff.
Whenever I have to help users with it, I notice that nearly everyone uses it with helm and not calling by the binary directly. It just comes down to the fact that presentation and perceived ease of use counts for a lot when people evaluate whether they want to make a tool part of their workflow.
Agreed about Orion, I keep it around and update it and try it out every now and again but I don’t think the experience is there yet.
> Educate yourself