Comments by "Charles M." (@charlesm.2604) on "Perl in 100 Seconds" video.
-
94
-
4
-
@biskitpagla Linting isn't helping to write clean code though, it helps to share a set of conventions on a project. Consistency of conventions is just one of the many elements that form a clean codebase, outside the scope of linting I can think of:
-naming of variables, functions and functions parameters
-functions only solving one issue, being concise and short
-comments (JDocs format)
-avoiding "magic" code as much as possible (ternary, lambdas, etc...)
-using most familiar design patterns in the team
-white spacing classes properly
-avoiding referencing functional code from different files, reserving unique file exports to objects (classes, enums, interfaces, etc...).
For example linting wouldn't mind those 2 approaches yet the second is clearly cleaner than the first:
1) public run(str: string, o = this.default): string []
2) broken down:
public getDirectoryContent(path: string, options?: DirectoryParserOptions = this.defaultOptions): string[]
private isDirectoryAccessible(path: string): boolean
private optionsToArgs(options: DirectoryParserOptions): string
private runCLICommand(command: string): string[]
And that's not true at all, a lot of modern languages make for disgusting dirty codebases with confusing code, spaghetti code and bad conventions from the language designers themselves. Off the dome I'm thinking Dart & Flutter or the stairway to hell as I like to call it.
On the other hand you have C# for example which, despite being an "old" language, is clearly more readable. Because the people who designed it aren't dogshit.
3
-
2
-
2
-
1