Am I a freak?

[thistlechaser]

Or just a non-pro coder?

I needed to make some new code tonight for the MUSH. Not the most complex stuff I ever made, but not just a couple simple commands strung together. However, the MUSH is down.

There's no reason I can't write code in a Notepad file, then paste it in when the MUSH comes up... but I can't work that way. I like to write it piece by piece, and make sure each piece works before adding it into the whole and moving on -- that way there's better chance that the whole thing will work at the end.

Bah. Nowadays there's so little call for me to code! I was excited to actually have something to do tonight. I know just how I want it to work, I just have to write the pieces and then put them all together...

(I realize I'm missing an "angry" icon. This is funny in that when I started making new ones, they all were angry ones, so I made other ones as well. Then I liked those other ones better, so I used those...)

ETA: There we go, new icon! Pirate kitty is gone, as much as I liked it. It was between the pirate kitty and the "men hugging" one, and there'd be more use for the hugging one.

Comments

[kirbyk.livejournal.com]

That's not an unusual thing at all. I've had to occasionally do the 'monolithic' code style, where I write a lot of code before I can test any of it - and it's a terrible way to do it. A lot more bugs, and even worse, the same mistake I make once, I tend to keep making.

Whereas, in the preferred development environment, I write a small bit (like a function) and test the bejeesus out of it, and then move on. Then, when I have to write some other similar bit of code, I have a good starting point. And the vast majority of things a pro coder does are very similar to something they just did.

Not always possible, particularly when you have to wait on key bits from other people (like, say, you're writing db access routines, and the folks setting up the db are still working on getting the hardware online) and so (at least on a job), you have to make due or get horribly behind.

Some people do work better under different models, but this one is certainly valid. (Computer Scientist geeks would probably call it 'Rapid Prototyping' methodology.)

If it happens often, you could probably set up a MUSH server on your PC, with a wizbit, for code testing. Doesn't help much if you're interfacing with other existing code (unless you back a lot of stuff over to your offsite testmush, which isn't a shabby idea for a number of reasons), but at least your creative window isn't stifled.

[thistle-chaser.livejournal.com]

Huh, that's good to know. Thanks for the insight!

[daltontrix.livejournal.com]

And lo, a flood of new little commands rained down upon the people.

Remember +rps? Now we have +oe! Flip a coin, play Rock Paper Scissors, or now Odds and Evens for all your decision making needs!

Remember the days where +attempt was just hit or miss? Forget them! Now you get a full report of where the attack hit, how hard, and how horrible and gruesome the injury was! Complete with a halftime show!

See, there are plenty of things to code! They're just horribly cumbersome!

[thistle-chaser.livejournal.com]

*laughs*

Okay, smart guy, get to work on those things! I'll check 'em when you're done!

;)