16

tl;dr - My company makes me pass around code over email. Is this normal?

How we fix bugs at my company.
1. Simulate bug in dev env (ok, cool)
2. Get the required code from svn and make changes locally (so far, so good)
3. Deploy changes in dev env and test (yeah!)
4. Take screenshots of fix in action along with the files you've changed and mail it to the respective leads (really? send code via mail?)
5. Keep changing your fix based on feedback and keep repeating above steps (what!)
6. Once approval mail comes, check-in your code in the svn branch for deployment and testing in the test env (QA team)

My question to you fine folks is, is this normal? Is this how most companies work? Passing around code over e-mail? Where the different versions of your fix are just attachments in emails. Or have I committed a sin by being a part of this heinous act?

Comments
  • 5
    Yeah that's fucked up. My manager won't use Git and only does code review via FTP to production. Occasionally he'll amend live code directly on the server and we have to download his version and add it back to the repo (assuming we notice). It's not uncommon for him to amend generated files. It's very rare that any of his changes are useful.
  • 1
    Just bcc competition 🤔🦖
  • 4
    Or.
    Ditch SVN for git and use feature/bugfix branches.
    Like any sane dev team.
  • 0
    @Root sane dev team, who dat?
  • 2
    @karma No idea.
    I've never met one.
  • 1
    @Root if u do, loop me in 😎🤣
  • 2
    It's ass-covering. Usually because someone high up the company's food chain isn't a programmer, let alone an actual human being:

    "Wait -- that bugfix for that one specific bug didn't fix ALL bugs?!?!?! Who authorized this?!?!?!? All vacations are canceled!!!! No personal days!!!!! Heads will roll!!!!"
  • 1
    For me it's very simple: fix the bug in the live server through SFTP.

    😨
  • 1
    @AnonymousDev wearing a pink sombrero
Add Comment