I've asked myself some time ago why do not post anymore in this blog. Why I've stopped posting rants about technology, why I've stopped doing work-in-progress snapshots of code or Lego guns. Fact is that I don't have time I want to spent writing blog posts. I speak in codes and comments, my Lego gun progress is far beyond the need of sharing and I actually don't post anything of the really stuff I've programmed so far. I still want to publish my library one day, but it'll need a lot of time to perfect (I hate imperfect code). I know at the right places, people are interested in my output - but right now I'm not yet interested in sharing my technology or thoughts. I've already deleted old version of demos and libraries from my dropbox folder and I don't want them back there. If I'm going to publish them, I'll create a completely new and non-blog wegpage for it. I believe that if you eventually find yourself not beeing able to post anything contributing anymore, you don't need to. I started my first blog because I followed the advice of Jeff Atwood over at Coding Horror which is that if you want to get really good at something, just create a blog and constantly use it to document and improve your progress. While most of his stuff is completely irrelevant to my dedication, this single advice eventually helped to get better (though his advice had a rather different meaning). And over the years I developed a competent internal workflow where the blogging element became more of a remote status dump. not necessary of helpful to bring my closer to lifetime goal. I know there some dudes and/or dudettes reading it from time to time but I've completely contributing for a really long time now. The blog became more of a mess representing how mixed but still focussed my efforts were. I don't want to continue this anymore. I'm almost done with my bachelor (beginning a master), found a great and occupying game developement studio where my developed skills are appreciated and every new library feature I finish eventually leads to the next pixel on my personal progress bar. The real challenges and interesting things await behind locked doors where I can't blog about them. It's the place where you can train and use your skills to the max while still having more than one blogging opportunity to discuss solutions and document progress. Let's call it a balance that sorta fit's my way of life and work. So, this blog now officially closed for future postings. Anything I do will eventually be reachable via my deviantART gallery - though not my libraries but rather links to games that use them or something like that. So if you're interested in any output I may generate in the future, just check this site out. I won't post any music anywhere except when actually doing a video game. And I still don't care for those who dare to say I never release anything. You know, the awesome thing about commercial video game development is that there WILL be some output... And while I can focus on getting things done in time, I can put my perfectionism to good use in my stuff. I'll never release a game on my own without atleast 50% technical perfection. So if you'll excuse, there are some things I have to get done.
Tags: The End
It's been quite a hard week. Finished my bachelor thesis, documented and debugged a shitload of code, rewrote third of the thesis a bunch of times and now I'm ready to print and bind it. Then just add a CD and I'm officially done with it! Well, a little presentation if they accept the thesis and I'm free to go. Oh boy - this would mean beeing done with the bachelor, having an academic agree and so on! Fuck, yes. I was always looking forward to this. But whichever way I'm turning it, I'm not fully lucky with what I see. Sure, it was a heck of work, I can use the results everday if I want and I reall stand to my work. But damn, I wish I sorta relax right now instead of when it's officially over. Still have to work out some presentation with pretty pictures. Geez, I hate pretty pictures in presentations.
I like original work and reasearch, independent and logic-oriented work in the field programming. It's a field of great and interesting discoveries - just take a look at what some indie developers archieved and strife for. Anyway, if you have to create something purely using the scientific method, your chances to just successfully dump your results will be astronomically low. Personally, I also build up from a problem with a well-analyzed situation. Then I logically advance to the most suitable solution with some optimization taken here and there. Often I arrive at the best solution this way unless it's a very complicated base situation (in which case' you'll have too much to take into consideration). But on a scientific base? Well, first off you'll have to read everything that exist just to make sure your worthy of state-of-art thinking (hohoho). Then you can attempt to take closer look at your problem while applying the things you learned before. Quote something here, do foot notes there - there's obviously no way the author can do this all on it's own! He's not even allowed and intensive science based study has to be done before! Well, that's the way a lot lecturers I know see it - especially the more theoretic and less hands-on ones. They don't even think about original work and research, alternative ways of achieving knowledge or whatever. You only way to justify your work is do it bottom-up with a lot of foot notes in the more theoretical part and step-by-step analysis/buildup for everything else. Geez, I hope my prof's is a bit more open to it than others. Gladly, my bachelor thesis is more about implementing, searching and designing a suitable subset of techniques rather than proving. Even better, I get to do an analysis of my implementation so any assumption I make in the design part will have a result later on. Hmmm, I think I'm worrying too much about it. Awesome enough that I can quote my own documentation - take that, science!
I had an extremely long programming session today (well, it's more like tomorrow now). Well, not as extreme as it sounds, but 7 hours non-stop coding and debugging is quite exhausting I can tell you! I made the really big mistake of not completely finishing the resource manager part I was working on. I had to re-implement a few hundret lines because the logic was and broken everywhere. Anyway, it seems to be on the right way now and I'm really I spent the night programming on my project. Didn't do something like that for while, so I guess it was necessary. My project's going along rather well. Too bad I still have to debug some polling where there should be polling at all.
Today I sorta took a day off and visited a museum I've never seen before. I had to get out of this room and get some other things to do. I did nothing programmey oder bachelor-related at all, I just did stuff I haven't done in a long time. It's not that I worked effin hard the last days/weeks, but I did a lot of stuff on and on again. It's just not worth it. Sooo, at the end of the day I continued the work on my Lego gun I didn't completely finish the last time. I improved the iron sight to some very good ghost sight relatively unaffected by light coming the from the shooter's direction (a weak spot of the previous version). I also tried to mod my bullet type to feature thicker and broader rubber bands I bought before. They provide more power at higher space consumption. The changes I made also get together with my problem of not having enough special Lego parts: 6 cartridges at your disposal with far more sturdy construction and higher shot power per projectile. Additionally, I filled some more gaps as it makes sliding more effective. Thus, I get the ability to create some nice magazine one day. The cartridge is now powerful enough for anything I'd ever need I guess. The only thing not nicely done yet is the gun's cartridge holder lock. Using some well-fitted plastic cases doesn't work as it does with normal guns. No idea what to do there beside the rather flimsy but functional solution I'm having right now. Anyway, this is something I'll have to do some other day. Tomorrow will be filled coding, writing and Harry Potter movies in the background. Or Indiana Jones - I'm uncertain about this.
I never this in such a direct way, but wherever I have to get something done some time, I'm asking for a deadline or date. It's a very important fact to know, especially cause they can get huge productivity boost of you. I haven't actually met many persons in my life that work better without deadlines. Then again are those who never get anything done with deadlines or not - usually raging against deadlines in any way. Personally, I believe they just don't want to get it done. I'm a lazy person, too, but I'm also motivated by necessity. Right now I'm experiencing the best example ever: having only a month left for my bachelor, I got my "reduce everything to important essence you'll get your marks for" spirit back. I'm able to perfect almost anything but I need a certain pressure and experience with things. Having no pressure will result in more time to get experience but having no experience will just increase pressure. I'm very glad about this set deadline as it makes my code more minimal and shortens it down to the things that actually matter. Oh and my new task/resource manager system seems to work just perfect and nice as thought. I'm really happy about this - it took me over a year to learn about and perfection every detail. It's good that I made it my bachelor thesis. Haven't done that much progress for quite some time now.