I like the idea of selling out the oldies.
But what i really would like is to get the games in a some what decent condition.
Clean up the games and machines (who likes buying anything covered in 2 inches of dust). Try to get original copies of the boxes (make duplicates or replicas) even replicate the goofy promotions that obviously are outdated.
Sure it might be a little bit more expensive, but as a somewhat game collector thats what i buy the game for... The box and the manual.
I've just recently had something like this happen. One of the programmers left and his section of code was dropped in my lap. I was the one to continue maintanence.
The code worked but just barely and there were a lot of issues with synchronization and scalability.
The first thing i did was make the code style consistent(braces, variable declerations, header files, It was a mess). Noramally i don't care what style a person uses as long as its consistent.
Next i located the bugs and problem area's. Most of it was just needed error checking and a few synchro locks. I then made some conclusions about the code and put them in terms the upper management could understand. Does it need a complete rewrite, How long is going to take to fix or cludge, if we leave it how will it affect the system and when, How it will delay the project. This project has to do with money which is always a great thing to attach, it scares the bigwigs when you can relate bugs to cash.
Next I started at the begining of the of the section and worked through the process. Rewrote the sections that broke but left his functions and procedures alone as long as they worked.
The point is that if it's about to break, then rewrite what you have to but use whats there even if the function is poorly written, as long as it works.
Slashdot Mirror
I like the idea of selling out the oldies.
But what i really would like is to get the games in a some what decent condition.
Clean up the games and machines (who likes buying anything covered in 2 inches of dust). Try to get original copies of the boxes (make duplicates or replicas) even replicate the goofy promotions that obviously are outdated.
Sure it might be a little bit more expensive, but as a somewhat game collector thats what i buy the game for... The box and the manual.
I've just recently had something like this happen. One of the programmers left and his section of code was dropped in my lap. I was the one to continue maintanence.
The code worked but just barely and there were a lot of issues with synchronization and scalability.
The first thing i did was make the code style consistent(braces, variable declerations, header files, It was a mess). Noramally i don't care what style a person uses as long as its consistent.
Next i located the bugs and problem area's. Most of it was just needed error checking and a few synchro locks. I then made some conclusions about the code and put them in terms the upper management could understand. Does it need a complete rewrite, How long is going to take to fix or cludge, if we leave it how will it affect the system and when, How it will delay the project. This project has to do with money which is always a great thing to attach, it scares the bigwigs when you can relate bugs to cash.
Next I started at the begining of the of the section and worked through the process. Rewrote the sections that broke but left his functions and procedures alone as long as they worked.
The point is that if it's about to break, then rewrite what you have to but use whats there even if the function is poorly written, as long as it works.
playing for money sounds like it could bring the bots out of the wood work.
:)
Although it could be interesting to see a bot war in a FPS