4 ms·

I've been that guy. & yeah, found greener pastures a couple years later No regrets, canopy was an absolute pleasure to use https://lefthandedgoat.github.io/can

• spywaregorilla 5y ago
  > No regrets The victim of this pattern is not you
  • __s 5y ago
    I have a conscience, if I did anyone wrong, I'd regret it; the code I left behind has stood on its own
  • blacktriangle 5y ago
    Consulting and working full time have the same problem, you need to program for the customer, not for yourself. If you work with people who are unwilling and/or unable to learn a tool, then DO NOT use that tool. It doesn't matter how much better it makes your life, you've taken a more or less functional organization and given them a bus factor of 1, where that 1 is you and clearly if you're so high on your tool you're willing to shove it down the orgs throat, you're probably looking to leave already.
    • jrsj 5y ago
      Doesn’t that sort of increase your own value to the organization though as well? It would vary based on the situation but it seems like this could sort of work to your advantage if you’re the only person who can reasonably work on something critical (and others can’t be bothered to learn)
      • blacktriangle 5y ago
        I guess, but I think that behavior falls under a dark pattern of employment. I'm not saying you can't introduce new ideas into your organization, but this is where the politics of development comes into play. You need to get buy-in from your team and management, otherwise you're intentionally hurting your organization.
      • evfanknitram 5y ago
        It also means when there's an outage due to X during christmas or whatever, then you're the only person who can reasonable work on it. Great work.
      • mjmahone17 5y ago
        Only if you can ensure no one ever replaces what you wrote with their own solution. You become critical in the short term, but also critical to the business to replace in the long term, in the same way that a vendor tripling their price often results in short term profits while customers transition off of them, leading to a long term decline in revenue.
      • mason55 5y ago
        I'd argue it increases your importance but decreases your value. You become a single point of failure for the org, so you're more important, but you're removing value from the org because you're making it more difficult to scale the organization.
      • majormajor 5y ago
        It's your bosses job to make sure there aren't single points of failures. If you try hard to become one, they might start trying hard to make you not one. You're now a bottleneck, after all. Some places have toxic cultures so that's the norm, but if you're fortunate to be at a better place, don't force their hand to go down that route! (There's also the aspect where if you're the only person who can do X, but now someone needs to do Y which will actually be ten times more valuable to the company than X, you've closed off that opportunity for yourself!)
• gagege 5y ago
  I was that guy too at one job. It was wonderful to work on a few F# projects, but I have no doubt they quickly went away after I left.
  • evfanknitram 5y ago
    I have been on the 'receiving' end of such persons actions. We had one guy who worked probably 50% of his time on using not F#, but another "nice" thing. It never worked well and he spent an incredible amount of time patching it and fixing issues with it. I threw it out the day after and replaced it with some older boring technology, and the problems just went away.
    • gagege 5y ago
      Bravo. Yeah, I learned my lesson.