Technical writings and software documentation
It seems Naveen, Ari and Shivan won't get to a conclusion. For relatively small SME projects, following a good coding habit is the most essential requirement. The cost of documenting the project could be too prohibitive for the SME. Consultants can give a value for the money by just following standards as per the language and environment.
This makes it imperative for the developers to be disciplined on whatever they are doing; that doesn't come right away when you work for small projects. It is like a circle, where bigger projects bring in discipline - developers have to gain experience with smaller projects to enter bigger ones - smaller projects need discipline (more than bigger projects where minor deviation from standards here and there won't matter much).
Tough cycle to break; but will try that!
On software, society, entertainment and many other topics that just do not matter.
Subscribe to:
Post Comments (Atom)
Earlier Posts
-
▼
2006
(25)
-
▼
December
(11)
- Handling attrition in SME
- Technical Writing and all such talks
- Traffic lights coming down in city
- Tips for reading other person's code
- Hype about IITs
- Crystal Version 9.0 - Demystified
- Crystal, Installshied, OLE and all the problems
- ChennaiCentral - a die-hard Chennai-loving Indian ...
- Google: Gmail - Calendar Integration
- Differing views of managing software requirements
- I'm impressed
-
▼
December
(11)
No comments:
Post a Comment