grunt. school.
So back twelve years when I went to the U for Computer Science, your choices for specialization were basicly nil.
The math covered was the old style monolithic algos that did EVERYTHING in one step.
This is how the old ForTran programming went, but they were forcing us to do it in C++.
It didn't matter if the same data was fetched and combined with the same operators 100 times in the step, it's how things were done.
The programming languages taught were also a bit light.
ForTran, C, C++, Scheme, Pascal. That's it.
ForTran was only taught for people wanting to talk to engineers.
Scheme was used everywhere you didn't need any particular language.
C and C++ were used interchangably in a few low level classes, then dropped for the remainder of your degree course.
Pascal was in a couple specialty intro classes in the hope that someone still used it.
In all, I was dissapointed with my experience.
Researching schools to go to at the time was a bit difficult.
They all had brochures that looked the same and made the same claims about their amazing program.
Finding and asking students who had already been there was nearly impossible, as I lived very very far from any university.
Anyone who's thinking "why didn't he just look it up on the 'net?" has no clue about the state of technology at the time.
I've been trying to make up for my lack of school experience with my own learning projects and such.
It's slow going, unfortunately.
I want to break into independent games, but my skillz are lacking here and there still.
The open source game engines I've tried are poorly documented to say the least.
SDL has the best outlook, but there's still that learning curve.
Got a couple online books about various game engines that I haven't gone through yet.
Hooked up an old monitor to the secondary output on my gfx card.
It's only working in 640x480 these days, it seems. :(
Still, having a second display has proved useful in numerous ways.
More screen real estate is good.
The math covered was the old style monolithic algos that did EVERYTHING in one step.
This is how the old ForTran programming went, but they were forcing us to do it in C++.
It didn't matter if the same data was fetched and combined with the same operators 100 times in the step, it's how things were done.
The programming languages taught were also a bit light.
ForTran, C, C++, Scheme, Pascal. That's it.
ForTran was only taught for people wanting to talk to engineers.
Scheme was used everywhere you didn't need any particular language.
C and C++ were used interchangably in a few low level classes, then dropped for the remainder of your degree course.
Pascal was in a couple specialty intro classes in the hope that someone still used it.
In all, I was dissapointed with my experience.
Researching schools to go to at the time was a bit difficult.
They all had brochures that looked the same and made the same claims about their amazing program.
Finding and asking students who had already been there was nearly impossible, as I lived very very far from any university.
Anyone who's thinking "why didn't he just look it up on the 'net?" has no clue about the state of technology at the time.
I've been trying to make up for my lack of school experience with my own learning projects and such.
It's slow going, unfortunately.
I want to break into independent games, but my skillz are lacking here and there still.
The open source game engines I've tried are poorly documented to say the least.
SDL has the best outlook, but there's still that learning curve.
Got a couple online books about various game engines that I haven't gone through yet.
Hooked up an old monitor to the secondary output on my gfx card.
It's only working in 640x480 these days, it seems. :(
Still, having a second display has proved useful in numerous ways.
More screen real estate is good.