(This post was last modified: 22/04/2012 07:28 AM by ProperBritish.)

(22/04/2012 07:27 AM)ProperBritish Wrote:  I've written a sorting algorithm program in C-Style array and also using binary tree structures.
I also wrote a piece of coursework using OpenGL ES and C++, creating vertex buffer objects. And now I'm writing a physics simulation in OpenGL using GXBase, using C++. I'm in my second year of university atm.

Not to mention I also had to write artificial intelligence using Prolog, and some networking coursework using C#.

And i still have my 3rd year to go! Joy~

Next year I hope to be writing my final projet for the PS Vita, as well as another module in which I'll develop for PSP.

Man what? I haven't even gotten around to doing things like this, just math, math and MOAR MATH (then again I only did 3 courses in my term due to my chocolatety choice to switch majors). This is why comp sci at my uni sucks, should've just stayed with their traditional sciences (where they are 1337 in) than try out their take on computer science.

Hopefully I see stuff like this later on in my year :/

(This post was last modified: 22/04/2012 08:14 AM by Tetris999.)

(21/04/2012 05:23 PM)Tetris999 Wrote:  Ah fudge I have absolutely no computer programming skill, so I don't know how I can demonstrate my passion with "I like computahs HURR".

You don't have to show it through projects, though you can do some minimal contribution to existing projects and that'll count.
You can specify the types of things you do or read about, for example.

(21/04/2012 05:23 PM)Tetris999 Wrote:  This course is pants on head confusing, or at least from what I'm getting so far.

Algorithms can be confusing if you haven't really done them before.  Though if you're doing computer science, you should get comfortable with them cause you're probably only going to get more...

(22/04/2012 07:27 AM)ProperBritish Wrote:  VB is old, like really old xD

He said VB.NET which is basically an alternate syntax for C#, not the older version of VB.

(22/04/2012 08:13 AM)Tetris999 Wrote:  Man what? I haven't even gotten around to doing things like this, just math, math and MOAR MATH (then again I only did 3 courses in my term due to my chocolatety choice to switch majors). This is why comp sci at my uni sucks, should've just stayed with their traditional sciences (where they are 1337 in) than try out their take on computer science.

Hopefully I see stuff like this later on in my year :/

Computer science is somewhat more geared to maths, algorithms, abstractions etc - it isn't particularly that practical, so don't expect to do too much of that sort of thing...

(23/04/2012 07:03 PM)ZiNgA BuRgA Wrote:  

(21/04/2012 05:23 PM)Tetris999 Wrote:  This course is pants on head confusing, or at least from what I'm getting so far.

Algorithms can be confusing if you haven't really done them before.  Though if you're doing computer science, you should get comfortable with them cause you're probably only going to get more...

(22/04/2012 08:13 AM)Tetris999 Wrote:  Man what? I haven't even gotten around to doing things like this, just math, math and MOAR MATH (then again I only did 3 courses in my term due to my chocolatety choice to switch majors). This is why comp sci at my uni sucks, should've just stayed with their traditional sciences (where they are 1337 in) than try out their take on computer science.

Hopefully I see stuff like this later on in my year :/

Computer science is somewhat more geared to maths, algorithms, abstractions etc - it isn't particularly that practical, so don't expect to do too much of that sort of thing...

Well, I'm only complaining about it because of the slur of information when reading any scientific text documenting areas of mathematics. Not to seem like some poser or anything, but I really like math, I just don't like to struggle to understand the jargon that many experts use. It's almost like every mathematics professor/person believes that people cannot have a learning curve into understanding something and must take it for what it is. It's as if you walked into a language course and the professor taught the course in french, assuming that this "immersive" approach is something that people can understand right off the bat (some courses actually do this, later when you are at third year or fourth).

Of course, understanding mathematical jargon comes with time, but it is frustrating nonetheless when all explanations are extremely linear and straight forward, as soon as you don't understand a piece of information in a math textbook (and ESPECIALLY an algorithmic course), it's very hard to be able to interpret the ideas and techniques into something that you can understand.

A math textbook assumes that you have MASTERED concepts before going on to the next concept and therein lies the problem, math, in general, for me has never been _taught_, rather my life's approach to it is that it needs to be researched itself.

There's never been a single math textbook that has explained things rationally to me, ever, it was usually myself looking at reading things that made no sense, me playing around with the equations and then formulating my own theory on what the chapter is talking about.

In short, I just thought that this was the way it was and that if I didn't want to seem incompetent, I would be able to struggle past it. That was, until, I got into my statistics course this year and the prof made the WORLD of explaining mathematical concepts through repetition, different takes on the information and the break down of jargon so that people who are unfamiliar with the subject can understand. Fuck, that's the REASON why people go to school! It's someone holding your hand through territories that are unfamiliar to you as the student, that's why math professors suck because they never seem to try and put themselves into an "idiots" shoes.

I digress though, there HAS to be some point where you can become fluent in understanding mathematical ideas, but I don't believe that time comes when you're out of highschool, or even when you are doing your bachelors (for me, I've only done second year courses so far and I still find some speech as "foreign" to my understanding).

(This post was last modified: 23/04/2012 09:58 PM by Tetris999.)

I guess it varies from person to person how you learn things then...

(23/04/2012 10:46 PM)ZiNgA BuRgA Wrote:  I guess it varies from person to person how you learn things then...

If you wanted to sum up that post, yeah.

Sorry for ranting, kinda went off tangent to what you were talking about.

(21/04/2012 05:52 PM)ProperBritish Wrote:  big O is just how many operations an algorithm does compared to the size of the data set.
bubble sort for example is O(n^2), i.e. for a data set of 40 it'll do ~160 operations.

I was reading shit randomly, and noticed that this is pretty much totally wrong.

O(n^2) means that increasing the data set by n times increases calculation time by n^2 times.  So if a data set of size X takes Y time, a dataset of n*X takes (n^2)*Y time.

Note that the big O notation only cares about the most significant term, so something like 3n^2+5n+8 will simply be O(n^2), not O(3n^2+5n+8) because that's a giant mess and because lower order terms doesn't matter that much when shit gets large.

I wouldn't say it's totally wrong.  He just left out the bit about proportions.

If you wanted to be pedantic, you could say that O refers to worst case scenarios - some algorithms usually run faster than their asymptotic maximum.

(01/08/2012 11:38 PM)ZiNgA BuRgA Wrote:  I wouldn't say it's totally wrong.  He just left out the bit about proportions.

If you wanted to be pedantic, you could say that O refers to worst case scenarios - some algorithms usually run faster than their asymptotic maximum.

Basically.

Now that I look back on this stuff, I would've rather have learnt these things after I actually programmed.