Details
-
AboutDeveloper and Tech. Enthusiast!
-
LocationBangalore, India
Joined devRant on 5/13/2016
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
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?9 -
Step 1. Read posts about ads on devRant
Step 2. Become a supporter if you aren't already
Step 3. Go celebrate, you've done something good today2 -
So my company finally decided to make the shift from using irc for internal chats to Slack.
After a month of patiently waiting for my team to make the shift, I went ahead asked one of my (young) fellow teammate why he hasn't shifted to Slack yet. His reply:
"What's Slack?"8