> There is a story of mysql as a company who had an employee who was not reachable for a few months.

How does this have anything to do with WFH? If someone is not reachable and has not communicated up front they are going to be out, then fire them. This is no different than if they just stopped showing up to an office job.

I always love the arguments that are around 'well how will I know my programmers are working'? Well, how do you know they are working when they are in the office?

"There is a story of mysql as a company who had an employee who was not reachable for a few months."

I couldn't find the story with some (brief) googling. What makes it different to "they didn't turn up the office for a few months"? Were they still getting work done?

And that is the reality of the situation. Work from home simply doesn't work for many people because they don't have the discipline or morals to make themselves work 8 hours without supervision.

> I personally like to have the option to work at home when necessary and i might get more stuff done at home i also might just not work.

I might just not work at the office either.

MySQL is a great example of it working. Hundreds of employees, the vast majority remote, regardless of where they were located. Sold for $1B.

It was my first remote job and I enjoyed it immensely, so much so that I haven't had an office job in 10 years now, and have no desire to return to one.

I'm not sure I would take anything Yahoo is doing as an example of a good idea.

They did buy a share in Alibaba! Yahoo's share in Alibaba is worth more than the total value of Yahoo. So, if you buy Yahoo, fire all its staff, close all its web sites, and then liquidate its share in Alibaba, you can make a lot of money.