3 ms·

It seems to lowly-old me that you come-across as possibly tired of exceeding your BS/reward ratio. If so, a vacation/sabbatical could be needed if it's a tempo

It seems to lowly-old me that you come-across as possibly tired of exceeding your BS/reward ratio. If so, a vacation/sabbatical could be needed if it's a temporary thing. If it's permanent, finding a promising startup with a defensible business model to be a first-round employee might be a better option. They skew towards hiring A-players (not always, but usually). If staying for some time: Popularity != engineering soundness. Fools and novices are allergic to simple, especially if they've never built solid anything at scale or worry about work being taken from them. It doesn't sound a collaborative/consensus environment either, maybe a toxic, religious, adversarial one containing outsized egos who want their solutions advanced because it's job security for them, and anything else gets in their way. You could try asking them what are their specific objection(s) to seek their honest feedback. Using self-deprecation can be helpful too. Personally, I don't use Go anymore for the past 2-3 years. I prefer Rust for speed, Haskell for generality and Crystal for rapid prototyping. I'll use anything to get a job done, because real customer problems and real solutions are rarely perfectly-crated masterpieces in your favorite tech stack. IMHO, Go got too popular, fashionable and full of needy noobs who dragged the ecosystem down. (Ironically, I remember telling a head-hunter in about 2011 he was dead wrong and to never call again since he arrogantly proclaimed Go was going "nowhere.") I hate K8s and systemd because they're overkill, "emperor's new clothes" amoeba-ware that are poorly-conceived, poorly-executed and of marginal benefit compared to what they replaced. It's important that "new" projects crammed down our throats because of celebrity and techno-fashionabilism not be easily compared to today's latest flavor Javascript library. Only after exhausting attempts to fix deficiencies in existing solutions, then deeply consider/seek feedback about the impacts, UX, behavior and interop of proposal through project-based RFCs. That's my 2c from ~25 years being a code monkey punching buttons on glowing boxes; and maybe I'll accidentally write Shakespeare one of these days. ;-)

ThrowAwayOG 7y ago
> It seems to lowly-old me that you come-across as possibly tired of exceeding your BS/reward ratio. I think you nailed it. > You could try asking them what are their specific objection(s) to seek their honest feedback. "It won't support our needs in 1-5 years" (The projects in question are not supporting our needs for the next 0-12 months). > Using self-deprecation can be helpful too. Agreed, but in the current case it seems to embolden those who do not wish to discuss alternatives. Which is another problem I neglected in my post: The mere suggestion of alternative approaches threatens our 10X egos, and communications tend to degrade at that point. Sometimes the solution - for the mental health of all involve - is to step back and let bad decisions play out, while working on independent tasks. I consider it bad leadership, but there is also something to choosing one's battles. A sabbatical does indeed sound like a good way to reset. After all this time of never taking a break by choice, its definitely something I have to figure out: How to truly disconnect without spending everyday planning what happens after the sabbatical is complete.

ThrowAwayOG 7y ago

> It seems to lowly-old me that you come-across as possibly tired of exceeding your BS/reward ratio. I think you nailed it. > You could try asking them what are their specific objection(s) to seek their honest feedback. "It won't support our needs in 1-5 years" (The projects in question are not supporting our needs for the next 0-12 months). > Using self-deprecation can be helpful too. Agreed, but in the current case it seems to embolden those who do not wish to discuss alternatives. Which is another problem I neglected in my post: The mere suggestion of alternative approaches threatens our 10X egos, and communications tend to degrade at that point. Sometimes the solution - for the mental health of all involve - is to step back and let bad decisions play out, while working on independent tasks. I consider it bad leadership, but there is also something to choosing one's battles. A sabbatical does indeed sound like a good way to reset. After all this time of never taking a break by choice, its definitely something I have to figure out: How to truly disconnect without spending everyday planning what happens after the sabbatical is complete.