Frontend coding guidelines at my company https://gist.github.com/shovon/93960e4240fabd184150f441a4d3533e
#TypeScript #Frontend #React #Prettier #ESLint #CodingStandard #Programming #Coding #SoftwareDevelopment
I would enjoy seeing the codebase to see the impact of these guidelines. What do you like or dislike about them?
@techt@lemmy.world bear in mind, even though I’m the one who came up with these rules, I admit, the code looks incredibly ugly, IMO.
That said, the goal isn’t clean code; it’s functioning code.
There’s code with obviously no bugs, and then there’s code with no obvious bugs. We’re trying to minimize the latter.
I respect that – kudos for putting your own written rules out here for everyone! After working on a mid-sized? codebase for awhile I think my top priority would of course be functioning code, but right after that: maintainability. As people come and go and you have a Thesius’ Ship situation with your engineering team, readable and maintainable code now pays dividends later. How long have you been working on your codebase? Do you have trouble onboarding new people? I do think Clean Code™ is overrated – even after having read the book – so I agree with you there to an extent.
On the topic of readability: we’re optimizing for searchability.
On the topic of maintainability: we’re optimizing for deletability.

