Jason Knight
1 min readFeb 28, 2021

--

That's where this stuff usually loses me -- it's none of the above. People CLAIM they are easier to write, or test... or to maintain... and I find them to be the polar opposite because it's more code, more cryptic code, spaghetti code by spreading the logic out all-over creation, etc, etc,..

Same disconnect I have with front end frameworks, where people endlessly sing the praises of how halfwitted garbage pissing on the entire reason HTML and CSS are separate from each-other, dragging things back to the WORST of HTML 3.2 / browser wars era practices... but somehow, magically it's easier (glittering generality) because "so and so said so" (testimonial), everyone is using it (bandwagon), we shouldn't get left behind (more bandwagon),

OR worse, "functional programming" which basically takes late '70's early '80's spaghetti code practices and makes it something to strive towards.

It all seems to me like stuff created and used by people who haven't learned the underlying languages enough to know if they've been saddled up for a ride or not.

Much like with Apple "quality", when people talk about these "proactive paradigms" (that's a joke) being "easier", I have genuinely zero huffing clue what they're talking about.

How is more code, spread out all over the place, taking more steps with more things to test, "easier" in any way, shape, or form? I just don't get it.

--

--

Jason Knight
Jason Knight

Written by Jason Knight

Accessibility and Efficiency Consultant, Web Developer, Musician, and just general pain in the arse

Responses (1)