Re: may start a mud: what would you prefer?
 

Alright then. If code is your thing, check out the RPI Engine. It is C-based. In any case it is a very complex code-base and might be good practice to tinker with.

You can get it here:

Re: may start a mud: what would you prefer?
 

I'm sure it would be but, if I do get around to this, that's not the point. The idea is that I'd learn how to design and execute large projects, networking, polymorphism, the list goes on: if I only write a cross-platform network library capable of handling only telnet, I've still learned a lot. Again, don't know if/when this will happen, but that is where I stand on this issue. I care more about the code than the mud, and publishing a codebase will probably be downloaded by more players than I can ever hope to get on a mud anyway.

And for anyone else who is watching this thread, I still hope to possibly work for a mud, and gave this a lot of thought.

Re: may start a mud: what would you prefer?
 

What they said ^

Re: may start a mud: what would you prefer?
 

Camlorn,

If one of your goals is to learn large project management and other advanced software concepts, my advice to you is to start writing code immediately. Don't spend your time buried in books; don't spend your time designing everything; instead, sit down and write code. When you're writing code and you run into a problem that is giving you issues, head back to the books and see if you can find a better way of doing it. Read the books on the side and try to integrate what you find, but keep your focus on writing software.

The thing is, you never really understand -why- certain things are important until you really have an application for them, and you aren't going to understand the drawbacks until you try it. Polymorphism is a good example of both - there are great places and reasons to use it, but there are also reasons to not use it, and drawbacks to using it. Just knowing about polymorphism doesn't make you a great software engineer. Knowing when and where to use polymorphism, which only really comes through experience, is what does that.

There's also a lot to be said for whipping some stuff together in a hurry, then having to debug and deal with it for an extended period of time. That epitomizes large projects - stuff you wrote ten years ago will be at a different skill level than you write today, and it's very instructive to see stuff you yourself wrote a long time ago. Large projects are often less about writing new code and more about making sure everything works properly.

If you could give just one piece of advice, it would be: Code something, even if it's wrong.

Good luck!

-dentin

Alter Aeon MUD