+972 52-548-6969
Platform should have source control, and that is not optional
time to read 1 min | 113 words
Gary has a post that talks about something that I have been thinking about for a while. Platforms, defined as applications that you extend, must have source control built in. That is not an optional feature, that is a Must Have.
I am working on such a system now, and the amount of effort that it took to get to the point where I can have sort-of seamless source control means that I am not going to work with the product again, period.
I am toying with the idea of an enterprise platform that does hurt, that is possible to maintain and actually work with a smile with.
Enterprise, not enterprisey.
Comments
I think built-in is the wrong path. Enterprise plattforms should work well with my text files and DLLs, and allow me to import them by file copy operations. So, no need to mess with some proprietary version control mechanisms, or take the configuration and troubleshooting pains to integrate the app with an existing SCM. Just point SVN to the directory that has your customization files, done.
...platform that does hurt...
You meant "doesn't" right?
Thanks for the shout-out Oren.
My thoughts are in line with what Stefan said.
Our current product suite is well suited for source control. As a vendor, when we walk in to a customer site, one of the initial implementation tasks should be to get things under version control.
I spent all day yesterday at a customer site coding some customizations for them. At the end of the day, I didn't have anywhere to check code into. I felt somewhat dirty. Like my job wasn't really done. When I asked their technical team about what version control system they used, they just shrugged. Ugh.
Last week I had a customer ask me to resend them some custom development that we did for them 8 months ago, because they had "lost" the entire project that we delivered. Double-ugh.
Comment preview