Idea: python game code swap
Reading some people's PyWeek code, I realized I could give them suggestions on how to improve it, and I'm sure someone reading my code could do the same as well. I'm not talking about "best practices" like scalability, docstrings, and unit tests - these things understandably go out the window during PyWeek. I'm talking about avoiding doing things the hard way. Suggestions that would save time during PyWeek and make your code more usable/reliable/readable/efficient to boot. Things like:- a set would be better here than a list
- you've basically implemented itertools.product from scratch
- caching these images would speed things up a lot
So I'm proposing a "code swap", where we write a small game and send it to each other for feedback on the code itself. I'm thinking something like 500 lines of code, depending on your coding style. You'd get maybe a week to write it, so there's not much pressure, and you'd be expected to put some effort into making your code comprehensible. If you think your PyWeek game is coded well, you could also submit that.
This wouldn't be a contest, just a feedback session, but hopefully we could apply lessons learned to PyWeek. Would anybody be interested?
(log in to comment)
The purpose of this code swap is to give and receive feedback on your python code, to help us become better at writing PyWeek games. This is very informal but hopefully we'll get something useful out of it.
Submission guidelines:
"Judging" guidelines:
Game guidelines: