I maintain a few small Apache 2 libraries, I'm not sure how I feel about my code being used for AI training data.

Would such a licence even makes sense? If not, what's the most permissive licence you could have that still restricts use of the code in AI training data?

And what might be some unintended consequences of restricting the ability for your code to be used in that way (assuming that's legally possible - and I do appreciate that it's probably practically impossible)

Comments URL: https://news.ycombinator.com/item?id=35646778

Points: 2

# Comments: 4

Comments URL: https://news.ycombinator.com/item?id=34379151

Points: 3

# Comments: 0

I had started by hoping (almost assuming) people would be amazed at how useful my library was. But mostly they didn't notice it, or (and this was harder to accept): didn't even recognize or understand the issues it was addressing in the first place.

5 years later, the issues are generally much better understood in android world, but still. I know some teams are using it, but it's probably not that many.

So publishing it has just become a hobby, it's something I can be proud of, it works nicely, I often use it (or the knowledge gained while writing it) to speed up whatever I'm doing and make my life easier. I also publish articles about said issues, and they seem to be helpful to the people that read them, and I enjoy explaining things I understand.

I'm not on the engineering manager track, and I hope to be programming until I retire, so I'll probably just keep supporting it.

If I had any advice for the OP I'd say set your expectations at: personal pride in doing a good job

(I'm definitely not the best person to dispense any kind of marketing advice anyway)

Edit: looks like it's back from the dead again :) https://github.com/gitx/gitx

Comments URL: https://news.ycombinator.com/item?id=30683656

Points: 4

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=30525913

Points: 6

# Comments: 0

( I think the last time I did this was for a point of sale terminal I was working on, which needed a solution similar to the change making problem https://en.m.wikipedia.org/wiki/Change-making_problem )

Anyway, for those situations, I write a large number of tests cases, covering every reasonable scenario, plus a bunch of unreasonable scenarios.

Then I write a half-assed implementation that fails on several tests, and I keep hacking about until more of the tests pass. Once they all pass, I stop. Even if at that point I have no idea why that particular version of the code completely works.

It's nasty I know, but sometimes it's the quickest way to a robust implementation

so we could expect about 5 people with dementia in that control group, and the test group got 0, so not bad

What are the chances of a random control group of 14 over 85 year olds also not getting dementia?

If it's very common, and you would usually expect 7 of them to develop dementia, then 0 cases in the test group is potentially impressive. If it's quite rare and you would usually expect only one of the control group to get dementia, then it's not that impressive that the test group had 0, and easily down to chance

Comments URL: https://news.ycombinator.com/item?id=28992022

Points: 11

# Comments: 1

It's easy, all you need to do is spot the term "Russiagate", in this case the "gate" is being used to suggest that Russian influence in American politics is a fake news story (which it definitely isn't, see Muller report)

"In six out of seven countries — all but Germany — Tweets posted by accounts from the political right receive more algorithmic amplification than the political left when studied as a group."

I have to say, I think I would be happier with an answer like "because it avoids hotspotting according to the bocs"

This limits the applicability of the "don't use sequential IDs" rule to where it actually helps.

Otherwise, the rumour spreads, and later you find teams doing huge damaging work arounds to avoid using sequential IDs, in contexts where hotspotting is totally irrelevant (perhaps because they are not even using Firestore) all blissfully unaware, because they they think they are following "best practice"

I've seen this happen so often in large companies, the words "best practice" let people abdicate their professional responsibility to _think_ and it's quite dangerous IMO

I'm an android developer and whenever I hear the term best practice it immediately sets off my BS detector.

As a non EU citizen, immigrating depends on that specific country's requirements, but typically it would be a time limited arrangement, you'd need to pass a language test, find a company willing to sponsor the effort (so your residency is tied to that specific that job, and if you loose it you need to leave), that job would need to be at a certain level (e.g managerial level), the job would need to be in a field where there are national shortages, the sponsoring company would need to prove that it had made the effort to fill the job with a local first. If you're rich enough you can alternatively pay to create a business with maybe 100k capital and employ 1 or 2 nationals on a continuing basis and get your residency that way. Software developers no doubt have an easier time than most given the lack of software devs, but it's not a given by any means.

https://www.freemovement.org.uk/surinder-singh-immigration-r...