Just chiming to say that we used Hellō for one of our products ( bestozy.com ) and the whole experience was a breeze. Dick Hardt was very accessible - but tbh we didn't need much help at all as the integration was straightforward and the documentation comprehensive.
I think we need to factor in "Correlation is not causality" and the presence of confounding variables.
Slave abolitionists explicitly mentioned where they derived their morals from - clearly establishing causality.
Could there be something else common among slave practitioners apart from religion - like common materialistic greed and superior firepower to overpower and dominate others?
> Could there be something else common among slave practitioners apart from religion
Cherry picking again, are we? So now we are looking for an alternative explanation - but only on the evil side. The existence of Christians who opposed slavery does not prove that it is in any way central to Christianity, or exclusive to Christianity. That's not how logic works.
On the other hand, the humanist Enlightenment in France led to the French revolution, led in turn to laicist France granting citizenship to former slaves in 1792 on non-religious grounds.
So yeah, there was something else among both abolitionists and slave holders, which is my whole point.
I totally agree that asking people who created/maintain/make significant contributions to open source projects is a waste of time.
However, for hiring people who don't have a public body of work to point to - it remains pretty effective. (I am not affiliated with hackerrank/hackerearth/codility - just been on the hiring side for the last many years)
Also, in my current org - we've been able to trust people lacking the "expected" graduate degrees - solely because they were able to prove their acumen in the interview by solving algo-data-structure problems. (Of course, we have to be creative here - and avoid like the plague the same bunch of questions which are present all over the web)
Loved your blog - but I think the parent's question was how to gain the skills of working/designing OT/CRDTs etc on their own. (I am clarifying the question - since I'm interested in the answer as well)
I honestly think a good skill to have as a programmer is to know when something is a complex, niche problem with inherently "fragile" implementations (as in, it is really easy to make mistakes) that is therefore best solved by a few domain experts working on an open source library, and just use that library.
Based on everything I've seen about them, OT/CRDTs sound like they are that.
(Author here) I agree with that conclusion. I think they're really fun to implement and explore. I've been working in the area for a decade. And I've implemented over a dozen variants of OT systems by now. And despite all that I still consistently make mistakes that are only found with a fuzzer. Even thorough unit testing is never quite enough.
I recommend implementing them for the fun of it. I love it. But don't put anything you write into production until you can leave a randomized test suite running overnight without errors.
This guy just asked how to get into them because he is interested in them.
You just replied don't. Have you considered he wants to this regardless of not applying them purely commercially and wants to perform research, or in a novel industrial capacity?
I wasn't telling them not to learn this, or at least that wasn't the intent. Learning for the sake of learning should never be discouraged, and I apologize if I came across that way! I was responding to this last sentence:
> It's just... sad to know enough that I produce less than optimal work but don't know enough to confidently prevent it from happening over and over and over again.
Basically, the notion that not knowing how to implement this means the resulting product is sub-optimal. My counter-argument is that delegating work that needs expert domain knowledge and skills to the experts and use the fruits of their labor will result in a better product.
One thing that I learned from Gladwell's masterclass notes [1] is giving the reader (or listener in a speech) some candy. Candies are fluffy - but they also help readers/listeners retain more and also share more. Personally I've noticed myself using such candies to broach an idea with someone or a team - and the difference in interest is visible.
This will be similar to the college fees conundrum, no? An increase in financial aid resulted in colleges spiking up their fees (one of many factors - but definitely one factor). So won't landlord be similarly incentivized to increase the rents they collect?
Maybe a better example of what i'm referring to was a recent blog about why amish people get away with low medical expenses (one of the reasons being - their not being part of the insurance that the rest of the folks have..)
You can pontificate that its one rogue complainant or you can check the data because its right there and shows race, age and gender of the complainant. The very first page of data shows one sergeant with 25 complaints composed of atleast 11 complainants over 5 years.
Well, you've agreed that's not likely, so how exactly is your statement helpful? Why are you dragging the conversation to center around possibilities that even you don't believe in?
As long as there's zero accountability or transparency, there will always be the remote possibility that there are good cops out there being complained against, but that should be an argument for greater accountability and transparency, not for assuming the best and waiting for the next time a police officer murders someone on camera to do the same thing again.
Agree on the cheapening part - but I really love the reminders on my phone - 5yrs ago or 3yrs ago of simple everyday events - cheap photos but fond memories.. photos that probably would not have been taken with an actual camera.
