Worst Coding Standards to ever exist

@doma_inc

31.2K followers · usually 2.9K views a post

Views

15.0K

Likes

291

Comments

10

Shares

18

Selling · SaaS › Other SaaS

Doma Softwareseen in 7 videos →https://linktr.ee/Doma.software ↗

Why it worked

The video likely performed well due to its relatable and humorous take on common developer frustrations with bad coding practices. The use of memes and exaggerated reactions to showcase these 'worst' standards would have resonated with a programming audience.

Summary

The video discusses some of the worst coding standards encountered, including reverse indentation, excessive comments, and a strict rule against ternary operators. It also highlights an absurdly high unit test requirement and a problematic brace formatting style.

Structure

1Introduction to worst coding standards
2Reverse indentation example
3Excessive comments on a simple function
4Ban on ternary operators
5High unit test to code ratio
6Problematic brace formatting

Original caption

Worst Coding Standards to ever exist #coding #programming #code #javascript #domatech

More from @doma_inc

Their other posts in the index, biggest breakout first.

Product placement

The video mentions Doma.software via a linktr.ee link in the creator's bio, implying it is the product being promoted.

On-screen text

Worst Coding Standards to ever exist coding Worst Coding Standards to ever exist WORST CODING STANDARDS TO EVER EXIS Worst Coding Standards to ever exist reverse indentation. Worst Coding Standards to ever exist Wow. be ever WoW. be ever have database with TBL. Doing giving, like add function. ternary reactives ternary able application. be 165 tests 1000 code. out test code. No kidding. even quit

Transcript

These are worst coding standards to ever exist. So first off, reverse indentation. For example: myFunc(); and: if(something) { // do A } else { // do B } Oh my god. Wow. That literally might be the worst thing I've ever seen in my life. So I really, really hate when I have to preface database table names with TBL. Doing that is really giving, like, five lines of comments to like a add function. No ternary operators allowed where I currently work because not everyone gets it. If you told me, "Don't use it because we've had to rewrite them when the structures get too complicated" (nested ternary operators, anyone?), then I'd understand. But when you tell me that some developers don't understand them... um... Sure. They actually wouldn't be able to release that application. There must be 165 unit tests (not necessarily automated) per 1000 lines of code. That works out at one test for roughly every 8 lines. I feel like that was like a punishment. That's got to be a punishment that that person went through. This right format right here, which gleefully ignored the two pillars of the brace debate and just goes straight to crazy. No kidding. Even quit right there.