-
Building TyNETv5 Pt. 15 - Conclusion
2013.09.14 11:12:19This Monday university starts for me, which means I have to stop working on this for a while, at least until I figure out how to deal with everything. So I'll take yet another step back and see what I've accomplished and what I need to focus on next.
-
Building TyNETv5 Pt. 9 - Stitching it Together
2013.07.13 11:31:42I originally come from Java land and have most of my experiences with languages and IDEs that include build systems, so the way your program is compiled has never been something I had to worry about. In Lisp too this is usually not that big of a deal thanks to ASDF, which lets you define which files depend on what and figures out how to compile and load it by itself. My problem with building Radiance is also a problem that is specific to Lisp and doesn't really occur in any other OO language.
-
Building TyNETv5 Pt. 8 - Initialize!
2013.07.01 22:17:40About high time I write a blog post about this stuff again. Apologies in advance if I sound angry or in any way derogatory about things, I'm currently not in a very preferable state of mind. Still, Imma do this because then I'll at least have done something today. So, what's this all about then?
-
Building TyNETv5 Pt. 7 - lQuery and lQuery-Doc Release
2013.06.24 21:58:06Oh gods, I'm way too tired to be doing this at the moment, but here we go anyway. I finally wrapped all things I could think of up to release lQuery and lQuery-Doc. As I predicted, I was well able to finish lQuery-Doc within time and it was a great feeling of success when I finished it. But, then I had to go on to do a whole bunch of other stuff, which is why the release is so late rather than some time during the day.
-
Building TyNETv5 Pt. 6 - Intermission
2013.06.23 20:28:45As I was preparing lQuery for release today I noticed that I still needed a couple of other things before I was ready. One of those things was that my base syntax macro was actually not working properly (variables weren't being handled right), so I had to spend quite some time rebuilding and debugging that. Then I realized that I wanted to have a proper documentation of all the functions ready for release. Since I'm lazy and a programmer I thought I'd use lQuery to write a library that automatically generates HTML documentation files for a given package. This turned out to be a tad more complicated than I initially expected, so I couldn't finish it today. And that's basically why lQuery is delayed, oh no!
-
Building TyNETv5 Pt. 5 - Caramel Isn't My Flavour
2013.06.18 17:57:27So last week I was in Tokyo, which means not much was going on at all. Or rather, so I had planned, but something amazing happened in the meantime. One evening I sat down to take a proper look at Caramel, the library I had intended to use for HTML manipulation/generation. I didn't like it. So then I thought back to what I really wanted. I wanted to have jQuery, but in Lisp. Not thinking too much about it, I opened emacs and wrote a small prototype function that would allow me jQuery like syntax. After about half an hour of twiddling around, I had a (wonky) first solution and it was brilliant.
-
Building TyNETv5 Pt. 3 - Mission Statement
2013.05.29 14:16:35I never went to an actual coding class. I never had a professor teach me anything related to programming. All I know has been out of books, tutorials, specs and discovery. There are a bunch of problems with this approach, most of all that I started out with writing pretty damn bad code, had no idea of how to structure or plan anything and so on. These are all things a good professor could avoid. Regardless, I think this approach also has the benefit of dynamic learning and backstory. That is to say, I can follow back my timeline and see where I've improved and I know why my current style is better than before. I don't just do things because someone told me to.
-
Building TyNETv5 Pt. 2 - The Right Tools
2013.05.26 02:11:59
-
About Language Preference
2013.01.24 15:55:54Often times when you ask a programmer about what he works with, he'll tell you that he has to code in X for work and doesn't like it, but uses Y for personal projects because Y is so much more handy and appealing. Sometimes you'll get an answer that X and Y are the same. Rarely you'll get the answer that there isn't really a preference, but there's just one that is used most often, for one reason or another. Some people even get very enthusiastic up until extremely defensive about their language of choice, something I'd like to avoid doing. Regardless, I've been asked to state my personal preference and opinion on programming languages of today a while back and I'm here to answer that query.