863 karma · joined September 1, 2010
I've been bike commuting in SF for 10 years, and the last year has been by far the worst. And most bad actors are uber and lyft cars.
I don't believe in God, but I do believe that if I get hit on my bike uber/lyft will be responsible.
-Double parking everywhere waiting for pickup / dropoff /routing. Blocking car and bike lanes.
-riders getting out into traffic
-erratic drivers (new to SF, easily lost)
Its pretty terrible.
If they painted their cars yellow, and made them pickup and drop off at corners / out if the flow of traffic things would be way better (imho).
It'd be nice if there was some sort of way for them to indicate they drive erratically. Perhaps by painting their cars all yellow or something...
If you're only going to say "I'm too close to her" and call her some bad things with an anon account, well, you probably just shouldn't have posted. I'm all for learning from the experiences people have interacting with the technocrati, but this post feels petty and lacks information.
Reminds me of the heroku shaming posts that (then) rap genius had to do regarding dyanamo scaling and performance - http://genius.com/James-somers-herokus-ugly-secret-annotated They had no other way forward, even though they were paying the "experts"
This is why companies should pay open source contributors more frequently :-)
`git clone` is an incredible power. Companies should reward those who are generous with their code.
For example, Microsoft may be changing their image, but their core software is closed source. <cloud provider> may be great, but can you pull off something like this when you've got an issue? The importance of being able to debug and patch your mission critical systems is hard to overstate.
Please encourage your employer to fiscally support the open source code that they rely upon!
Downside is that very few other authors are using it, so when you share code people are concerned about its format (no semicolons in particular).
The interview process is intended to be a bi-directional flow of information. Giving someone a X hour programming test means that for X hours, the company gets to learn about the developer, but the developer doesn't really learn about the company.
The company is the one paying salary, so they set the terms of the interaction. But the feel of disrespect for the developers time is real and valid. If you chose to do a coding test, do so respectfully to avoid insulting the person you potentially want to hire.
And, IMHO,comment threads aren't a productive place to have meaningful debate about this topic. If you care about this issue, they're all very receptive on twitter, email, etc. They're not shutting you out
Similarly Working Effective with Legacy Code by Michael Feathers (http://amzn.to/1UxwVdL) is a great programming book. I appreciate it because It's really nothing but patterns for dealing with bad code (mostly Java, but most of it translates to other languages). Very little why (which I already know), lots of "how to fix X", aka, great signal to noise ratio.
Children are a known hardship, but you don't really see it because it happens at your co-worker's homes and it's deemed unprofessional to talk about it at the office. Also, it sometimes appears to be rewarding. Trust me, we're not cheating the system, you shouldn't be jealous. Every other country in the world has this "perk" baked into their laws of government. But because the US is so pro-corporation only something that is necessary to treat workers with respect gets lumped into the "perk" category with your free fitbit and monthly massages.
That's much easier to send along to someone in product or a C*O who may not be comfortable with the dev tools.
That women are driven away by bias/discrimination is the true failing of our workplaces.