HNHacker News
TopNewBestAskShowJobs

xenity7

112 karma · joined November 29, 2016

submissionscomments
xenity7··on Uber blames humans for self-driving traffic offenses as California orders a halt
It's difficult for me to understand how these types of things (specifically, the order by California to halt testing of self driving cars) can happen at a company as ostensibly as sophisticated as Uber.

There are two possibilities:

1) Uber had no idea it was illegal to begin testing cars in San Francisco/California without a permit, or somehow otherwise messed up getting the permit.

2) Uber knew it was illegal and didn't care or was a positive, probably because any potential penalty is essentially negligible, and free publicity results from a kerfuffle with a state regulator, reinforcing Uber's image as risk taking and cutting edge.

Option 1) beggars belief for a company of Uber's size. There are numerous legal issues around self driving cars and it would be very strange to devote millions to R&D without having at least SOME resources devoted to examining the legal and regulatory environment. The most basic question of all when testing a car... "do we need a permit for this?". It's difficult to imagine this falling through the cracks anywhere.

This leaves only option 2) in my mind, strange as it may seem. Maybe I'm giving them too much credit...

xenity7··on Building a Data-Informed Culture
A lot of this is pretty typical data warehouse stuff, but I really like the concept of allowing "anyone" to creat ETL jobs rather than relying on a more strict segregation of duties.

I've had the most success allowing free access to warehouses data with some guidance given around how to use it. The data team doesn't need to be the gatekeeper of all access to data - a better way is to consider them expert advisors on how to use it.

Getting bottlenecked with simple requests because you refuse to give technical end users full read access is silly.

xenity7··on Don’t Sign That Non-Disclosure Agreement Yet
I agree with you that often the consultant gets nothing out of the NDA (bar the case where the consultant is sharing a proprietary method). Larger consulting firms actually often include their own form of NDA in engagement letters forbidding the client from sharing work product with third parties without permission.

The NDA is typically separate from the actual engagement letter in my experience, and to your point I've actually worked on projects where we signed the engagement letter but "forgot" to sign the NDA and that piece fell through the cracks

We scrupulously acted as though we had though to prevent the reputational damage that would come from violating confidentiality - NDA or no NDA.

xenity7··on Don’t Sign That Non-Disclosure Agreement Yet
This isn't good advice in general - sure, in this situation you happened to have all the leverage because you were developing a core product of the company they needed to own to raise funding, but that's a corner case.

It's just as likely the situation be flipped and the client refuses to pay because there's no contract. The contract is there to protect both parties.

Starting work without a contract puts you at risk as a consultant - maybe the funds haven't been approved yet and the contract will never be approved, maybe the ultimate approver will disagree with the scope and you'll go down the wrong path with your day to day contact ...

Most companies hiring contractors are going to be larger than a handful of people and it's dangerous to assume you understand the internal dynamics as an outsider.

Just like a client will check that you can uphold your end of the contract by checking your references and qualifications, it's ok to ask a smaller client like a startup for assurances that they can actually pay.

← PreviousPage 2 of 2