Why would contaminating the environment of a major food supply be the least harmful place? how is that better than purpose built infrastructure to contain that trash?
They do also work on intercepting from rivers [0], but what do you propose? We should just leave all that garbage in the ocean and just try not to look at it?
You tell me. What would happen if we left "all that garbage in the ocean and just try not to look at it" ? What if all the effort and funding was focused on the waste production problem and materials problem instead of trying to collecting it in the open ocean? How long would it take for the waste to fall to the seafloor and then be covered by falling sediment? What is the EROI of both approaches?
I am convinced they mean well and are trying to tackle a tractable problem, but the garbage patch cleanup is not a good use of limited resources.
We need to know way more about our gut and bowel microbes. it's wild how little we actually understand outside of good gut health is good. It will take a lot of big and small research to slowly get reliable science and results.
sure it might be a mess, but at least it's purpose built. I love that kind of performance gains. Honestly most companies die before purpose built code like that becomes a problem.
In most cases it's not even censorship -- it's just some combination of an attempt to squeeze these non-EU companies for as much as they can get and good old fashioned virtue signaling about protecting consumers from things that most people couldn't care less about.
The "hard" way is often the simple way with these sort of things. What makes it easier is while building out your code, you make little pieces of UI to visualize what you're doing. Think of them like unit tests or test driven development. Then you can take those, clean them up a little and publish them.
If you like technology you could always slowly transition into teaching technology. Highschool programming courses, student robotics teams, etc might be fun?
Where Im from those programs and activity are usually ran by multiple teachers and need a lot more than hard science knowledge to run well. For you they could provide a on ramp into more and more tech without losing too much of what you have know
I review a lot of code with the mindset of yes and…
Basically when I start the PR is approved in my head until I find something blocking. I.e. major problem that causes dataloss, big performance issue or breaks other code. Anything else is a minor comment at most. The PR is approved by default. This gives the dev responsibility and ownership. Plus it increases release cadence
Doing a follow up PR to improve or fix something is just as fast as blocking the MR, but blocking the MR can be bad for morale.
This strategy might work better in young startups where having the feature _exist_ is better than not shipping.
in my experience this builds up responsibility and ownership and removes the whole policing of other peoples work vibe around code review.
Also decisions and discussion around formatting, when to test, design, features, functionality, architecture should not happen during code review, they should have happened way before coding, or collaboratively while working. Code review is the worst time for that stuff, imho it should be to sanity check implementation.