[LHN91]

Realizing how rusty my coding skills are at the moment. Relatively simple assignment that I've just more or less finished, but god is it ever a kludgtastic mess with almost no error handling. I would do a major refactor and clean-up of the code, switch to a more modular style..... but it's due in 3 hours and I really don't feel like spending all of those hours trying to refactor working code for an extra percent or two. Documentation writing and submission time it is, then.

[Klaustrophobia]

error handling is for programmers who introduce errors into their code. 

[z64555]

error handling is for programmers who introduce errors into their code. 

It's also for people running the program on a multi-process OS, and don't really want to shut down the entire thing...

LHN91: What language are you coding in?

[LHN91]

Just straight C on Linux. Like I said, it was just me being rusty and not bothering to properly lay out my code and modularize in the initial design.

[z64555]

straight C... error handling...

oh yuck. 

[Klaustrophobia]

i thought i was gonna be a programmer up until 10th grade when i discovered physics and engineering.  then i thought i'd get a CSC minor for giggles since programming logic is piss easy for me, and it's just a matter of learning the language.  until my 2nd level class, when i learned i was expected to run test cases, error handling, and comment ****ing everything, and i pulled the eject handle.  didn't help that the professor, who was supposed to be a well-respected, intelligent guy, was a complete ****ing moron.  i don't want to be anywhere near an industry that can think highly of a guy like that.

[CommanderDJ]

You get morons in every industry.

[General Battuta]

i thought i was gonna be a programmer up until 10th grade when i discovered physics and engineering.  then i thought i'd get a CSC minor for giggles since programming logic is piss easy for me, and it's just a matter of learning the language.  until my 2nd level class, when i learned i was expected to run test cases, error handling, and comment ****ing everything, and i pulled the eject handle.  didn't help that the professor, who was supposed to be a well-respected, intelligent guy, was a complete ****ing moron.  i don't want to be anywhere near an industry that can think highly of a guy like that.

Damn dude, way to put down everybody in CS.

[z64555]

I somehow got drunk off of chocolate syrup. wth? 

[Colonol Dekker]

Probably a sugar rush.

[z64555]

Probably a sugar rush.

Nope, nope. Definitely not a sugar rush.

[Polpolion]

i thought i was gonna be a programmer up until 10th grade when i discovered physics and engineering.  then i thought i'd get a CSC minor for giggles since programming logic is piss easy for me, and it's just a matter of learning the language.  until my 2nd level class, when i learned i was expected to run test cases, error handling, and comment ****ing everything, and i pulled the eject handle.  didn't help that the professor, who was supposed to be a well-respected, intelligent guy, was a complete ****ing moron.  i don't want to be anywhere near an industry that can think highly of a guy like that.

Damn dude, way to put down everybody in CS.

Personally I don't mind, and I don't think any other CS student would. Almost comical, actually. 2nd level programming, at UM at least, is just a class designed to weed out students that CS is a bad fit for anyway. If you think testing, error handling, and documentation are beneath you I'll just say good riddance. It sounds like Klaus would have be better off with a minor in computational mathematics. (inb4computersciencevscomputationalmathematics  )

[Dark Hunter]

If you think testing, error handling, and documentation are beneath you I'll just say good riddance.

Oh hell yes. The last thing the programming industry needs is more people who don't comment their code.

[Nuke]

i thought i was gonna be a programmer up until 10th grade when i discovered physics and engineering.  then i thought i'd get a CSC minor for giggles since programming logic is piss easy for me, and it's just a matter of learning the language.  until my 2nd level class, when i learned i was expected to run test cases, error handling, and comment ****ing everything, and i pulled the eject handle.  didn't help that the professor, who was supposed to be a well-respected, intelligent guy, was a complete ****ing moron.  i don't want to be anywhere near an industry that can think highly of a guy like that.

Damn dude, way to put down everybody in CS.

Personally I don't mind, and I don't think any other CS student would. Almost comical, actually. 2nd level programming, at UM at least, is just a class designed to weed out students that CS is a bad fit for anyway. If you think testing, error handling, and documentation are beneath you I'll just say good riddance. It sounds like Klaus would have be better off with a minor in computational mathematics. (inb4computersciencevscomputationalmathematics  )

