This also assumes that, for an SIS, there is one...

2008-04-09T00:39:00.000-04:00

This also assumes that, for an SIS, there is *one* solution -- in addition to developing a tool that addresses a subset of needs, you need to add in the ability to make your specific solution generalized enough where people can use it across contexts with minimal fuss.

Meeting the needs of one school is an easier proposition than generalizing that solution out to meet the needs of a larger subset of schools -- and that's where the real trick is.

On top, of course, of making it so the app is easy to download, install, configure, and use.

I'd say 6 mos to build, 1 year to generalize, and another year to re-design and incorporate changes based on informed feedback. Even if you have a team of 500, it's less about generating lines of code, and more about generating the *right* lines of code.

Nice post. I think of lot of people who move over...

2008-04-08T16:28:00.000-04:00

Nice post. I think of lot of people who move over to FOSS and especially Linux are assuming that there already should be an open source app for such-and-such purpose.

Your post helps explain why the repositories tend to have an abundance of particular types of applications and a virtual void of other types, especially SIS.

Comments on Tuttle SVC: The Brutal Math of Open Source SIS's

This also assumes that, for an SIS, there is *one*...

Nice post. I think of lot of people who move over...

This also assumes that, for an SIS, there is one...