scotch_bright

3 ms·

1.
by scotch_bright 9y ago
Yes. I am simply accepting the premise given and trying to explore from there. I am aware of the generalisation. But, your answer does help us move ahead. It basically says that there is a way to produce a high quality code base. It is not
2.
by scotch_bright 9y ago
Wow. Thanks for that. Sadly enough it does seem like things like this are very common. This is super important because “software is eating the world”. A car/aeroplane/subway system etc all have code powering them. So our lives dep
3.
by scotch_bright 9y ago
Great so OSS projects also have a very large number of people coming together and collaborating. How do they stay clean? Why is there a mess in the code that gets made within companies? What do you think the difference is?
4.
by scotch_bright 9y ago
Okay. I will study more about Conway's law. Thanks for that. What I want to get at is: Is this the "normal" state of affairs? Do all projects devolve eventually? There seems to be a lot of work that has been done on Deign Pat
5.
by scotch_bright 9y ago
That is a great point. Design Pattern and CS fundamentals are old and have not changed for 20-30 years. These are problems that have been solved ages ago. I can completely imagine what you are saying about the old C++ code bases to be true.
6.
by scotch_bright 9y ago
I know. Thats why I was suggesting there should be some anonymous way of acknowledging the problem without dealing with the consequences. (I am open to suggestions about this) I feel like it's a widespread problem but since there is so
7.
by scotch_bright 9y ago
In case you see this and feel like the code base you work on is also a mess, then I think it would be a good idea to post something like: "I work at XYZ, and the code base is a mess." (Maybe leave out the company name if not comfo
8.
Ask HN: Does any body work on a huge (and old) code base that is not a mess?
16 points by scotch_bright 9y ago|19 comments