jonobird1
Joined 14 years ago
Joined 14 years ago
I think there should be a manual QA process to test the functionality of what the developer is pushing out.
The issue with code reviews is always that they take so much time for another developer and many devs are super busy so they just have a quick review of the PR and approve or feel they have to add some comments. Context switching between what the dev is already doing and having to come to the PR to review properly means they should switch to that Git branch, pull down the code, test it all and check for logical bugs that a static code review won't pick up.
For juniors, code reviews are still useful as you will be able to spot poor quality code, but for seniors, not as much for the reasons above, better off having a QA process to find and logic holes rather than expecting devs to invest so much time in context switching.
At no point has anyone actually done anything about this, even though it significantly affects peoples views in a negative way through false truths, voting etc.
What about kids with social media and how bad it is for them? Evident through the fact that most people who work at social media companies ban or severely limit their kids from having phones and/or social media. Nope, let it slide.
But the China war with Tiktok? Of course this gets focus. How about they care about the country they actually live in by looking after the people that live in it rather than only focusing on external country threats.
It's sad living outside of the US and watching it fall apart by their own doing. If they cared, they'd focus on their employment rate, homelessness, free quality healthcare, gun control (yes), clean streets, and better education. If they can't solve it with their Military, they don't care.
If you take Tailwind CSS for example, when correctly using their CLI tool, it only includes the size of the css classes actually used, keeping it to a minimum, when compared to people just doing a standard import of the entire library. I like this mentality because it's offering the ability to be very lightweight, or as large as the 'framework' it offers. NextJS offers this as part of their build process, but not sure how big their assets are with it for a simple usecase.