226
hell
6y

I introduced git with hope that our team gets better

I introduced trello in hope that our team get better

I introduced gitlab in hope our team gets better

I introduced scrum in hope our team gets better

I'm losing hope...

Comments
  • 77
    Time to introduce middle finger
  • 16
    @BindView hahahaha yeah.. Or resignation letter
  • 15
    Time to introduce new employees!
  • 31
    you need to introduce yourself to your next employer
  • 7
    Maybe you should stop cargo culting technology and find the real issues?
  • 3
    Look at the first line of agile manifesto. Than you will see what you need to introduce/replace...
  • 3
    Next up:

    Kanban
  • 2
    @hjk101 yeah, good point
  • 2
    Introduce the concept of hope to your team this time.
  • 0
    Wait, wut? No Git? What do you use for version control? Just code in production? Pass around a USB flash drive as a central code base? Dropbox with file names like 20180207_file.txt? 🤦🏽‍♂️
  • 2
    @eeee first line of rant is about git...
  • 0
    @azous so you actually succeeded? I thought your rant was sarcastic, so you didn't succeed in starting to use it. Nevertheless, since you introduced Git, where was the code base before that?
  • 1
    @eeee yeah, hit was a "success" , at least they can "pull,push,commit" after 2 fucking years.

    We used to update by ftp , lol, it changed as soon as I joined the team.
  • 1
    Sounds awefully familiar to me. Takes so much time if you have to lecture every single one of them so the workflow benefits...

    Are they just incompetent or do they lack motivation to work?
  • 1
    @Ederbit lol, I guess both :/

    @Unipheas yeah, we are on the same boat here, been paying 2 months for YouTrack already, set up a test environment on our servers and they are fucking waiting for me to "teach" them how to use it despite the fact that I already did!
  • 2
    I find if onboarding tools isn't the immediate solution, you'll have to stop, take a step back, restart and rework the current mindset so that the workplace culture can catch up to support those additional tools; otherwise their introduction feels like extra work that they didn't have to do before.

    I got a lot of "everything was working fine before" or "this seems like unnecessary extra steps" when I started at my work place and had a different workflow pipeline.

    Have to host lunch n' learns to help change the mindset, like that version control isn't extra work but something you bake in to workflow process, and that it's not a hassle, it saves your ass.

    I learned it's really how you market the tools to a team.
  • 0
    Have you ever heard of “shinning the turd” 💩?
Add Comment