|
|
Rather good IOTD, today. I think you have chosen the right approach.
"Reinventing the wheel" is very usefull occupation, especially if you want to have deeper understanding of how it spins. ;) Some folks here told a lot of their thoughts about using libs and reusing smbody's code. Some thoughts are very bright, but I think they are adressing another space. The real programmer should resolve such equations from the point of view on his problem, not the coolness of library or smbdy's code. So if you saw smbdy's cool terrain engine you should not try to do your own or even do a remake of smbdy's code, but if you need to do terrain engine, persuating some estimated results, such as profit, education, expierence etc, you MUST DO IT BETTER, even if you are NOT SMARTER. It is possible, believe me. I can evene say there are a lot of ways to make your code better than anyone's else(of course in some
specific areas). So you can make more readable code, more reusable,
faster one, more configurable, more well-designed, add on your own taste. Everything depends on your individuality.
P.S. As for myself, I'm eighteen. I have done some stuff before(
several serious system apps for WinNT, some winsock code,several MFC applications, some graphics stuff(filtration, 2d effects, compression, rasterization, convolution ,etc), some parsing code(
expression calc, differentiation, graph plotting, preprocessing html, without use of lex and yacc), etc), but hence some of this was even made for profit, all this stuff is far from the perfectance, needed to release the sources(currently most code "features" bad formatting, no makefiles, bad OOP design(if C++), if optimized it is completely not readable, if not it enomoursly slow, most classes, funcs and variable names are "taken from the roof"(esp. in older code)). I even have doubts about releasing to the public the stuff I am currently involved into. ;) Anyway I hope you'll soon see my IOTD(in about two months). Guess what it'll be. ;)
|