bhuga

9 ms·

61.
by bhuga 9y ago
> The idea that the taxis are corrupt and despicable is 100% Uber/Lyft propaganda. Here's links to stories of investigations into taxi bureaus and dispatchers for bribery and other schemes in 3 states: http://www.nol
62.
by bhuga 10y ago
GitHub doesn't charge for anything that's open source. Who the owner is or if they happen to be a customer doesn't factor into it.
63.
The Disappearing DriveCo Women(hackernoon.com)
3 points by bhuga 10y ago|0 comments
64.
by bhuga 10y ago
This is an important part of the new integrations early access program: https://developer.github.com/changes/2016-09-14-Integrations...
65.
by bhuga 10y ago
I wrote an electron app to inject javascript and CSS into slack in an attempt to turn off a lot of distraction and, more importantly, easily differentiate between bots and people. I feel the author's pain, but the great part about bein
66.
by bhuga 10y ago
There's plenty of agreement with you, so I'll offer a counterpoint. When a company is small--less than 10 or 20 people--it really can feel like a 'family' in that everyone would rather see the company fail than break apa
67.
by bhuga 10y ago
Fun article! I appreciate the author taking the time to go through the details, like formatting the source of the javascript, and figuring out the module system. Hacking on other peoples' websites is great fun. Everyone should try it,
68.
by bhuga 10y ago
It's bad enough that the VEP was bypassed, but the high-profile, 7-figure payout for the security researchers who had their hands on the bug is a problem too. Plenty of bug bounty programs have remote code execution at $10k, but the FB
69.
by bhuga 10y ago
Slack does a good job overall, but I'm glad to see articles like this one challenging the enthusiasm that they've seen of late. I'm starting to share the article's opinion that Slack encourages unthoughtful communication
70.
by bhuga 11y ago
I've found message retention to be a "checkmark feature:" It's technically there, but it's not really achieving the goals you'd hope for message retention to help with. You'd want to be able to say "D
71.
by bhuga 11y ago
> and a lot of process just to ship out one migration. I would have agreed with you before working at GitHub, but the end result is that deploying is so easy that 3 deploys does not feel like "a lot of process." On most of our
72.
by bhuga 11y ago
GitHub now has a build (we have about 12 builds per github push) that runs all the tests with all feature flags enabled. This doesn't hit problems that only appear in the matrix of some enabled, some disabled, but in practice has worke
73.
by bhuga 11y ago
It's quite a bit more hassle than normal American tax paperwork. Every foreign bank account or financial instrument over some trivial amount ($500?) must be reported. Foreign banks must report your holdings and gains using forms more b
74.
by bhuga 11y ago
Interesting piece. It will take some time to digest. I wonder about the arrow of causation for conformity back in the 40's. This essay describes WWII as a spark of a generation of conformity (preceded by the New Deal for some). But it&
75.
by bhuga 11y ago
I was taken aback by this as well. The Ruby community lets opinions be strong, and tends to converge on 'standards,' so I expected 2 spaces to be a strong winner. But beating out go, which ships with `go fmt`, is a pretty impressi
76.
by bhuga 11y ago
Does anyone know if this comes with an initiative to fill in the gaps in Slack's administrative API so addons can be created around that, too? I'm working with SlimerJS to audit message retention and a few other settings. Slack ha
77.
by bhuga 11y ago
If you've ever worked in residential construction, there's one constant truth: everything you make will be redesigned away before it fails. Our desire for novelty is strong, and cheap construction lets us reconfigure houses afford
78.
by bhuga 11y ago
I suspect setting up the free LFS reference/test server[1] that GitHub provides would have taken less time than writing this post complaining that GitHub isn't free enough. 1: https://github.com/github/lfs-tes
79.
by bhuga 11y ago
In that case, I might prefer an authenticator to a keyfob that requires insertion too. The yubikey is slightly more secure since it's actually signing a message from the server rather than sending a password that can be (briefly) inter
80.
by bhuga 11y ago
Your point is valid, but this may be a bad example. Construction margins are so thin, and construction businesses so sensitive to it, and Lowe's and Home Depot are so fungible. Even among retailers, there's no room for margin. Esp
81.
by bhuga 11y ago
Yubikey has a "always available" form factor if you're already bringing your laptop to work in the neo-n: http://www.amazon.com/Yubico-Y-110-YubiKey-NEO-n/dp/B00O8ST7... . It just lives in your USB p
82.
by bhuga 11y ago
I was going to come comment that there must be a good way to solve this, since the Ruby community has such a rich ecosystem of tools. Heroku, for example, has a nice one-click deploy button for Rails (and many more languages/frameworks
83.
by bhuga 11y ago
The API was originally about SHAs, rather than refs, but for protecting branches trees make sense. (You can retrieve statuses by ref, but are required to set them by SHA). Since a SHA can be uniquely resolved to a tree, we're doing thi
84.
by bhuga 11y ago
> Does the "required status check" thing apply to `git push`, or just to the merge button on the website? It applies to all ways of updating git: push, the web UI, merging, and the API. > how do you trigger a status check to
85.
Introducing Heroku Flow(blog.heroku.com)
38 points by bhuga 11y ago|0 comments
86.
by bhuga 11y ago
I still live here, and I'm sick of the "Crime is part of the character" narrative. The Quarter, Marigny, Bywater, and Treme can have plenty of character without the risk of getting mugged biking home from work.
87.
by bhuga 11y ago
Some popular GitHub CI integrators already do this: http://docs.travis-ci.com/user/deployment/releases/ http://www.appveyor.com/docs/deployment/github
88.
by bhuga 11y ago
The "lab" environments have enough capacity to allow plenty of parallel testing. When deploying to production, it's expected that you already know your branch does what it's supposed to do. A production deploy is when on
89.
by bhuga 11y ago
The deployment system automatically merges master into the branch being tested on deployment, and will not deploy any branch that does not contain master. In fact, there is a check that nags the main app team if master is not deployed to pr
90.
by bhuga 11y ago
"Bugs on onboard Wi-Fi, entertainment systems or avionics" are not eligible for bounties. It's very strange to see website timing attacks as worth rewarding, but not avionics. Perhaps they'd rather not incentivize people

More ›