Diary 2019-04-28
I continue to angrily follow a tutorial that seems to have somehow gotten worse since the last time I looked at it. The diffs are just making less and less sense, it's ridiculous.
Anyway, that level of complaining in mind, I'm considering trying to make my own tutorial based on my efforts to rewrite and update this tutorial.
What I'm thinking of those efforts so far:
- invoke, pyenv, and pyenv-virtualenv are nice
- I ended up wanting to do some stuff to nox that I'm not sure what the preferred way to do it is; or rather, I kind of don't want to do it the way I suspect is the preferred way.
- I'm still getting my footing with Coconut. I don't think I've fully achieved a balance between "just type in Python code!", "it's got all these fancy extra features!", and "but you don't have to use them in any given situation". Also, it seems like sometimes the parser handles things so badly that it can only tell me that the error is on a particular line, and not anything about what's specifically wrong.
Thinking about what my own take on any of this would probably look like:
- Pages on GitHub, probably
- All diffs would be actual git-formatted diffs from actual repo state.
- I'm actually kind of imagining that maybe this would be done through the medium of PRs and commits. All like "here's what it takes to get from this game to this, slightly more sophisticated, game". Probably not actually workable, though.
- Not sure how I'd handle stuff like refactoring, since I'd be writing this for people like me, and a lot of my reactions I remember were along the lines of "Just write it correctly the first time, come on."
What I really need before I can plan the idea in earnest is to go through things again, and try to get further. (Part of the trick of this is that Coconut provides features comparable to Structured Data, more or less, so I've just, you know, got them, and I don't have to context-switch to developing them.) Having worked through this stuff once before sort of helps, but nowhere near as much as I would have expected. Not only has the tutorial been updated in ways that don't completely make sense, but the tcod library has been under active development, complete with deprecations, and my own code style has changed somewhat since I stepped away. The overall effect is like a tripod with a pogo stick duct-taped to each leg.
Anyway, I'd better get on this. I'm not even through Part 3 yet. Get on this later; I'm tired now. Good night.