Re: python spaces, I still don't get how it works.
Again, let me reiterate, after college style is *not* optional anymore. If you think you have bad style, you need to fix this.
Sighted programmers are different from us. I don't think most blind programmers get that, not right away. Style feels like this stupid bullshit thing that doesn't matter, but that's because to us what really matters is things like "how far do I have to scroll". Blindie coding style, if I had to give it a name, is narrative--we're telling a story with our code, so we i.e. introduce variables right before they're needed, things like that. Sighted coding style is pretty universally "do the important parts jump out at me visually", which is where thins like all variables at the top of blocks, indentation, etc. come from, and if they don't your code is actually not just unpleasant, it's incomprehensible. Style guidelines for wherever you end up working exist so that someone who has 20 things to do today can review your code quickly because it looks like all the other code they have to review today, without reverse engineering your style (and god help us all if it's not at least consistent).
So how this will go for you and many others on this forum is that you'll get as far as your first job or your first contribution to a major open source project or something, and then you will get slapped down for bad code style and they won't make exceptions because you're blind (nor should they, this is *not* a place you should have to use accommodations, nor is it fair to your sighted colleagues if you just keep giving them a visual spaghetti pile to review).
For my personal projects (i.e. Synthizer) I've started making the style "whatever the formatter does" and coding that way, and that's fine as far as it goes. But you can't actually just apply formatters whenever and have to be harmonious with what's already there because otherwise it breaks the entire repository history when you rewrite every file. Then everyone has to reclone and fix all their in progress work to match the new style, and all the tools where you can say "what changed since last month" when a bug happens stop working since what changed since last month is every single file in the codebase.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
