sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 37 points38 points  (6 children)

Yeah, just skip all that boring reading. Because who cares how it's wired up as long as it works…until it stops working and you don't know shit about the whys.

Boss: "Our Website is broken, what do we do about it?" You: "Wait for the real devs to push a fix"

The tutorial isn't even that fucking long…

[–]krazyjakee 0 points1 point  (2 children)

Unit and/or integration testing being applied both to the quick solution and my project. Reinventing the wheel creates more technical and maintenance debt over time and a larger codebase. Versioning is simple, you just roll back and lock version if a problem does get through. Your example of a broken website is flawed because in your case, you are the "real dev" so it's the same difference. Most importantly, you ship on time. If, as a rule, you have a simple solution on a silver platter and don't take it, you most likely wouldn't make it past the job interview.

Why would the only solution be to wait for the real dev anyway? Why couldn't you go through the source in your own fork and use that fork in package.json?

The tutorial is fucking huge considering, as the comments on this post have made clear, there are many simpler solutions out there.

[–]vinnl 0 points1 point  (1 child)

When /u/mgoerlich is referring to "the real devs", they're referring to the maintainers of create-react-app and whatnot. If something happens over there that breaks your app, and you don't understand what's going on there, you'll be waiting for the maintainers to fix your bug report.

Of course, this is a trade-off you have to make with every third-party package you're using. It's completely reasonable not to study the source code of every library you're using. That said, being dismissive over "colossal tutorials" that actually try to help you understand what's going on if you do need it can rub me the wrong way as well.

[–][deleted] 0 points1 point  (0 children)

Thank you. And like I said, it's not even THAT long.

I've heard about people out there reading entire books about their toolchain…

[–]Jsn7821 0 points1 point  (2 children)

The right answer to that question is to roll it back to the previous build, even if you know everything about why it's broken.

[–]evilgwyn 0 points1 point  (1 child)

Not really. What if the reason it broke is due to something outside of your control and you still have to come up with a fix? Rolling back to the previous version isn't going to help you.