\ud83d\ude42<\/p>\n
I finished February’s work on my software development notes. Despite a late start and general laziness, I think the project went decently well. Here’s the project in its current state<\/a>. I’m taking the Zettelkasten approach of treating the content as a flat list of entries that I organize in a separate document (in this case, the main project page). I’ll probably make this the default way of organizing my projects.<\/p>\n The purpose of February’s sprint changed as it progressed. I wanted to come up with a basic procedure for my programming projects, but that ended up being too ambitious for the way the project was going. Instead I set up buckets to drop my future software development notes into. My plan is to do a lot of that work incidentally as I do my other programming projects.<\/p>\n In related reading, I finished IEEE’s Guide to the Software Engineering Body of Knowledge<\/em> (SWEBOK). I give it 4\/5. It’s important and fairly comprehensive. But I have problems with the organization, which is most of the reason I was reading it.<\/p>\n After SWEBOK I started Release It!<\/em>, a poorly named but respected book on designing your web app to survive in the wild.<\/p>\n \ud83d\ude42<\/p>\n My next programming project will be for Thinkulum March, which starts this week. It’s a continuation of the project generating program<\/a> I started writing a couple of years ago. It creates boilerplate code to kick off a programming project. This month I’m going to try to get it to version 1.0. This week is the initial planning and exploration phase.<\/p>\n","protected":false},"excerpt":{"rendered":" Software development \ud83d\ude42 I finished February’s work on my software development notes. Despite a late start and general laziness, I think the project went decently well. Here’s the project in its current state. I’m taking the Zettelkasten approach of treating … Continue reading Coding project generator<\/h2>\n