News for hackers. Stuff that matters.
Re:How to Go From Google Engineer to First-Time CTO by benjaminwootton on Monday September 09, 2013 @12:56AM (#6351933)
This made me chuckle:

> The “build your rig” workstation budget was a good idea... at least until one of our new hires requested one [...] Suddenly we had hires asking to use their own laptops and spend their budgets on expensive peripherals. Others wanted to assemble systems that were sure to be an IT nightmare and high-maintenance. And all the while I knew everyone should be using Mac OS X because it would be clean and simple.

Isn't this the whole point of the perk? All corporates want you to use their own clean, consistent, standard desktop, even though we have more powerful tools at home customised to our likings.

Letting me use my own laptop and giving me a nice huge monitor and chair to pair it with at work would cost less and come with real productivity benefits.

Re:How to Go From Google Engineer to First-Time CTO by pbiggar on Monday September 09, 2013 @02:57AM (#6352200)
The goal is to have a machine you want to use. You don't want to instill opulence as a corporate policy.
Re:How to Go From Google Engineer to First-Time CTO by jmspring on Monday September 09, 2013 @03:18AM (#6352243)
From a corporate perspective and from a personal liability perspective, what else is on that laptop and what code/inventions where created when? A big issue is the time/machine/invention intersection. California employment law gives a lot of credence to what you do on your own machine, on your own time is yours. If you use your own hardware for day to day work the lines get muddied.
Re:How to Go From Google Engineer to First-Time CTO by DannyBee on Monday September 09, 2013 @03:20AM (#6352247)
"California employment law gives a lot of credence to what you do on your own machine, on your own time is yours"

It really doesn't, people just think it does :)

There is a persistent misreading of the law, mostly by engineers.

It's actually pretty close to most other states laws in practice.

If you work for a very very very focused startup, sure, you may end up owning some personal stuff. You would in a lot of other states too.

If you work for any mid-sized tech company or larger, you probably won't own much, unless your interests are really off the wall.

The law allows employers to claim inventions that relate to an employers business, which for most mid-sized or larger tech companies, covers a lot (IE Apple's business is not just phones and computers, it's mapping, video editing, music software, word processing, distributed cloud services, etc).

In addition, if your invention relates to any actual or "demonstrably anticipated research", that would be covered too.

So if's demonstrable that apple was going to start exploring (not producing) social games, any social games you made (direct), or social platforms (they are "related"), or heck probably even social apps ('related' to that research) or ... would also be arguably be covered.

Over time, the research of most tech companies quickly expands to cover almost everything (since they frequently seek new markets), even if they never do it, ....

Re:How to Go From Google Engineer to First-Time CTO by VladRussian2 on Monday September 09, 2013 @03:33AM (#6352271)
>Isn't this the whole point of the perk?

why it is considered a perk? Ability to configure tools/workspace (at the $3-5K cost) by an employee (who costs $200K+ to the company) to maximize productivity of the employee and/or time the employee spends working productively at the workspace - doesn't it sound like a "perk" for the employer?

Re:How to Go From Google Engineer to First-Time CTO by altero on Monday September 09, 2013 @05:54AM (#6352541)
Please do not be so negative. They also provide other great stuff such as chairs and toilet paper.