lol freelancer read this in a day, learned the basics and some advanced stuff as well.
didn't know a day was years and years of education.
http://www.cplusplus.com/doc/tutorial/
lol freelancer read this in a day, learned the basics and some advanced stuff as well.
didn't know a day was years and years of education.
http://www.cplusplus.com/doc/tutorial/
Learning to program = / = programming properly.
Programming is like math and science. After you learn the basics and move onto more advanced stuff, you find out that the stuff you learned before was wrong, inefficient, or inaccurate.
uh... its not just math buddy, it's about structure and order and making sure you do what you want in the least yet most efficient way.
it only involves math up to algebra really...
and how it involves science? unless you are talking about reverse engineering, then that's completely different.
He was comparing the learning process of it to that of math and science. He wasn't talking about the math/science involved in it.
No not really, there's a lot of math behind algorithms to create efficient code.
http://en.wikipedia.org/wiki/Big_O_notation
Programming is mostly logic. Math plays a part, but they're called programming languages for a reason. Big O notation is used in computer science to basically measure the efficiency of a data structure to handle a procedure (sorting/adding/deleting); e.g. O(1) means that the procedure's efficiency is constant, O(n) means that the procedure depends on the amount of data in the structure, etc.
I swear I have some sort of learning disorder because every time I tell myself I'm going to learn programming I go ride bikes
Programming is a lot more than logic. You have to conform to conventions which you just learn over time.
The reason OS is written the way it is, is because partially Korn uses common naming conventions and on the other hand implements his own. Naming conventions are mostly ignored by beginners and that's why most of the code looks like crap in the beginning.
Not to mention having background knowledge allows you to write much more efficient code. You could use a 64-bit data value (e.g. int64_t) for iteration purposes, but when you optimize your app to run in x86, the iterator cannot be stored inside a single general purpose register.
There's a lot of logic behind algorithms to create code, be it efficient or otherwise. Big-O isn't a part of programming, it's a part of computer science. It's theory. It uses math and math notation to describe structures and the code surrounding them. You can use other constructs for modeling data and information for use in computer systems, eg object entity relationships or plain old flow charts.
Moving on to "more advanced" stuff doesn't mean what you learned or were doing earlier was wrong, inefficient, or inaccurate. Programming (or maybe software engineering is a better term in this case) is about solving problems, be it purely logical, mathematical, or something in between. You use different tools to solve different problems. Some tools may provide a cleaner solution to a problem, where another one doesn't. Doesn't mean that other one is wrong, inefficent, or inaccurate. It just means it's not the right tool to solve that problem. You can use the wrong side of a hammer to nail something, but it's not the best tool for it. That's not what it's made for. But boy, when you need to remove a nail from something, it sure can work wonders.
Really, programming is only a piece of the computer science pie. Anyone can shit out code and then say they program. They're known as hacks, not actual computer scientists.
edit: sniped by Pat
Programming skills are reflected in forum posts:
Korn uses a profound language, italics to highlight keywords and uses enum(erations) where can.
I on my behalf did a half arsed job of a post without any structure at all.
This guy has obviously no clue how to program:
![]()
There are currently 3 users browsing this thread. (0 members and 3 guests)
Bookmarks