This is so true. A month or two goes by and it is like learning certain pieces of code over again.

That’s why it’s so important to no not neglect readability.

@Lensflare I see people write chained function shit with map (or other commands like it) with embedded functions and wonder how they wrote it in the first place. Just the mass of symbols all in one place causes fatigue. I suppose someone could get used to that. But I don't want to.

@YourMom yup, definitely. It’s horribly unreadable when you are not used to it.

My ayes instantly translate chained FP functions into a kind of pipeline where data is flowing through and is being transformed.

Readability is subjective and if you are the sole dev, you should at least write code that is readable for your future you.

@Lensflare so not agree, people just need to read . People write code like if the person that comes after them is retarded. Most cases, you're the one yourself working the next time on it.

@retoor snek won't let me login. Just goes to login screen after border on login turns green. Is snek broken?

I remember losing save data from 'Final Fantasy VII'. I was on the last disc after having played the game for some 80+ hours. When I inserted the memory card w/ the save into the console, the memory card just wouldn't show up.

The backup memory card worked fine but the idea of starting over was so bad that I chose to start playing other games.

Years later, it turned out that the original memory card w/ my save worked, but the connectors were worn out a bit, so you had to push it in fully into the slot, then push it slightly from the side so that it would be connected at an angle.

I was very excited to see my old save still working. I booted the game, loaded the save, but after such a long time I had no idea where I was or what I was supposed to do. Eventually I started over...

Anyway, that seems like a similar situation to writing a piece of code that you can't understand in a few months.

@Lensflare if I neglect readability (more like "total it on purpose") I can read more of the code faster because it's more concise and actually captures my attention

I always remember what my code intends to do.

But that's because I've developed an inherently pragmatic approach, which I guess is unique to me.

If I'm in a shared environment with people I know can't follow (juniors) or use some obscure math IT people wouldn't know (I'm a physicist, which is not mathematician, but for practical purposes, close enough), I'll leave comments.

That's the key point. Don't comment code. Code is always readable and predictable. Document *intent*.

@YourMom Huh now? I'll check immediately. There is a new proxy in between. Hmm. Wait a sec.

@YourMom @YourMom Fixed, faster than light. It was the proxy server not handling redirects well. Removed it, sad, i loved that thing. It kept bandwith statistics like https://retoor.molodetz.nl/stats but in a much nicer and detailed way! Tue proxy server of molodetz is made to ddos the 'hacker' dude when it tries to create a spam repository :P Just to crash his bots. It keeps sending data.

Edit: i did not notice the bug, people were still chatting but they were still logged in i guess.

@retoor it logged in this time

@YourMom of course, snek comes with premium support! As much available as an amphetamine addiction can handle, almost 24/7! dfox is probably a weed smoker.

If your thought process is consistent, old code should read more like a good book instead of your car's user manual. You should know how 80% of the code works before you even read it because you should be able to expect what your past self would have done when solving the problem the first time.

Some code, this is just unavoidable. I hate reading boilerplate and trying to figure out where the framework expects me to shim in some random/specific configuration value.