----------------
Very simple, asking the experts for what I didn't know.
In project management, each project is assigned a pcode or project code to report time spent on a task.
In complex system, nobody knew everything. Thus instead of scratching my head for hours or days, I've made visits to expert in that field, made phone call, or sent an email. Expert would spend around 15 minutes - 30 minutes to answer my questions. Of course, they could charge with my project time report code, i.e. pcode.
-> The total time spent on the pcode would be less, and I could get my tasks done quicker.
-> As people said that the project/product is less expensive, faster, and better quality. [Expert was consulted.]
I couldn't understand developers staying at their desk, and scratching their heads instead of making a trip :-).
Of course, if you're assigned a task that you're the only resource on that subject, you'd be working alone.
- - - - - - - - - - - - - - - - - - - - - - - - -
I recalled that I had worked for an outsource company in Vietnam for a short period of time. I left due to the trouble with fucking neural networks.
This company had works for Nortel. Nortel bought a switch, and probably asked this company to do an architect diagram.
Employees at that company started by reverse engineered of codes. The challenged me to do this diagram.
Of course, I knew reverse engineered would produce a messy diagram, if supported by the provider.
I walked in the office of Nortel staff, and asked for documentation. I knew that Telecom Company has to maintain good document. Nortel staff gave me a story of buying a product developed in a garage without documents. Later I found project documents with diagrams, i.e. a good starting point to further investigation/break down into smaller parts. I have spent time to search Nortel's document repository for info instead of reading codes. Anyway I left there shortly after.
-> Why scratching your head with reversed codes? They must have some forms of documentation, otherwise they couldn't enhance those.
-> There must be good documents for a large system; otherwise development time would be very long and full of bugs.
* Personally I wouldn't pay for a software or hardware system without proper documentation.
Very simple, asking the experts for what I didn't know.
In project management, each project is assigned a pcode or project code to report time spent on a task.
In complex system, nobody knew everything. Thus instead of scratching my head for hours or days, I've made visits to expert in that field, made phone call, or sent an email. Expert would spend around 15 minutes - 30 minutes to answer my questions. Of course, they could charge with my project time report code, i.e. pcode.
-> The total time spent on the pcode would be less, and I could get my tasks done quicker.
-> As people said that the project/product is less expensive, faster, and better quality. [Expert was consulted.]
I couldn't understand developers staying at their desk, and scratching their heads instead of making a trip :-).
Of course, if you're assigned a task that you're the only resource on that subject, you'd be working alone.
- - - - - - - - - - - - - - - - - - - - - - - - -
I recalled that I had worked for an outsource company in Vietnam for a short period of time. I left due to the trouble with fucking neural networks.
This company had works for Nortel. Nortel bought a switch, and probably asked this company to do an architect diagram.
Employees at that company started by reverse engineered of codes. The challenged me to do this diagram.
Of course, I knew reverse engineered would produce a messy diagram, if supported by the provider.
I walked in the office of Nortel staff, and asked for documentation. I knew that Telecom Company has to maintain good document. Nortel staff gave me a story of buying a product developed in a garage without documents. Later I found project documents with diagrams, i.e. a good starting point to further investigation/break down into smaller parts. I have spent time to search Nortel's document repository for info instead of reading codes. Anyway I left there shortly after.
-> Why scratching your head with reversed codes? They must have some forms of documentation, otherwise they couldn't enhance those.
-> There must be good documents for a large system; otherwise development time would be very long and full of bugs.
* Personally I wouldn't pay for a software or hardware system without proper documentation.
No comments:
Post a Comment