Topic: Programmers' Wanking Corner (Read 20776 times)

Brentai · « **Reply #100 on:** February 16, 2009, 11:13:25 PM »

I found a little bug when I was maintaining my comments.

Now I get >60 fps with ~3000 onscreen sprites.

Presumably I could push more than that but I'm pretty much out of screen space and I think I'm well past the point where it matters. Sufficed to say that XNA can suck my dick.

Kazz · « **Reply #101 on:** February 16, 2009, 11:37:46 PM »

Doesn't sound like a little bug to me.

Brentai · « **Reply #102 on:** February 16, 2009, 11:42:21 PM »

Q: How many Cronos does it take to screw in a light bulb?
A: 3,942 + 1.

After that it sort of crashes out of memory.

Quote from: Kazz on February 16, 2009, 11:37:46 PM

Doesn't sound like a little bug to me.

It was seriously a tiny little thing that I didn't even think was a problem until I started documenting it and thought, "Hey, that's kind of weird, why's it written like that?" I had dutifully typed in the code from another source and, well, sufficed to say the source was doing it wrong.

Even then it didn't seem like an issue until I changed it out of curiosity. That's why I'm so amused right now; this 4x performance increase is purely accidental.

It also demonstrates why I like to maintain my comments so diligently.

Bongo Bill · « **Reply #103 on:** February 17, 2009, 02:41:50 AM »

Why would being a junior developer prevent you from saying anything?

It would be rude regardless of seniority to make a big deal about it being his fault, but at some point you have to explain what was wrong; just say "There was an unclosed quote on line whatever" when an explanation is needed.

Zaratustra · « **Reply #104 on:** February 17, 2009, 03:00:13 AM »

Quote from: Neo-McBrentor X on February 16, 2009, 11:42:21 PM

dutifully typed in the code from another source

omg I haven't typed in code from text since the eighties

Aintaer · « **Reply #105 on:** February 17, 2009, 05:37:59 AM »

Quote from: Bongo Bill on February 17, 2009, 02:41:50 AM

Why would being a junior developer prevent you from saying anything?

It would be rude regardless of seniority to make a big deal about it being his fault, but at some point you have to explain what was wrong; just say "There was an unclosed quote on line whatever" when an explanation is needed.

I can't say anything as in I can't email back and say When you make changes, assume it's your fault. Since the thing was fixed, nobody will ask anything because everything is smooth. Honestly, at this point I'm glad to have a job at all.

Brentai · « **Reply #106 on:** February 27, 2009, 06:38:31 PM »

I got my rotation code right on the first try.

To nonprogrammers or programmers who have never performed soft rotations: this is terrifying.

Bongo Bill · « **Reply #107 on:** February 27, 2009, 07:49:44 PM »

Getting something right on the first try is terrifying, if you really think about it.

Brentai · « **Reply #108 on:** February 28, 2009, 03:25:07 PM »

UPDATE: Turns out I didn't, and was too dense to notice.

God's in his Heaven, all is right with the world.

Bongo Bill · « **Reply #109 on:** February 28, 2009, 03:41:58 PM »

The Spore API is now available to anybody who wants to use it. It grants access to all data about everything people have created, except for the actual models and animations. You still get the pictures, though.

Cyan Prime · « **Reply #110 on:** February 28, 2009, 08:29:35 PM »

As you can tell, I've been really busy lately. Another project of mine is a map editor coded in Java, which will be able to run using Java web start so you can edit maps where ever you are!
This is what I got so far: http://imgur.com/36I1D

Brentai · « **Reply #111 on:** March 02, 2009, 09:03:11 PM »

Ever start building something, get really into it, and when you've nearly got it finished realize that, while cool, it's completely a different thing than what you set out to build in the first place and now you've got to pack it away in your library hoping that the day will come when you need it and that you'll actually remember it's there when it does?

Kazz · « **Reply #112 on:** March 02, 2009, 10:02:59 PM »

I actually realized today that I have never stopped midway through programming something. Everything I've made, for class or otherwise, I've made in a marathon session from start to finish. This habit meant staying up for 36 hours on two seperate occasions during finals last semester.

This also means that I can not get myself to start a project unless I'm prepared to stay up until it is finished. This is causing problems.

JDigital · « **Reply #113 on:** March 03, 2009, 04:00:26 AM »

I've done something similar. I once stayed up until 11am writing a PHP script to calculate D&D 3E monster advancement. I went to bed, woke up that evening and continued on until noon.

No idea where that script is now.

The trouble is longer projects. What happens when something is going to take you a few weeks? Nobody can stay awake that long.

Brentai · « **Reply #114 on:** March 03, 2009, 11:46:41 AM »

Set a time period where you will work on the project. For me, it's 5-7 PM.

Start working at the beginning of that period.

Stop working at the end of that period.

NO. EXCEPTIONS.

Kazz · « **Reply #115 on:** March 03, 2009, 03:54:47 PM »

Two hours is NEVER ENOUGH.

Brentai · « **Reply #116 on:** March 03, 2009, 07:00:41 PM »

Ahem.

A set time per day. Sorry if that was unclear.

If you can't get in and out of the groove in that time period, well, learn.

(Obviously two hours doesn't exactly work if you've got a looming deadline or something, but the idea should be the same. You'll simply set yourself up for minimal returns if you overdo it.)

JDigital · « **Reply #117 on:** March 04, 2009, 01:06:57 AM »

But Brentai, that would require discipline. If I had that I'd be in a full-time programming job like you, and not intermittent Wordpress-monkey work like me.

Catloaf · « **Reply #118 on:** March 04, 2009, 05:55:48 AM »

I know I never stop working until the specific problem I'm working on is solved. But if all I have to do is easy shit that isn't all that important, I may just working on it mid-line. Well, unless I can't fucking figure out what the hell is causing a certain error or how the hell I implement something without fucking things up. Then I force myself to stop and come back to it later so I can look at it with a fresh mindset.

Brentai · « **Reply #119 on:** March 04, 2009, 11:15:48 AM »

Quote from: JDigital on March 04, 2009, 01:06:57 AM

But Brentai, that would require discipline. If I had that I'd be in a full-time programming job like you, and not intermittent Wordpress-monkey work like me.

...uh, exactly what do you think I do, JD?

(As an aside, I am the least naturally disciplined motherfucker on the planet, which is why I feel I can speak with some authority on how to get past your usual productivity blocks. Also, everybody on the fucking planet should read The War of Art by Steven Pressfield.

Seriously. Do it.)

News:

Author Topic: Programmers' Wanking Corner (Read 20776 times)