Programmers that can't do shit

In my experience, they manage by leeching of team based work and getting scrapping passes in theory based work and exams.

I'm one of those people you speak of....... please don't [flaming] me too harshly.
...at least you two don't work together (at a real job that is).

I went to school with a guy, fourth year, FOUR YEARS OF DIGIPEN, that asked me how to do a dot product. And he graduated with me. And is making more money then me. I just cried into my keyboard.

Quote:

Original post by Alpha_ProgDes I'm one of those people you speak of....... please don't [flaming] me too harshly. ...at least you two don't work together (at a real job that is).

I am not [flaming] you, but I have several questions, considering that you are into game development. I am into game development because I like making them, emphasis on "making". So since the beginning, I learned to start creating something from scratch. Open notepad/VS, start typing. Save, compile, run, and debug. When I get stuck, then I look into other people's code for inspiration, but I still try to reimplement the whole thing on my own, because 90% of the time I am making a different program, so obviously I need to redesign their implementation. The rest 10% is when I am reusing their code, but I still have my own code to supplement it.

So, If you do, how do you create your own game?

The people you're talking about are the people who get the assignment and first 5 seconds of having it, post all over every programming forum they know for the answers.

Quote:

Original post by cherryhouse The people you're talking about are the people who get the assignment and first 5 seconds of having it, post all over every programming forum they know for the answers.

That's some of them anyway. The lazy ones.

Theres also those who just-dont-frickin-get-it! That doesn't mean they're stupid (at least the ones that I know). It means that they won't just stop and listen and think for a second. Like Jessica Simpson with the tuna can. If she'd have stopped and thought about it for four seconds instead of asking the question, she'd have noticed the cleverness of the name. Instead, she's a laughing stock. Many of these programmers are the same way: they are too busy trying to get it to just stop and get it!

Kill him!!!!!

Yes, and all of them will graduate and BS their way into jobs making more money then you do spending all of their time there fucking up the code base as much as possible. Then you'll get hired and paid less then them only to end up realizing how fucked up everything and how much shit you're going to be cleaning up for the next year or two.





Yes, I hate my job.






Some days.

There was someone in my old department at my job who had no clue how to do a damn thing. We are in a department where we're supposed to solve these "problem tickets" opened by our clients. Well she requests for one of these tickets to be opened for someone else to solve because her "computer keeps making a beeping sound"!! All it took was to turn off the damned PC speaker! omg, so irate...and she got a promotion soon after that (among many other similar ridiculous things).

This is a bit off-subject, but a similar vein:

In high school, we had a "typing" teacher who was supposed to be the one that got us comfortable with computer use. One day in his class I was readjusting my monitor (trying to align the screen with the obnoxiously complex interface that plagues most monitors). At this time, the printer starts acting up, making noises and printing big black marks.

He looks over at me, see's me fixing the monitor, and accuses me of hacking into the printer through the monitor dials.

Classic.

Quote:

Original post by alnite Quote: Original post by Alpha_ProgDes I'm one of those people you speak of....... please don't [flaming] me too harshly. ...at least you two don't work together (at a real job that is). I am not [flaming] you, but I have several questions, considering that you are into game development. I am into game development because I like making them, emphasis on "making". So since the beginning, I learned to start creating something from scratch. Open notepad/VS, start typing. Save, compile, run, and debug. When I get stuck, then I look into other people's code for inspiration, but I still try to reimplement the whole thing on my own, because 90% of the time I am making a different program, so obviously I need to redesign their implementation. The rest 10% is when I am reusing their code, but I still have my own code to supplement it. So, If you do, how do you create your own game?

Since you went from several to one [smile] question, I'll answer. [grin] I was one of those people who didn't get it. I'll read and read, ask questions, tried to implement and got either unsatisfactory result or nowhere. So I stopped and school went along with it (well it's easy when you're sick all the time and fall back on IT). Now suddenly, I get it. I'm rereading all the books and e-books I have. Going over school books and game programming books. Downloaded the VS EE and the tutorials. Unfortunately, I'm wired differently from alot of other people here. I'm not too technical, so I need tutorials that explain things in a very plain way, then work up slowly to technical (yeah I know I'm screwed). But now I read and read and practice. Write things on paper and have a general "direction" before I program. For complicated things however (raytracers and anything similar in complexity), I'd be the dumbass you work with "so how do I do this?" Gimme some direction or a place to start and I should be able to pound something that's workable though [smile]

I think to be good at programming, you just need to have been playing with lots of Lego's during childhood :)

Programming is not usually the core of the problem, it's just the problem solving part. I think these people would be equally useless at other task that require planning, structuring, design, and sometimes thinking out of the box. But they just wouldn't know where to start, nor how to finish (the most difficult part in my opinion). That can be learned, obviously. It's just methods to learn, and developping the right brain muscles until it becomes second nature. Like Lego's :)

Man, I played with Legos and I still can't program worth a damn. I can't even figure out how to open a program in a manner that will allow me to hack out my tiny bit of programming knowledge and run it.

So, I do art now [grin].

oliii, made me feel worse. i was never good with legos as a kid. [sad]

Hehe.... I LOVE Legos!! But I am still in the process of learning C++...

in my CS class my friend, who doesn't even know how to open a program, got the highest grade in the class on a test by guessing... The test involved memorizing something about a marine biology program no one cared about. *sigh*

Yeah, I played with Lego all the time when I was a kid,...

I'll admit I suck at actually programing, but I am fairly good at working out design docs. Well, i think I am. Anyone want to give me a few million to hire a team to see if they can actually make something out of one of my docs?

Integrating vs. reinventing the wheel.

I think being able to reinvent the wheel if necessary is good, but eventually integrating will win. We must stand on the shoulders of those giants that created really useful libraries and suites.

I worked with people that only could do shit. That's much worst.