I intend to write regularly about the process of building nextSIS, but to do this I find myself with a difficulty. nextSIS exists because the open source system we originally chose to implement at our school proved too problematic to continue with. As such, nextSIS is in no small part defined by the failed project it replaces.

However, if I regularly name the SIS we had so many problems with on this blog, then this project becomes too defined by this other system. So I’ve chosen to forego the prospect of easy search engine hits and only refer to it here as namelessSIS. It will be necessary to draw comparisons between nextSIS and namelessSIS in order to explain some of the design decisions, but this way – by not mentioning rival systems here except in a vaguely absurd and abstracted way – the message stays more positive. Also, I think they might sue.

If you really want to know about our namelessSIS experience though, and any pending lawsuits, you can read my personal blog.

Tagged with:
0 comments on “namelessSIS
3 Pings/Trackbacks for "namelessSIS"
  1. […] and that’s nobody’s fault, probably, although I do wonder whether it’s something namelessSIS would have benefited from […]

  2. […] because they that parent in is your system as a teacher. In fact, this is how things are with namelessSIS, where the only solution appears to be for a teacher to have a separate user name as a parent in […]

  3. […] the last few months I’ve been juggling the pressing needs of developing our local version of┬ánamelessSIS against investing in the future by developing nextSIS. But another factor may be our decision to […]

Leave a Reply

Your email address will not be published. Required fields are marked *