Coding style shouldn't break C++ highlighting. Are you possibly using NEdit with an old Lesstif version that might have display problems? If not, report it and we'll have a look. That's definitely not a common problem.
That sentance, "Of course, I see no reason to force it on individual programmers. It's something managers should do, themselves.", was about project tracking, not about design documentation. Obviously the people doing the design should be the ones documenting it.
I remember several of the developers of one of our SASD projects expressing almost the opposite opinion; that SASD might be more helpful on a project with LESS experienced developers, where the pacing and structuring of the design process would lead them in a clearer direction than they might otherwise choose for themselves.
Slashdot Mirror
Coding style shouldn't break C++ highlighting. Are you possibly using NEdit with an old Lesstif version that might have display problems? If not, report it and we'll have a look. That's definitely not a common problem.
That sentance, "Of course, I see no reason to force it on individual programmers. It's something managers should do, themselves.", was about project tracking, not about design documentation. Obviously the people doing the design should be the ones documenting it.
I remember several of the developers of one of our SASD projects expressing almost the opposite opinion; that SASD might be more helpful on a project with LESS experienced developers, where the pacing and structuring of the design process would lead them in a clearer direction than they might otherwise choose for themselves.