Daily Scrum (2013-10-25)

This morning I dug right into the software and started working through compiler errors at 6:40AM.  After several hours and about 500 compiler errors, I started checking to see if the error count would drop below 102 (it stops at 102, so there's an unknown number of errors beyond that).  And finally, after weeks of non-stop error fixing, the number dropped to 70.  I quickly fixed the remaining errors and started the program.  The main window popped up, in rough shape but at least it was running!

So what did I do last time?

I fixed a couple thousand more compiler errors.  The program finally compiles as of 11AM today!

What do I hope to do with what's left of the day?

I'm going to start debugging the foundation of the software - opening and closing the new portfolio files, and maybe even try to create a new loan.  There's going to be thousands of bugs in the program, but at least now I can start testing and refining the user interface, etc.

Any roadblocks in my way?

I have some paperwork to do and a few phone calls to make, but I'm so excited the program runs I'll probably forget to do that stuff.


Daily Scrum (2013-10-18)

What did I do last time?

On Monday, I worked at TrailsWeb because the State was closed and made another good push toward getting the program to compile.  As far as I can tell, the main window compiles and the loan calculator code compiles.  Many of the reports, the template designers and print-time template drawing code, along with several other forms compile, too.

What I hope to do today…

I'm going to keep plugging away at those compiler errors until the program can start.  It'll undoubtedly crash like crazy until I rewrite and debug all the new pieces and fix where they splice with the existing MLP system.  I've been working out a new structure for how MLP will store the loan data which will make viewing the loan data and recalculating the loan much faster - it'll also simplify the loan calculator system.  I doubt I'll start implementing that today, but I am refining that design as I review the code while fixing compiler errors.


Time, patience, and focus.  I've been making great headway the last two weeks, and I want to keep it up.  I have a quick edit to make on a website, and a moderate one on another site which will take a bite out of the hours in the day, but there should still be plenty of time for fixing compiler errors.


Daily Scrum (2013-10-14)

What did I do last time?

Friday was awesome.  I worked on Moneylender Professional 3 all day, only taking a brief pause at 4:00 to do a couple small things for another client then back on Moneylender until 5:00.  I made what I estimate to be about 3000 fixes to compiler errors!  As far as I can tell, the main window should compile – which is a major feat.  Also, several forms such as "Manage Payments", "Manage Regular Payment", "Manage Late Fee" were upgraded to the new file system.  I believe about 2/3 of the loan calculator is also done.  It's hard to tell exactly what remains because Visual Studio only shows the first 100 compiler errors it encounters, so there might be another 2,000 errors or there may be another 20,000.  If I had to guess, I'd say more than half the program has been revised so it will compile.

What do I plan to do today?

It's a bonus day to work at TrailsWeb, with the State of South Dakota being closed for Columbus Day.  I'd be super excited if I can get the rest of the compiler errors fixed and start debugging the program under the new file system.  So today I'm just going to go through as many compiler errors as I can and if I get them all I'm going to start debugging the program and adding in missing pieces of functionality.

Roadblocks that might stand in my way?

Today is a freebie on the TrailsWeb schedule.  Also, there's not much else I need to be working on right now.  If I get tired of compiler errors, I might hop over to a small HTML5 / Audio conversion job for a couple hours.


Daily Scrum (2013-10-11)

What did I do last week?

Well, obviously, I bit off more than I could chew.  I did make a lot of great progress on the system that installs licenses automatically, and the system that allows manual license assignment on the web.  I forgot how many things I had to change from MLP2 to get it to work in .NET 4, so that was an unreasonable goal to set for a single day.

What will I do today?

Today I’ll be working in MLP3 to get the code to compile so I can get it running again.  There’s a lot of code still that needs to be rewritten, but hopefully I can make another big dent in it.  When it can compile and run, it’s going to be a fast and fun ride to the release of the program.


I have a couple phone calls to make, a couple tax forms to fill out, and some small jobs for other customers.  Since I do my best work in the morning, I’m going to give myself until 3PM to work on Moneylender and then button those other things up in the afternoon.


Daily Scrum (2013-10-04)

What I've done since last time…

I was sick all last week, and I still have a cough I’m trying to get rid of. I haven’t made much progress on MLP for about four weeks because of the mail server issues that needed to be dealt with. Now that that has all stabilized, I have time today to make some good progress on MLP.

What I hope to do today…

MLP's sales have always been somewhat irregular, but 2013 has seen more consistent sales than ever before. At the present, we're in a bit of a dry spell that we haven't seen for nearly a year. My goal today is to upgrade MLP 2 to .NET 4 and change the activation system to use the new system that MLP 3 will be sold under. I hope to have MLP available for purchase on TrailsWeb's online store by the end of the day today.

Any roadblocks?

I have to make two small edits on other websites which shouldn't take very long. Moving all the existing licenses into the new activation system might be a chore. Getting the online store production ready by the end of the day is a pretty major undertaking. I have to watch my son for an hour at 1 PM. Other than that, it should be smooth sailing.