Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
The Courts Businesses Crime

Former Tesla Employees Brought Stolen Documents To Self-Driving Startup Zoox (theverge.com) 45

Self-driving startup Zoox has admitted that four of its employees took confidential documents from their previous employer Tesla, according to a statement issued after the company settled a lawsuit this week over the matter. The Verge reports: "Zoox acknowledges that certain of its new hires from Tesla were in possession of Tesla documents pertaining to shipping, receiving, and warehouse procedures when they joined Zoox's logistics team," the startup said in a statement to Reuters. Zoox says it will pay Tesla an undisclosed amount of money and will perform an audit to "ensure that no Zoox employees have retained or are using Tesla confidential information." Zoox says it "regrets the actions of those employees," and says it will also "conduct enhanced confidentiality training to ensure that all Zoox employees are aware of and respect their confidentiality obligations."
This discussion has been archived. No new comments can be posted.

Former Tesla Employees Brought Stolen Documents To Self-Driving Startup Zoox

Comments Filter:
  • God no! (Score:4, Funny)

    by Impy the Impiuos Imp ( 442658 ) on Thursday April 16, 2020 @05:26AM (#59954026) Journal

    were in possession of Tesla documents pertaining to shipping, receiving, and warehouse procedures

    Zoox says it will pay Tesla an undisclosed amount of money

    "Sources say it could be as high as $4.98."

  • by nospam007 ( 722110 ) * on Thursday April 16, 2020 @05:34AM (#59954052)

    No stealing involved, it's only a copy, the original is still there, I checked.

    • Something taught at any university with a business program, it's called Manufacturing Theory.

      WTF?

      • That's something that was mastered by people with high school diplomas - at best. I knew business majors studied stupid shit, but I guess I underestimated how stupid.

        • Um, it's complicated stuff. Certainly nothing you get a degree in, but it could easily be a full course. Doing shipping, receiving, and warehousing efficiently in a large manufacturer can translate to added efficiency on the factory floor. This isn't your standard office mailroom stuff. I don't think there was anything really secret in those documents that were stolen, but it would still be a good boost to a manufacturing startup.

          • I would argue that while the problem is a complex one, the THEORY of warehouse management is straightforward.

            In other words, I'm skeptical that a business major who took a course in warehouse management theory would compare favorably to a high school graduate with basic math skills and 3 months of warehouse management experience.

            • by sycodon ( 149926 )

              No.

              You are an idiot who evidently has NOT had any experience in manufacturing.

              Sure, inventory clerk who just push buttons can follow work procedures and push buttons, but the task of managing people, materials, equipment, schedules, etc in a modern manufacturing plant is hugely complex and encompasses many disciplines.

  • by bobbied ( 2522392 ) on Thursday April 16, 2020 @05:35AM (#59954060)

    Non-disclosure contracts are important, leave company documents behind when you leave, all of them.

    You can take the knowledge and skills you have learned with you, but you cannot take information that your past employer has paid to develop. That basically means, leave the documents behind, paper or electronic, even if you wrote them. If your previous employer paid you to develop something, they own it, not you. That goes for software, processes, client lists, phone numbers or anything they consider a trade secret.

    You can take your skills and technical experience with you. Just be very careful to leave behind the practical application of these skills and experience (or at least the documented proof that you took from your past employer). You can redevelop the systems and processes you know work relatively safely (being careful of any patents) but don't take documentation to jumpstart things. That's pretty stupid.

    This has usually been made clear by any new employer I've had. They don't want to get into a legal argument with your past employer and I don't blame them.

    • by jellomizer ( 103300 ) on Thursday April 16, 2020 @08:43AM (#59954512)

      I once worked for a company that had bought out another smaller company. The previous owner of the company (who was still on board as an employee, to manage the transition) decided that (now that he was out of debt) selling the company was a bad idea. So he just got up and left. Normally that would be the end of the story. But this guy took all the software that he wrote and downloaded all the data over a weekend before he quit and started his own company, stealing a lot of customers who he offered a 0 issue transition because he had a perfectly working environment with historical data at home.

      Needless to say, we successfully won every lawsuit against him. So the guy went back into debt again. Because he broke so many laws, it was like buying the company for free. It was business, and luckily for him because what he had done could have put him in jail. But we decided to fight for Civil damages vs criminal ones.

      His defense was filled with a lot of what we see from Slashdot ANAL responses to these things, claiming he was using an older version of the software before he sold the company, there isn't any proof that it was him (there was). He recked his life, where if he would have taken the money he could have lived a good early retirement.

      • Day 1, talk 1 to anyone I hire: "Not a single line of code from your previous life. Even it is a published PhD thesis work, no way Jose. I will pay you to re implement and retest. But I want git commits and merge records proving beyond a shadow of doubt it is a fresh implementation. "

        Some balk. They want to hit the ground running and show they have the stuff and they want to "contribute" immediately. One more serious talk about the liability and lawsuits makes them see reason.

    • by raymorris ( 2726007 ) on Thursday April 16, 2020 @09:43AM (#59954764) Journal

      > That basically means, leave the documents behind, paper or electronic, even if you wrote them. If your previous employer paid you to develop something, they own it, not you. That goes for software, processes, client lists, phone numbers or anything they consider a trade secret.

      Absolutely right. If you develop something (documents, processes, software) that may be useful to you in the future, but isn't a key competitive advantage, talk to your boss about releasing it at the time you create it. I've done that successfully several times.

      Publishing and open sourcing things has advantages for the business. Software modules that you contribute back to an open source project can get maintained by others, for free, rather than the company needing to permanently pay someone to maintain them in-house. Rather, when they become part of the upstream distribution, they are maintained as part of the upstream project. An employer from six or seven years ago is currently using updated versions of code that I wrote when I worked for them, but they haven't touched it. Other companies have updated it for them when the other organization wanted to use it too.

      That also means I can use it, of course, since it's open. I had permission to open source any code that wasn't unique to our industry or our specific environment, anything that had broad application beyond just us and our competitors.

      Publishing white papers and things can be good marketing and PR, getting the company's name out there. On the other hand, when I spent a few weeks developing security training to train our employees in general information security topics and asked my boss if I could present the lessons at outside security groups, he gave me permission to release them after *removing* all references to the company . He figured that would avoid any implicit endorsement of the material by company, and reduce or eliminate the risk that something I put in could embarrass the company. I followed up the verbal conversation with an email "here is a copy of the slides with all references to the company removed, and adjusted for an outside audience. This is what I plan to present at the security conference. If it's okay I might put it on my blog or something too". Then I forwarded his reply to my personal email just to have a record of the approval.

      At another organization, it would have been more difficult to get approval to release internally-developed software under an open source license. In fact due to fud, the general company policy was that we only used upstream versions of OSS, we never used our own modified version. What I did a couple of times instead of "I want to write this and open source it" is I wrote a message like this to my boss:

      There is an open source component that does 90% of what we want. I can work to get the other 10% that we need added to the public distribution, then we can use it. That'll be faster than writing our own software from scratch and the this open source one already has the bugs worked out moreso than if we wrote a new one, with new bugs.

      I got approved to "work to get the OSS one to release a version that does what we want". Of course that's exactly the same thing as open sourcing my work on it, just phrased differently.

      Nobody can complain about me re-using the work I did since *anybody* can use it, it's open source.

    • I tend to have backups of stuff from previous companies. No serious trade secret stuff, and I've never worked two places in a row that were in the same industry. Mostly it's a matter of not purging stuff at home. I have gone backed and looked at older stuff, like how I had an easy to use makefile system, or a script to rebuild a gcc cross compiler toolset so that I could quickly compare different versions, etc. I wouldn't use copies of an old company's code, most of it is horrendous junk.

      I have also kept

    • by pavon ( 30274 )

      A good corollary to this is to make the habit of creating at-home collections of public reference information that you learn while at work. You get used to being able to look information up when we need it, so you don't commit every detail to memory. Then you move to another job, hit a familiar problem, and think "I've seen that problem. It was solved in that paper by that dude that is referenced in private code that I don't have access to anymore." and spend a day doing literature searches that don't turn

      • I don't. I never bring stuff home, ever, unless it's on their equipment and I never leave an employer without returning everything that's theirs.If they want me to work from home, great, buy me a laptop so I can. You want me on conference calls at all hours? Again, fine but you are going to pay for the cell phone. I will never do work on my equipment (beyond letting you use my network, and then if YOU require it I'm going to likely ask you to pay for some of the expense). I don't so much as insert a per

  • by h33t l4x0r ( 4107715 ) on Thursday April 16, 2020 @06:57AM (#59954268)
    What's going through a Tesla employee's mind when they leave Tesla for a company called Zoox. But it has to be $$ eyeballs. Also Zoox? They took that nonsense about having 2 o's seriously? Just because Yahoo and Google did it does not mean Zoox can do it, and in fact it almost guarantees they cannot.
    • They took that nonsense about having 2 o's seriously?

      Seemed to be working^H^H^H^H^H^H^H not going so well anymore for ZOOM.

      • They took that nonsense about having 2 o's seriously?

        Seemed to be working^H^H^H^H^H^H^H not going so well anymore for ZOOM.

        You're looking for ^W ;-)

      • by cusco ( 717999 )

        Xoom on the other hand is doing business hand over fist now as people send remittances back home to shut-in families.

    • Back in 2000 during the dot com bubble (gee!) some French guys created a site called kasskooye.com. The name is a pun on a word meaning "ball-breaker". It was full of derision about the silly tech startup names, crazy business plans and IPOs etc. happening at the time. In fact the site still exists... Will never get old apparently!
      • Well, they were (and still are) a lot of people saying Tesla, Amazon, Google, Facebook... the business plan was crazy, no one is going to buy electric cars, no one will want to buy all their stuff online, no one will want to pay a lot of money for ads on a search engine or social media. With silly names, and much doom and gloom about them going IPO.

        90% of the businesses fail their first year. Often due to a lot of silly things, most often the Owners not working hard enough to bring in customers. (A friend

      • Back in 2000 during the dot com bubble (gee!) some French guys created a site called kasskooye.com. The name is a pun on a word meaning "ball-breaker". It was full of derision about the silly tech startup names, crazy business plans and IPOs etc. happening at the time. In fact the site still exists... Will never get old apparently!

        Do you remember heyidiot.com? From an article, "The site, which calls itself a “cash portal,” sells one product — shares in HeyIdiot.com: “You can buy as much stock as you want with the only rule being that each new purchase must be executed at a successively higher price.” A funny idea — made even more amusing by the fact that two of the site’s creators are prominent Silicon Valley CEOs: Oracle’s Larry Ellison and Network Computer’s Mitchell Kertzman."

    • by Rei ( 128717 )

      Zoox raised $800M in capital on a $3,2B valuation, which strikes me as insane for a startup. So they had ample cash for poaching.

      I really doubt they'd get that sort of valuations now, though. Self-driving valuations have been collapsing. In a year and a half Waymo has gone from a $175B valuation down to $30B.

    • Some people like being a big fish in a small pond. Tesla has been growing from the plucky underdog company to a major automaker with a Market Cap of 132.55B compared to Ford 19.73B and GM of 29.82B

      When a company gets large, they hire more people, many above them, often in positions that they were hoping to get promoted into.

      (Now the fact this particular guy seems to have a lack of business ethics, I expect Tesla didn't want to promote him anyway)

      But now seeing he is stuck in a dead-end job, it is probably b

    • About 2 years back I met a zoox IT guy at a network security training event. Before that I never heard about the company.

      They had a lot of funding out of Australia and if you think Musk over-promises things you should see what these guys were attempting.

      Car will be fully 3D printed.

      Fully self driving from the first model. Basically like Musk's Robo-Taxi thing based on the M3 but no production car before that.

      Symmetrical from front-to-back so it drives either direction without turning around. I

  • by Zaraday ( 6285110 ) on Thursday April 16, 2020 @08:49AM (#59954542)

    Zoox says it "regrets the actions of those employees,"

    No, Zoox regrets that they were caught. We've seen this and similar expressions far too many times not to know its true meaning.

    • I guess it's hard to have value as a self driving company if you can't really figure out self driving. Autopilot is about as far as you can get from 'controlling the steering wheel' to real self driving capable of handling any situation.
    • I don't know. They might have taken a look at the documents and said "WTF?" and thought "We risked getting sued into oblivion for this crap?"
  • Funny. I hadn't heard that Zoox pivoted from their crappy dating app. Well these days everyone needs a crappy dating app or a self driving car.
  • Warehousing. Shipping. Receiving logistics are constrained resources by sheer physical reality.

    Where's the rocket science? At most, its an algorithm, electric truck and robotic automation. These are fairly known roadmaps to JIT manufacture.

    Waiting for other shoe...

The 11 is for people with the pride of a 10 and the pocketbook of an 8. -- R.B. Greenberg [referring to PDPs?]

Working...