85 karma · joined June 1, 2020
Even if this trick works, would it be ethical, knowing it draws money away from other areas? What would be the road SLO we would agree be acceptable?
You can't throw more compute at a problem ad infinitum.
- flattr support discovery: Instead of having a "Flattr" button on the webpage I visit I need to navigate to flattr website and search there... but I'm not going to do that. Maybe adblocker removed that button?
- ownership confirmations - I wanted to donate to person $PERSON and found them on flattr. But I had no idea whether this flattr account actually belongs to $PERSON. I reached to $PERSON about that and never heard back so I stopped donating.
Yes, this is in Europe.
I think I learned quite a lot, namely:
- why I failed the interview (I struggled to produce correct code, the code wasn't very robust and I said it's ok to put it into production)
- why I haven't failed the interview (ex. no mention of my English language skills) - which was more valuable for me than the "why I failed"
- a fairly good confidence that there's little details omitted - when they submit you a voluntary feedback they may give just the most obvious information. Ofc I didn't get the data about what was said on internal meetings.
- some insight into their internal structure, opinions of individual interviews about me etc.
I probably burned bridges with that company but after the interview neither party was interested in cooperation so I decided to give it a shot and see what happens.
I had to wait exactly 30 (or 14?) days (GDPR deadline) for the feedback to get to my mailbox.
https://www.theguardian.com/uk-news/2021/feb/08/royals-vette...
> Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d. And since systemd manages the system, it's called systemd.
> Système D is not an acceptable spelling and something completely different (though kinda fitting).
Wikipedia says that it somehow relates to Systeme D, but they don't have any good references for it.
https://kunit.dev/ - unit tests for kernel
https://docs.kernel.org/dev-tools/testing-overview.html - entire testing overview.
> It's DB implementation is utter garbage. It doesn't even organize files by time or really anything useful.
That sounds interesting, can you please elaborate on the internal structure of journald files or link to further documentation? And why would I care if journald handles it for me?
A nice feature is that journald gives you flags like "--boot" to see logs only emitted during a specific boot, or "--since '5m ago'" which is not that straightforward to do with the approach you favor. (if there is a way to do it easily, please let me know!)
They focus on the very problem you're asking about.
The question "how much free memory do I have" or "how much memory does this program use" is a very hard one, and you can't just read the "MemAvailable" column from /proc/meminfo or RSS/PSS/Virt from ps/pmap.
http://www.brendangregg.com/ActiveBenchmarking/bonnie++.html provides an example how "the same benchmark" can measure a different thing on a different platform.