A Very Sixy Week
Another week, another review. You know the drill. Now let's get to it.
This week was another light week. The only post this week was a riveting analysis of the blog's audience statistics. I know I didn't hit the two posts per week you've come to expect, but the post was fairly long, so I'd say we still got the recommended dose of nonsense this week. Besides, I'd say that post is my favorite I've written so far, so that must count for something.
In our last review, I had mentioned a small porting project I was going to work on real quick and then post about. The good news is I did, in fact, start the project. The bad news is I didn't finish it, which you could have probably guessed due to the lack of a post about it. Turns out the project is a bit larger than I expected. The issue is not so much with scope as it is with the sheer amount of code. Porting the first class, which was just shy of 300 lines of code, took well over an hour. When I opened up the next class and saw it was over 900 lines, I died a little inside. The original codebase is in Python, so nothing translates particularly cleanly to Haxe. I basically have to rewrite the code, using the original as a reference. On top of that, several native features from Python need to be replicated or replaced in Haxe. Even the naming conventions are all wrong! I would say this isn't fun, but in a weird way it actually is. It's certainly grunt work, but I'm a sucker for a good grind.
This coming week is probably going to be side project week. Progress is slow, but I'm definitely getting somewhere. I think I'm getting close to actually getting some of the basic functionality up and running. It's sort of like killing a hydra, though. Every class I finish introduces three new types that need to be ported as well. If nothing else, I am learning quite a bit. I don't have a lot of Python experience, so looking over the codebase has shown me a whole bunch of little tricks. I also went into this with no idea how the system I was porting actually worked, but file by file I'm getting the idea. If I can finish it up this week, there will be a post about it. If not, there probably won't be any posts at all. So, the usual deal.
That's all for now. We probably won't talk until the end of the week, if not the next weekly review. Try not to get into too much trouble until then.
This week was another light week. The only post this week was a riveting analysis of the blog's audience statistics. I know I didn't hit the two posts per week you've come to expect, but the post was fairly long, so I'd say we still got the recommended dose of nonsense this week. Besides, I'd say that post is my favorite I've written so far, so that must count for something.
In our last review, I had mentioned a small porting project I was going to work on real quick and then post about. The good news is I did, in fact, start the project. The bad news is I didn't finish it, which you could have probably guessed due to the lack of a post about it. Turns out the project is a bit larger than I expected. The issue is not so much with scope as it is with the sheer amount of code. Porting the first class, which was just shy of 300 lines of code, took well over an hour. When I opened up the next class and saw it was over 900 lines, I died a little inside. The original codebase is in Python, so nothing translates particularly cleanly to Haxe. I basically have to rewrite the code, using the original as a reference. On top of that, several native features from Python need to be replicated or replaced in Haxe. Even the naming conventions are all wrong! I would say this isn't fun, but in a weird way it actually is. It's certainly grunt work, but I'm a sucker for a good grind.
This coming week is probably going to be side project week. Progress is slow, but I'm definitely getting somewhere. I think I'm getting close to actually getting some of the basic functionality up and running. It's sort of like killing a hydra, though. Every class I finish introduces three new types that need to be ported as well. If nothing else, I am learning quite a bit. I don't have a lot of Python experience, so looking over the codebase has shown me a whole bunch of little tricks. I also went into this with no idea how the system I was porting actually worked, but file by file I'm getting the idea. If I can finish it up this week, there will be a post about it. If not, there probably won't be any posts at all. So, the usual deal.
That's all for now. We probably won't talk until the end of the week, if not the next weekly review. Try not to get into too much trouble until then.