No it was not a stupid assumption. You need to read more carefully as I exposed a flaw in his reasoning. The suggestion was that since CP possession does not prove physical molestation, therefore it is OK. Actually possession of CP is a crime in itself. This is an objective fact. I've known of otherwise intelligent people who do believe its actually OK to possess child porn if they're not physically molesting anyone.
Of course it is not OK. Does making it illegal and violating everyone's privacy rights reduce child abuse? I'd like to see the evidence. Another example is virtual child pornography which , evil as it is, does not harm anyone during its production, yet that is also illegal (in the US). The question is how far will governments go with the instrumentalization of child abuse prevention in order to spy on their own citizens
He means developers should commit work in progress directly to the master branch. The work in progress would be disabled in production deployments by a "feature flag" boolean configuration setting. The exception to this rule would be very large changes which must be developed in a separate branch, and have been carefully planned with a corresponding RFC document.
In general I don't like this approach. Branches are troublesome when you hire mediocre developers who don't communicate and coordinate between each other. Merge conflicts are often a result of laziness, poor architecture and planning, and weak communication skills. In my experience, smart developers do not create problems with feature branches.
I agree with this. One of the best changes we ever made was embracing a branch-heavy merge-centric workflow for literally everything. There was considerable pushback initially because it was perceived as 'complicated' but that dried up after a month because people were no longer fighting to push their hurriedly-rebased work to the canonical master branch any more.
It also means we can put an extra layer of QA testing between dev branch and master, which works nicely as a means of forcing communication between devs and QA too, and helps with onboarding (because the product featureset is huge).
Automated tests are great, but having a person read the feature ticket description and testing steps and then check that the functionality actually makes sense before it hits the master branch...
One more tool in the box, and it's a great culture correction mechanism too. Devs who don't test their work before submitting it get it sent back for fixing and feel less productive, so doing things thoroughly the first time feels quicker than rushing it. Doesn't even require management to monitor rates of reopening tickets, etc: people just don't like having to redo things.
It's really silly for you to be offended by something as objective as the PageRank algorithm, which is essentially how search results are ranked. https://en.wikipedia.org/wiki/PageRank
There has been a severe population-level decline in testosterone levels since the environment was flooded with xenoestrogens. This is a major global problem.
Soy is optional and consumed voluntarily, but BPA and other such chemicals have a significantly more potent long term effect, and contaminates everything it touches.
Yes, BPA accumulates in body fat. However, the environment has also been flooded with pornography which could also be responsible for the decline in testosterone/sperm counts, no?
No. This is not a trivial matter. The decline starts around the mid 20th century, is occurring globally, and levels have reduced by standard deviations from the old norm. Read up on it. It's way more serious than you think.
You're right, it isn't a trivial matter. However, neither has it been well explained. For example, how exactly has porn been ruled out? Porn also grew steadily since mid 20th C...
Correlation is not causation. Computing performance has also increased significantly since the mid 20th. Should we blame Intel for the drop in T levels? Where the hell do you get the idea that porn reduces testosterone? Research shows that watching porn increases testosterone levels in men https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2799222/
Simplistic "No True Scotsman" bullshit. ORMs provide type safety, ease of refactoring, and reduce a lot of boilerplate. Of course, occasionally you need to bypass an ORM to write complex queries, which is fine. ORMs are not perfect, but are a very useful tool nonetheless.
