suREFIre 2.0 CRMS Geeked Out Development Update
CRMS Geeked Out Development update 4/21
We came, we released, we got great feedback, and as Mark said Monday, we went back to the drawing board. While this is true, we didn’t really have to go all the way back to the “dragging our knuckles” stage of development and we actually have a lot of evolved and reusable code that fast tracks our User Interface transformation over the next few weeks.
To help keep you more informed and better able to understand our progress and/or delays as we furiously race towards 5/14, we wanted to share more of our internal development operations with you; partially to provide more transparency to our work, but mostly because Mark gets hernias and internal bleeding every time he tries to explain our development process (ha ha ha, just kidding Mark) đź™‚ .
Seriously though, it makes a lot more sense for development updates to be coming from me and I’m happy to oblige every 48-72 hours. So, here is my first development update for the CRMS system since our early adopter release was jettisoned.
New Deadline: 5/14
Code Complete: 20%
Current Roadblocks: None
Confidence Level: 95%
What’s going well?
- The User Interface (UI) – the UI transformation is going well. We’ve torn apart our dense pages and gone with lots of little pages. I’m almost completely done with the entire UI framework, next just comes putting all the code into the pages.
- Back to basic controls – Most of the proprietary (and heavy) controls we were using are going to be ripped out in favor of lightweight vanilla asp.net controls. This creates a little more work on our end to get the functionality we need, but the performance improvements are already noticeable. The initial work the last few days was finding adequate asp.net replacement controls for all the proprietary ones we were using. We have a solution for all but one, the email editor.
- Back to basic layout/style – All image elements have been ripped out. Now we’re just using cheap and free styles (like “background-color:blue;” to differentiate objects and layout, instead of loading images from web pages which increase load times. Another area creating load time benefit that is already noticeable.
- Browser compatibility – Making all of the above changes has fixed a number of compatibility problems we were having between IE and Firefox. I was more relieved than surprised by this, but it’s a win all the same.
- Dev team is kicking on all gears – We recently brought on help to speed up and improve our development process. We’ve taken a divide and conquer approach and everyone is busy on their tasks. We’re still early on in this “complete overhaul in sixty seconds” project, but signs are favorable that things are moving smoothly and we’re going to be able to roll out code on time and on schedule.
What could be better?
This is my section for honest dialogue about what’s not going well with the project. We’re only about three days in and everything seems pretty positive right now, so I don’t have anything to share at the moment that is concerning me. My hope is that I won’t end up needing this section very much, but if I run into roadblocks or issues, you’ll hear about it here first.