i kinda think the whole cs crowd is kinda spoiled. multi-gigahertz, multi-core processors awesome floating point units and large amounts of ram, and libraries that handle pretty much everything for you. its a hell of a lot more fun writing code on something that has nothing. no fpu no multi core, no gigahertz, and where including a library will waste all your resources. so ive had a hell of a lot of fun with embedded systems, microcontrollers and the like. it also meshes well with my electronics wizzardry.

you really do more computer sciencey things when your focus is not set on application development. such a programmer need not worry about their math library being sub-optimal in a certain situation and there is no concern about use of basic math operations. you just use what you need when you need it. like how does one do scaler operations without an fpu or even a hardware multiply instruction.  you really start appreciating things like shift instructions, which come in handy for a lot of fixed point maths. and when you have to make your own trig functions when your math is all binary fixed point. for example when dealing very low level code like that it helps to completely abandon concepts like degrees or even radians, and start dividing into 2^8 or 2^16 ticks per rotation (the latter usually being in an 8.8 fixed point format). application programmers dont think about this stuff till they run into a problem. and even thin just work around in instead of replacing their libraries with custom code.

[deathfun]

I somehow got drunk off of chocolate syrup. wth? 

...that wasn't chocolate syrup...
...at least not just...

[Nuke]

If you think testing, error handling, and documentation are beneath you I'll just say good riddance.

Oh hell yes. The last thing the programming industry needs is more people who don't comment their code.

i think i comment my code more out of necessity than for readability. i lack the photographic memory neccisary to be a good coder. i can write code and design even a complex system. but if i go do something else (which i do a lot), i will have an insanely hard time getting back into it. so i might have a comment every third line so i can follow the code. like im very bad at naming variables, so 9 times our of 10 there will be a comment next to it explaining what they are for. i know ive had some programmers call my code overcommented, but its better than no comments at all. i look at their code and your luckey if you get a comment every other function. like they expect everyone that reads their code to be as good or better than they are. assuming that every other coder speaks c++ fluently is a bad assumption. rest assured that any programmer will be able to parse the comments at a faster rate than the code. and they certainly make navigating a code base much easier. having one comment that says what the next 10 lines of code do is a real time saver for me. i dont get why so many coders dont like commenting their code.

[Androgeos Exeunt]

I somehow got drunk off of chocolate syrup. wth? 

Any relation to this?

[10:33]   <z64555>   Whoa, hello. Aparently there was something more in that chocolate syrup I made
[10:33]   <z64555>   and I have no idea what that might be

Seriously, what did you put in there? Or did you stir it too few times?

[Klaustrophobia]

believe me, i get it, and i don't think it's beneath me.  i just despise doing it.  that's why i left.  for the kind of programming i do now, small programs for personal use to automate tedious computations, it's not necessary.

as for the professor, this guy was invited to speak at symposiums and crap.  he asked my group to use one of our 'projects' (which was just a stack of flashcards) to present.  i don't recall him ever writing a single line of good code.  his TA fixed everything he gave us.  and he gave us a physically impossible assignment.  we could either meet all the assignment's criteria of what classes to use and how to use inheritance and whatnot, or we could write code that worked.  not both.

[Aardwolf]

I don't suppose it's possible to mistake a caffeine high for being drunk, is it?

I opened a bottle of chocolate syrup recently that had a foul after-taste... idk wtf was wrong with it. I've gotten similar from Giant brand chocolate syrup, but never from Safeway brand. So I guess it's not the recipe per se, it's the quality control...

[Polpolion]

believe me, i get it, and i don't think it's beneath me.  i just despise doing it.  that's why i left.  for the kind of programming i do now, small programs for personal use to automate tedious computations, it's not necessary.

as for the professor, this guy was invited to speak at symposiums and crap.  he asked my group to use one of our 'projects' (which was just a stack of flashcards) to present.  i don't recall him ever writing a single line of good code.  his TA fixed everything he gave us.  and he gave us a physically impossible assignment.  we could either meet all the assignment's criteria of what classes to use and how to use inheritance and whatnot, or we could write code that worked.  not both.

Yeah I had the same kind of prof for my freshman design class. He spent half his time talking about his family, I'm pretty sure he was sexist, and he forced us to write our project in 'phrogram', which if you google it you can probably tell how frustrating it was for someone that had already been programming for a few years. What it boils down to is that they just don't care, so I could hardly condemn the entire field. Plus I had already declared my major and I was too lazy to switch to aerospace.