I work on a small dev team. A team member recently left. My boss is lenient about committing our repos. ex co worker didn't commit his code and instead just left his code on a zip drive. Today I had to resolve nine months of conflicts and basically throw out all the work this guy had done.

  • 2
    The fuck wsd that guy thinking?! So nobody ever looked at his shit ever? He just coded without getting anything done?
  • 0
    @alexbrooklyn he would get stuff done. He just never checked stuff in. No one checked the repos. I knew he didn't commit very often, but I didn't know it was that bad until yesterday.

    He would basically get his stuff done, put his code on the release server, and then no one would check the repo for his commits. He was largely working on standalone web apps so his code would just go directly into prod, unless he was bug fixing his own code.
  • 1
    @vomitmachine And this why production should only ever be touched by the operations team (or whoever acts as operations) and all code should be released using automated tools that only work from the git repos.
  • 0
    @tankerkiller125 like I said, we're a small team. I've been trying to convince my boss to convince his boss that azure is the correct way to go. But it's hard to justify for a three person team. And now cut that down to a two person team and it's even harder to justify. We're just making it work with the resources we have.
  • 1
    @vomitmachine No option to deploy Gitlab and use their CI stuff with some DevOps scripts?
  • 0
    @tankerkiller125 yes and no, since we're a pretty small team we can do small solutions like that. However, we have a lot of work on our shoulders and keep busy pretty much 100% of the day and unfortunately barely have time to refine our own processes. I know a tiny tiny bit about devops stuff, enough to manage our repositories, but not enough to write a full pipeline.

    What also makes it difficult is that before now, is that my boss wasn't working in the got repo until this week. He was working in a separate tfs repo, and now I'll have to figure out how to merge his tfs repo and the git repo which has all of our projects in it. Which, I don't like the design of, I'd like to switch up the design so that our common libraries have smaller repos and are more managed so we have more granular control.

    I'm fairly certain my boss is looking for a job currently. Which is the only reason why I'm sticking around this place. Which would leave me as the de facto decision maker for these things.
  • 1
    @vomitmachine It's not as fun as you think being the sole person... My current/former boss (company division split) was the sole guy for a long time in IT and he was reaching the end of his rope and completely burned out until I got hired and started to take things off his shoulder.

    If you work well with stress and long work days you might be OK, but otherwise it will get to you and you probably will burn out at some point. Worse if you make a bad decision everything is on you and everyone knows who to blame even if you follow a blameless model.
  • 0
    @tankerkiller125 I was the sole person at another company. You're right, long days, a lot of responsibility. It's not far from what I'm doing right now.

    I'm currently under the guise right now that I'll be able to get other programmers with me and I'll be able to be the senior, but I suppose that's the best case scenario. Worst case scenario is I get burnt out and can't deal with the stress anymore.
Add Comment