594 karma · joined March 6, 2015
If the market had been allowed to work, and rural Americans did not get service until it was profitable we'd have a much different market in the US today.
*Edit: Of course this isn't something I want to let a prospective employer know, so I try to keep it generic by referencing benefits.
Personally I try to start a discussion about how important benefits are to me, and the fact that they can make comparing salaries between companies meaningless, so I can't really talk about pay expectations until I have a good understanding of the full compensation package.
But I'd love to hear some other approaches to go to.
Consumers should also be considered. If casual drivers are excluded, the smaller pool of drivers will cause prices to rise. Some consumers who previously used ride sharing will go back to driving their own cars.
There's also the removal of a smooth transition driving as a career. If you can do it casually for a few hours you can discover if you enjoy it and want to quit your job and do it full time. If the only option is to be a full time employee, you have to go through the hiring process and take a risk of quitting your current job just to see if it's for you.
What I would like to see is a permission though, like when browsers ask for your location: "This site want's to manipulate your clipboard. Allow?"
To tackle the problem HIPPA tries to solve, that is making sure that data sharing is secure and only with the intended parties, I want to see stronger enforcement of liability. Granted, the US doesn't have a great track record on that, seeing Equifax get away with what their doing. But I think that's the system that needs to be improved.
Instead of government dictating what "secure" means, different approaches can be experimented with on the market with strong enforcement of liability providing the necessary incentives.
I now maintain a daemon who's sole job is to undo Docker's meddling with resolv.conf until I can get the bandwidth to explore migrating to Kubernetes.
Having CI configuration separate from the code sounds like a nightmare when a code change requires CI configurations to be updated. A new version of code requires a new dependency for instance, there needs to be a way to tie the CI configuration change with a commit that introduced that dependency. That comes automatically when they're in the same repo.
Before I allowed her to play I discussed with her that she is not allowed to tell anybody her real name or the state she lives in. I think and hope the experience of being scammed might have cemented the reasons for that.
On vanilla vim if you :e scp://host// you should get the built in netrw browser working over scp.
Site owners can monitor these logs for rogue certs issued for their own domains.
I'm trying to learn Rust, working through various programming exercises, but it looks and feels very foreign to me.
One example is the closure syntax. Compared to Go where closures look just like function definitions, closures in Rust look needlessly complex.
I also always find myself wanting to type mut &a instead of the correct &mut a. The former just seems more obvious to me, a reference to a is &a. Mutable a is mut a. So a mutable reference must be mut &a.
Then the lifetime syntax, I don't even know what to think of that, but that's probably more because I'm struggling asking myself "Should I use a lifetime here, or am I doing something else wrong that is preventing the compiler from figuring it out."
Maybe these things make more sense to people coming from C.
with open('file') as f:
... do something ...
I don't know why that didn't come out on top in the debate. if re.match(...) as m:
... do something ...