Working in a big Vs mid size organisation
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
No! If I find a problem, I take it to my line manager (me) who tells me to fix it. I delegate it to my junior (also me) who sulks for a while, and then gets it done. The accountant (me again) raises hell for the wasted time since the customer (not me) will never find the problem, until the MD (me in a funny hat) tells him to shut up. As you may have guessed, I work for myself. It helps, but the Christmas party is always a bit quiet...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
Large organization, branches, Labels, clumsy diagrams. By any chance, you use Rational Clear Case? That just sucks. Solid tool though. Seriously if you are not on the right project & assignments, working for bigger companies rots.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
-
Large organization, branches, Labels, clumsy diagrams. By any chance, you use Rational Clear Case? That just sucks. Solid tool though. Seriously if you are not on the right project & assignments, working for bigger companies rots.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
-
No! If I find a problem, I take it to my line manager (me) who tells me to fix it. I delegate it to my junior (also me) who sulks for a while, and then gets it done. The accountant (me again) raises hell for the wasted time since the customer (not me) will never find the problem, until the MD (me in a funny hat) tells him to shut up. As you may have guessed, I work for myself. It helps, but the Christmas party is always a bit quiet...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
draghu wrote:
more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy.
The joy of configuration management[^], or perhaps lack thereof. Seems like a pain until you discover how scr*wed you are without it.
draghu wrote:
biggest enterprise software manufacture in the world
They usually have a good notion about the value of proper configuration management, so info on what was shipped to whom should be available somewhere.
draghu wrote:
more than a week to find out the correct labels for the rest 15
Which revision control system are you using?
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS My LinkedIn Profile
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
Continue working wherever you're currently working - but also use your free time to work for yourself (not for money, though) and regularly put out small (and hopefully, useful for others) articles for Code Project. This way, you're also intellectually satisfied.
-
Continue working wherever you're currently working - but also use your free time to work for yourself (not for money, though) and regularly put out small (and hopefully, useful for others) articles for Code Project. This way, you're also intellectually satisfied.
-
No! If I find a problem, I take it to my line manager (me) who tells me to fix it. I delegate it to my junior (also me) who sulks for a while, and then gets it done. The accountant (me again) raises hell for the wasted time since the customer (not me) will never find the problem, until the MD (me in a funny hat) tells him to shut up. As you may have guessed, I work for myself. It helps, but the Christmas party is always a bit quiet...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
OriginalGriff wrote:
I work for myself. It helps, but the Christmas party is always a bit quiet
Yes I know, sheep really don't talk that much and if they do all it comes out as is blah, blahh, blahhhh! :laugh: Cheers!
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
-
OriginalGriff wrote:
I work for myself. It helps, but the Christmas party is always a bit quiet
Yes I know, sheep really don't talk that much and if they do all it comes out as is blah, blahh, blahhhh! :laugh: Cheers!
"With sufficient thrust, pigs fly just fine."
Ross Callon, The Twelve Networking Truths, RFC1925
Oh, we don't talk to 'em! :-D
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
No! If I find a problem, I take it to my line manager (me) who tells me to fix it. I delegate it to my junior (also me) who sulks for a while, and then gets it done. The accountant (me again) raises hell for the wasted time since the customer (not me) will never find the problem, until the MD (me in a funny hat) tells him to shut up. As you may have guessed, I work for myself. It helps, but the Christmas party is always a bit quiet...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
but the Christmas party is always a bit quiet on the plus side, you don't have to worry about those embarrassing photos coming back to haunt you :-D
Steve _________________ I C(++) therefore I am
-
I have been in the software industry for 6 years now and worked for two organizations, over 5 years in a mid size org and less than a year in one of the biggest enterprise software manufacture in the world. There is a huge difference in the way the two work, the way how the daily business run in these companies. I wanted to share a recent experience regarding a fix. It’s a one line fix, I think it was a mistake by the original developer who is not fully clear with the expected functionality or he was not informed well; it was a one line fix and I did it. Then I get 15 bugs assigned to me asking me the fix the same for 15 different branches/labels, port the fix to 15 different builds. I took me one day to figure out the fix and more than a week to find out the correct labels for the rest 15, my manager was not sure about what labels to use, the product mangers were not sure which customer is on what release etc etc. It was messy. Lots of emails were exchanged to figure out the right labels. I had to redo some work because I was using wrong labels. These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up. Is this how everyone works.
draghu wrote:
These are my early days of being a part of a big enterprise software organization, I am not sure if I can fit here. At least these are not the kind of challenges I would like to take up
What challenge exactly do you think you are encountering? Large organizations will have more complex communication problems. I believe there is even socialogical theories about that. That has nothing to do with technology. Supporting customer on different releases is a business decison just like any other business decision. The business was willing to pay you for a week due to the businesses inability to track down information. Maybe they prefer it that way. Maybe they just can't figure out how to do it better. But maybe they are open to allowing you to find a different way to do it.
