erdo

Joined 9 years ago

Karma
670
Submissions
172
Member since
Nov 17
maintainer of android-fore https://erdo.github.io/android-fore
View on Hacker News

Recent submissions

Comment · 3 years ago
That's sarcasm, it probably also wasn't actually Funny. Nothing about what they said suggests they didn't subsequently look into why their tests missed the issue
Comment · 4 years ago
That's exactly how I treat publishing my own OSS now (probably on a smaller scale though).

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)

Comment · 4 years ago
Comment · 4 years ago
I do TDD in one specific case, and it's always a unit test. Very occasionally I will need to write a function or a small class do some complicated logic that I'm too lazy or stupid to work out how to do. I do know exactly what the results should look like though, including all the possible edge cases.

( 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

Comment · 5 years ago
Ha of course it does, thanks :) I don't know why I didn't see that

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

Comment · 5 years ago
These stats are only useful if we know how many people get dementia in the first place.

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

Comment · 5 years ago
Who is this news org, why should we trust them? A cursory look at their content suggests we shouldn't.

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)

Comment · 5 years ago
the source blog post: https://blog.twitter.com/en_us/topics/company/2021/rml-polit...

"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."

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton