I've been working on a lot of behind-the-scenes stuff for this website, and one of the big changes is the way that authentication works. I'm not gonna bore you with the details, but the short story is that I'm "retiring" the old way that passwords were stored because it was pretty arbitrary and insecure.
Have you updated your password yet?
There's also a way to change your email address. You should probably take a look at that and update it as well.
Did you forget your password? There's now a "lost password" page.
Sometime in the near future, the old password scheme will stop working. Which means you won't be able to login anymore if you haven't updated your password.
So I'm still working on paying off my Technical Debt. There's a lot to figure out, things that need to get updated to work with newer systems that make life easier... and I'm getting there. Slowly, but surely, I'm getting there.
I've followed a fairly strict practice of versioning in the past. I've followed the spirit of Semantic Versioning, without even realizing it, though technically only about 90% of the way there. Most of this has to do with committing all the time, where I don't always update the version.
The problem has reared it's ugly head because I've recently changed my methodology for handling dependencies. With Subversion, I would "simply" use externals (svn:externals) to pull in external libraries using a fairly strict versioning system. Unfortunately (or maybe fortunately), each application was very much linked to a very specific version number. Technically each project should have been compatible only to the Major + Minor version (not all the way down to patch level).
Currently, I'm handling dependencies using Composer and Packagist (here's my public profile on Packagist). This way of dependency handling allows me to use automatic continuous integration testing systems like Travis-CI (I can't link to my profile, since it just goes to a blank screen, so search for "crazedsanity"), so I can be even more confident that my code will work on other systems. Oh, and I can put cool images up like this, which shows current and VALID values for build status on my projects:
(I totally understand if your eyes jumped to that grid right away)
Anyway, I've made significant strides toward code test coverage. That is to say that I've added unit testing to my systems in a more pronounced way, striving for TDD (test-driven-development), so that I can get to a point where I'm fairly confident in what ways any new changes will affect existing code. This will also help determine whether I need to release the code as a patch, minor version, or even a major version.
Hopefully this article gives you some insight into what I'm working on. Maybe it'll even give you some ideas, or help you, or encourage you to help me.
Today for me is the start of a new year. Going with the original Roman calendar March is the first month of Spring and therefore the first month of the New Year. Today is also my birthday so it is the start of another year of existence for me.
I have been afk for about 8 months now. I suffered from a number of losses of friends and family last year and basically closed myself off from everybody. I did some major thinking and made some life altering choices. I took a new job and moved myself and my family across the state. I'm finally getting settled in and I'm much happier with my new job and being much closer to friends and family. Unfortunately during low period last year I quit working towards my weight loss goals and actually packed on quite a few pounds.
I am happy to report that I will again be working towards my goals and blogging about them.
After some suggestions from friends, I've decided to start posting an "audio blog" about my story, "The Guardian Legend" (or :"Legend of the Guardian", or various derivatives). It's still under development, as I try to refine my writing style.
I started recording the first chapter. After some irritations of dealing with Audacity (my audio recording software), I found out some things about it (the story). First, while the heart of the story is undoubtedly good (at least that's what others have said after reading), it's... well, lacking. As soon as I start reading it out loud, I find it lacking something. The words jumble together, and it sorta feels... like a "B" movie.
Not a BAD "B" movie, but one that has potential. Like it's lacking good special effects... instead of seeing an awe-inspiring helm of a next-generation spaceship, you see a really tiny corner of it, where a great actor is using something that vaguely looks like one of the computer panels from NASA, back when they launched Apollo 13.
Anyway, I have to figure some way of writing my story so it's entertaining. The underlying actions are interesting, the idea of what's happening is good... but the way it's written is just... well, it's bad. I can tell that some of the writing is a few decades old. Yuck.
So how do I write it? Somehow, I've gotta find a writing style that matches how I tell stories. As I remember it, people reading the story weren't as thrilled as the people that I told the story. Because I really get into it when I'm telling the story, but somehow that just gets lost in the written part... ugh.
Anyway, this entry is just an appetizer. I'm working on the audio blog, but there's a bit of work left to do. Stay tuned!