* people not being able to contact me 24/7
* not knowing what is going on in the world all the time (this i miss the most)
* things being local
* way less crap people used to own
595 karma · joined July 11, 2018
* people not being able to contact me 24/7
* not knowing what is going on in the world all the time (this i miss the most)
* things being local
* way less crap people used to own
I don't like any language, but tbh I hate go the least, and I believe this is because few very very dedicated people with enormous amount of experience can simply make unpopular decisions.
In some cases when there is "no" it comes with clear instructions like: hey you need to know v8 more or understand hotspot better and try again in 6 months, but then there were those cases where the committee was incapable of giving feedback.
Interviews used to take about 6-8 hours of my week, and I was usually completely destroyed by the context switch. I remember many days when a deadline was very close, and I absolutely did not want to do the interview, but had to.
In general some days I was in good mood, some in bad mood and even though I tried to make the interview as objective as possible, I am absolutely sure I failed. Keep in mind, one interview has 5 interviewers and guess what they had bad days too.
From those 500 interviews, I was certain for about ~5 cases, for the rest I could not say if it was my fault, or the candidate's fault that the interview went south, in that case I pretty much voted as the majority was voting.
I still feel very bad about people's livelihood being decided in such shitty process, there is absolutely no way that in 1 hour I can find out if someone is good. I knew that, my managers knew that, their managers knew that, and yet we kept going..
I feel that adding more time/people to the process only increases the variance, adding more structure to the process only increases the bias (like we get people who can pass interviews, but not do their job).
1 year ago i tried to fix it myself, broke the space bar crimps on 6 month old mbp15, and they told me because i tried to fix it myself i have to pay 500E for the repair. keep in mind i make my own keyboards, i did not even think i will not be capable to remove a bread crumb from under the space bar.
few months ago I sold all my apple stuff, and have never been happier https://txt.black/~jack/bye-apple.txt
considering in many cases you want to copy live files, you have to copy them to place you can unmount, so now you have 2 problems
if you dont gzip the dd you risk pure cosmic microwave background bitflips and no checksums, and they can corrupt superblocks and etc
if you gzip it (to have crc sums) you cant restore partial files from it so easily unless you use squashfs and significantly complicate the process
so tar and gzip is more robust (compared to the dd) just because of the crc (of gzip not of tar), size and portability
to me the `yet another bootstrap css SaaS with three tier pricing, faded monotone brand logos and circlular portrait photos of the “team”` is just depressing
slack: https://baxx.dev/join/slack
google groups: https://baxx.dev/join/groupsothers I chose are horrible, such as https://scrambled-eggs.xyz which is effectively unsearchable, though you could say it was by design haha
it is super cute though, I still get excited every time I try the registration flow.
the registration api is quite easy (https://baxx.dev/help/register)
curl -d '{"email":"your.email@example.com", "password":"mickey mouse"}' \
https://baxx.dev/register
I will probably do make register.sh endpoint that returns a bash script that runs local dialog like:
curl https://baxx.dev/register.sh | sh
(just idea, not implemented yet)this will be fun, making portable tty dialogs :D
cat file | encrypt -k .pass | curl --data-binary
cat file | encrypt -k .pass > file.enc && curl -T file.enc https://baxx.dev/io/$BAXX_TOKEN/file
(encrypt: https://github.com/jackdoe/updown/blob/master/cmd/encrypt/ma...)offtopic: it is a bit annoying that cat | curl makes curl buffed the whole standard input, so for big files you have to either you have to do -H "Transfer-Encoding: chunked" or use -T file
2) dd block devices is very fragile, its better if you just tar --exclude/dev ... (https://help.ubuntu.com/community/BackupYourSystem/TAR - Alternate backup)
in the future my plan is to do 5€/m for 1TB which is pretty much glacier price
i think the problem needs exploration, i have been bitten by bad anomaly detection and setting up alerts post-moretm after losing data one too many times :)
i imagine creating a bunch of features such as:
* file extension
* time of upload
* delta from previous version
* size difference from other files in the directory
* etc..
and having enough customers we should be able to do good-ish predictionwhen a file version is "weird", so we could send notifications such as:
> hey is this file ok?
with some exploration factor, even using UCB will(should) be better than nothing
I plan to use vowpal wabbit's contextual bandits with only 2 actions, "send notification"/"dont send notification" given all the context
this of course will be just extra on top of the manual alert rules, but hopefully it will save some data :)
If the users agree we could also publish anonymized datasets with labeled data (such as: given context alert was sent: was [good]/[bad])
Which will be awesome.
started playing with https://github.com/rivo/tview last week, but didnt have much time.
thanks a lot for the feedback, much appreciated!
* i have actually implemented this kinds of systems multiple times and always failed at the 'who watches the watchers' and usually had broken backups (as in i usually needed them few years after the system is written and by then something is always wrong)
* in the future it will use contextual bandits to probe for broken backups (such as: hey, is file XYZ with size X uploaded at Y weird?) and learn from all the customers triggering the AI flywheel, more backups more data, better contextual bandits, better service, more customers (the idea is to use bandits[or something else with exploration factor] for probability of "good" notification)
so in few words: value = out of the box alerting + nice api + machine learning (not implemented yet) + good price (no cloud)
also fixed the $ to E in the blog, thanks for the heads up
which uploads: /EAAAAAEQJUAYSU5PR3WO7IKOX2ZPM5NSNIALFYJE5MMDJYNMNUZEA===
The systems will be written anyway.