Re:Why do you not make the code available under a 'source co...
by plorkyeran on Wednesday June 17, 2015 @11:36AM
(#9732546)
Modifying behavior only by subclassing rather than changing the code was the original idea of the open/closed principal. Of course, the idea has drifted a bit since then since everyone discovered that in practice it worked terribly.
Re:Why do you not make the code available under a 'source co...
by ams6110 on Wednesday June 17, 2015 @01:48PM
(#9733839)
I see no indication that the devs aren't using version control. All we know from that statement is that they are not making it available to the public.
Re:Why do you not make the code available under a 'source co...
by Roboprog on Thursday June 18, 2015 @01:02AM
(#9736920)
point taken -- or rather, "given" :-)
Re:Why do you not make the code available under a 'source co...
by learnstats2 on Wednesday June 17, 2015 @11:29AM
(#9732468)
> How do you "undo" to yesterday when you change your mind about something???
One might argue that developer time is valuable enough to ensure that it's spent on things that won't be "undone".
Re:Why do you not make the code available under a 'source co...
by faceplanter on Wednesday June 17, 2015 @11:34AM
(#9732524)
That's totally unrealistic. Often it's not the dev. that changes his mind, but the client. And since they have the $$$ you will be "undoing" previous work.
Re:Why do you not make the code available under a 'source co...
by nickpsecurity on Wednesday June 17, 2015 @12:03PM
(#9732803)
Exactly. Any good development process and software architecture must be responsive to change without enduring huge problems trying.
Re:Why do you not make the code available under a 'source co...
by mgold on Wednesday June 17, 2015 @01:46PM
(#9733820)
What happens when you introduce a bug that isn't discovered for 6 months? What happens if you think of a better way to do something? What happens if you're working on something and the power goes out, leaving you with partially-completed and saved work with no editor history? And so on...
I was reading about SCCS at the time, and wanted to convince my management to use that, but couldn't get them away from the "directory tree per release version" method.
My next job in the mid 90s used RCS, and I've never worked at a job since that didn't use some kind of version control / archive software. Hard to fathom that some organizations still avoid version/revision control. How do you "undo" to yesterday when you change your mind about something???