DEV Community

loading...

Discussion on: Why You Shouldn't Use A Web Framework

Collapse
quii profile image
Chris James

What's worse:

  • Reinventing the wheel slowly and missing deadlines

  • Or endlessly changing the wheels of your car with different shinier, slightly flawed wheels trapped in programming purgatory forever?

Collapse
dansweeting profile image
dan sweeting

Both sound pretty rubbish.

But someone paying my wages overheard the word 'deadline' so they're pushing for the other option

Collapse
fullmight profile image
Cameron Pick

What's worse, buying high quality tires from the local tire store, or rebuilding modern industry from the stone age all the way back up to manufacturing tires yourself that aren't any better or are possibly worse in your back yard?

Collapse
grahamlyons profile image
Graham Lyons

The first one. What's the point of developing if you never deliver?

Thread Thread
darpacertified profile image
Darpacertified

What's the point of delivering if all you deliver is Little Caesars? What's the point of developing if your client can do it themselves?
Learn to code? You might as well learn to lie like a journalist. The age of homogenization. Music, movies, cars, houses, art, ideas, speech, content, and websites. But, hey, it's all about the $$$, and if you're makin' it, keep on keepin' on. Until I sell your client a higher quality website for cheaper.

Collapse
thewix profile image
TheWix • Edited

That's a false dichotomy. How about knowing your craft and using the right tools for the job? That's what this article is saying in a roundabout way.

I could write my own version of redux to learn the inner workings of it. I'm not gonna. I'm going to learn the pattern that Redux is based on and use the library that is well supported and tested by thousands of other projects using it. Will I mess it up? Sure, will I learn? Yep. Will I jump to Mobx right away? No, cause I've been doing this for over a decade and I've learned the grass isn't always greener.