Why do you like programming?

Post Reply New Topic

nothing like the satisfaction of presenting work well done,
that said most of what i do program has no real purpose, except for the learning and the fun.

I claim that that's the best purpose

And being judgmental is for everyone.

You know you're a geek when you learn C++ for fun.

Hah!

Real men refuse to learn anything more than assembler and C.

I know binary if that counts.

I worked in the industry for years. It used to stimulate me so much and is far more rewarding seeing your program work than the money they give you to do it (and that was a lot).

It is a cool and funky thing to do, even the sad NT business people want to get in on it but their brains are no good for it most of the time.

Because watching a computer carry out tasks on its own is one of the most fricking awesome things ever.

It's like playing a game. A sandbox game, where the only rules are pure logic.

I LOVE IT.
It has everything I love.
Compatibility, you can do it on almost anything.
While sitting at the compiler, looking at it... To think you can do absolutely anything with it is pretty stunning.
The logic, its definite, everything you code into its pure logic. It goes one way and no other.
Problem solving, its awesome, you can spend 3 hours writing 50 lines of code properly and making it do awesome things and solving problems.
Its something I can really sink my teeth into.

I know most of the modern languages, but these days I do most of my work in two languages:
x86 Assembly: A program is a series of instructions. An operator, then operands, no exceptions.
Python: Again, nothing breaks the rules, and everything is easily categorized. I have what some call an irrational obsession with categories.

Mind over Matter. I like Using The Force.

ruveyn

I think of programming as an extension of art.
I started drawing pictures, then I created sculptures, then I did 2D & 3D computer animations.
Programming allows me to take things well beyond simple animation into full interactivity and simulation.

65xx was interesting to fool around with. But trying to explain it to kids who are in uni today often results in exploded head debris flung around the room.

("What? There were just 3 GP registers to work with?? Why 3?!?! Everything had to share 256 bytes of stack?!?! What the deuce is zero-page addressing?!")

Yeah, there's less room for doing interesting things. Necessity's the mother of invention, and most situations bring more computing power than necessary for a given problem.

Generally you just stuffed your code at $C000 and stored/loaded the registers on fixed memory positions to overcome that problem.

Programming is not that fun since you're spending 95% of your time debugging

^^ Might I therefore humbly suggest that you're doing something wrong?