[eluser]Unknown[/eluser]
I've peeked at CI a few times in the past but just fiddled about and thought about how nice it would be to use for a solid project.
Well now I've got something I can get my teeth into and using CI in anger throws up some interesting questions about the best way to go about things.
As part of the big picture, I'm starting off by writing a library for authentication stuff. Clearly models are the place where you're
supposed to put your data access logic but I wonder what the general thinking is about putting data access login in a library instead.
It's been a constant theme in my development career that I paint myself into a corner with poor decisions about application architecture and end up with so much code in so many places that things swiftly become a nightmare to maintain.
I'm determined to nip that little nightmare in the bud and get this right. Thoughts and opinions very welcome, peeps ...
