3 ms·
Thank you for your follow up. Clearly your experience is far outside my world. I've never heard of an outside consultant being brought in to second guess the co
by anonymous245 16y ago
Thank you for your follow up. Clearly your experience is far outside my world. I've never heard of an outside consultant being brought in to second guess the company's "architect".
It seems like you mostly move among bad developers. I don't think your experience is relevant to most of the developers reading HN.
Obviously, a full rewrite not a good idea in most cases as Spolsky eloquently argued.
PS: I didn't detect any "defensiveness" (you know, the catchall passive-aggressive term that is used to use to imply that the other side has a weak hand without backing it up) in the post you were responding to. It rang true to me.
- kenjackson 16y agoI don't think I move among bad developers, per se, but when I consulted I generally worked at places that weren't software companies. HN is filled with developers who plan to build companies (or work for companies) whose core business is to build software and either sell or have that software be the key part of a service. A lot of the places I did consulting for, if all of their in-house software stopped working, they could probably still do business, but a lot less efficiently. Most companies are not "about" the software just like they're not about the desks in the office. And actually... quite often I wasn't brought in to second guess the architect. Many times I was brought in at the request of the architect. But yes, most of the time you're brought in because they lose faith in the architect or team. If you see me stop by to do a simple audit of your code, you should probably get your resume ready -- well not really, as I don't do any consulting any more.