LogFAQs > #979562751

Yellow posted...

I've mostly stuck to the formatting that you used last time since I really liked your style of fitting as much stuff on the screen as possible.

that's kind of it yeah; it's that you should justify usage of vertical space. sometimes using more vertical space is ok to keep things readable, but sometimes things can be compressed and still be quite readable and maintainable. and some people do things that waste vertical space not realizing how much that hurts readability. but there is a middle-ground somewhere.

we don't have to switch to 3 spaces just for me. the challenge of "how do I use different tab sizes in different projects" is one I haven't dealt with before and something I should learn. (my switch to 4 yesterday made it work today since I have the same JetBrains account in both places and I guess it saves the setting to the cloud or something. (doesn't matter, it's easy to change the setting))

the challenge for me right away is that seeing your code there are 100 different style decisions that I would make differently and I have to decide whether I should change the code or myself to proceed. (FYI I am not always right; in fact I try to actively be in search of places where I'm wrong.)

I will try to make simple commits and merge often.

my approach lately is to do each "task" on a separate branch. branches are rebased onto master if master grows, and when a task branch is finished it is merged into master with no fast-forward and then deleted. this results in a very clean commit history, though the commits will not be in 100% chronological order (each branch is, but each branch is listed whole even if it was really concurrent with other ones). I'm not 100% sure how this translates to github.

I'm now remembering how much effort it takes to communicate these kinds of things through text.