Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
I'm not a pirate.
Ganzalf1543yBeen there, done that. We had a project to deliver in 3 months with technology no one was aware of. We did the best we could. Is somehow works, but the code is freaking bad, smelly. Thank god I no longer have to look at it. First thing I did was to commit an .editorconfig file.
I work on a enourmous electron project that does use a C# Backend with custom database, Vue and Vuex. Also i was the only fullstack web dev so i had teached JS to our junior who only knew C# and Java so basically the same potential for unmaintainable code.
But i enfored very strong linter policies for everything HTML CSS JS JSON JSdoc comments and even SVG, and kept making codereviews with the junior. And also i got codereview from our C# devs on how to handle the backend properly. This is where our Junior also shines when we implement new bridge functionality since we both are good with the language at each end.
So how should you keep code maintainable? I would say use every tool available, encourage developer to benchmark functions, make use of unit tests and especially reject every commit that does contain lint errors.
Character limit hurray...
Hope this helps if you need a example setup i am currently building a electron template that enforces all rules above, you can use most settings for general js projects. Also i always added a why explanation to the given settings. Follow me on github @hammster since the public release date is still a bit away.