2,068 karma · joined September 29, 2009
Web front-end specialist looking for a job with an ethically-aligned company
http://eleven-twelve.net
http://github.com/alxndr
http://drwxrxrx.bsky.social
email: YWx4bmRyK2huQGdtYWlsLmNvbQo=
[ my public key: https://keybase.io/alxndr; my proof: https://keybase.io/alxndr/sigs/B-vRl0kOw2kpqag-RlOReucueGiSJi-u5Ef4CTQ_TkI ](Because the extension works on a JS level, it needs to wait for the results page to load before it can strip out what you want to hide. Too often I'd see the results page begin drawing quickly, with a couple w3schools results at the top of the results, and my eyes would scan down to find the first non-w3schools result; then a second later, in the middle of finding the first such result, the w3schools results would be removed, and the non-w3schools result which I'd finally found and was about to click on has moved.)
I'm confused by his stance on versioning, however: he's very much against semver, which means these tools can be tricky to use with npm (which assumes all packages follow semver).
> "The cartels, of course, are adapting to the new reality. Seizure data appears to indicate that with marijuana profits tumbling, they're switching over to heroin and meth."
Is it a given that magnifying life's amplitudes is a good thing?
Based on what I hear come out of the mouths of politicians, that's emphatically not true.
Doesn't sound cost-effective.
The ticket that gets deployed is often as simple as a typo fix or a small CSS tweak, just to illustrate the whole process. The risk of deploying to prod isn't zero, but since we deploy many times a week already, the risk of deploying a typo fix is pretty low to us.
It also serves as a test for the existing employees: ideally those workflows are smooth enough that it all Just Works on a freshly-set-up environment and account, and we are comfortable enough with our rollback strategy that (after reviewing and testing) we are not afraid of merging in and deploying our new employees' code.