Click here to Skip to main content
15,868,010 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
hi group,


i am a new in development,i faced problem many times when the task assign,generally i started by my logic,later i thought in some stage or senior gave idea then i realize that was not the better logic or better procedure to solve the issue which i followed.
i am worry about.....

so group i want to ask when a task assigned then what procedure you follow in generally & in system wise too.
Posted

Let me give you one idea — from a different stand point. Most successful projects I knew well were written twice.

Now everyone talks about code reuse, especially managers responsible for project deadlines and use of team working time. There is common vision that re-writing of the project is just a waste of time. This is one of the most stupid modern trends. Instead of having first version of the project to be used as a working prototype mostly useful to learn the field and techniques and crystallize a plan for a mature project in its second version, people pretend that a first version will be mature enough to go to market. The result of this delusion is enormous cost of the project: it is done "once" but is being "improved" without maturing — ever.

Plan your logic and architecture as thoroughly as possible but… Don't be afraid to start over, based on your experience and learning your mistakes. Most people and teams cannot design everything in advance in first place, so be realistic.

—SA
 
Share this answer
 
v5
Comments
Abhinav S 18-May-11 0:45am    
My 5.
Sergey Alexandrovich Kryukov 18-May-11 0:48am    
Thank you, Abhinav.
--SA
Nithin Sundar 18-May-11 0:47am    
This is happening a lot. 5 for pointing this out!
Sergey Alexandrovich Kryukov 18-May-11 0:48am    
Yes, thank you, Nithin.
--SA
Hemant__Sharma 18-May-11 1:24am    
Wow.. well said. My 5.
Be confident and write your own logic. Get a solution working.
Request your seniors to review your logic / solution intermittently so that they can point out anything that may be wrong or not optimized. This would be one of the best ways to learn new and better approaches to solve problems.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 18-May-11 0:41am    
This is wise, my 5.
I have another opinion, not different from yours, but from a different stand point.

Please see my answer.
--SA
Abhinav S 18-May-11 0:45am    
Sure. Thanks for the 5.
Nithin Sundar 18-May-11 0:47am    
5 for this!
Abhinav S 18-May-11 0:48am    
Thanks Nithin.
One thing in development is that there is no "perfect way" to code. Everything depends on how each developer does his job in writing code. These are some helpful stuff which indeed make a huge difference in the end:

1. Understand the requirements of a feature or understand why a bug has suddenly popped up.
2. Like others said, have a well prepared logical flow and be confident. Understand that there is always room for improvement everytime.
3. Never miss out on Unit Testing. This can be a great boon to you sometimes. A perfect release which took a day longer is better than an early release with many bugs.
4. Always insist on a code review from your superiors. Not only does this point out something wrong before it happens, you can also learn a great deal from this through some techniques hinted by your superiors!

Good Luck!
 
Share this answer
 
Comments
Hemant__Sharma 18-May-11 1:25am    
Right. My 5.
Nithin Sundar 18-May-11 6:45am    
Thanks!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900