I need to stop sacrificing readability for smaller amounts of code. What looks good to me isn’t always best for everyone and that’s a fucking tough pill to swallow.

This is something I struggled with at first. I can come up with an elegant one-liner that does something that would normally take several lines, but if another dev can't figure out what the hell it does then it's not good code.

People joke about how you can write unmaintainable code to ensure they can't fire you, but in reality they absolutely would fire you and hire a team of foreign contractors for half what they paid you to rewrite it entirely from scratch if necessary.

@EmberQuill I feel this. I told myself if I just left meaningful comments it’d be enough, but when people come in to make adjustments or add to it I would just get called over to help. Eventually I was outsourced to foreign devs. I’ve learned to just assimilate my style to that of the team and if that means overly explicit statements and creating variables that are only referenced once, so be it 🫡

facts

we're expected to help the reader understand extreme difficulty without using large chunks of code? sometimes, not possible.

although, i will argue that efficiency is important and huge chunks of code can be confusing for non-programmers.