Skip to main content

The anti-Google crowd has a point

I'm looking at this backlash against Google and other SV tech co.s and surprisingly find myself on the side of the 'backlasher's. The news articles emphasize the SF hippies, but I think the deep root of it all is the basic social contract these companies are breaking. There is an idea, and it works well. You start a business on the street. You probably hire people who are local, you serve people who are local. You pay taxes to the local government. The government fixes the roads and sets up bus service and educates your kids. Your customers increase in number and their ability to pay. Your business lasts longer. Google and co seem to believe they can get away with creating their own parallel universe of buses and other infrastructure. But they would do much better to pay more taxes, especially local taxes, so that EVERYONE had a better bus service. Yes, their customers are more from outside SV than not, but their workers live here. If SF becomes a shitty place to live they will start to lose workers. Workers will not feel safe/happy in SF. When they go somewhere else, they might start out working remotely for google, but they might develop more ties to a different local business where they work. They might start working for them. These companies might be competing with Google. Wouldn't it just be better for Google and Co. to simply pay a little extra in taxes and make SF a much better place to live in?
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Remove field code from Word document

e.g. before submitting a MS, or hand manipulating some formatting because Word does things (like cross-references) so half-assed [from here ] Select all the text (CTRL-A) Press Ctrl+Shift+F9 Editing to remove anonymous comments that only contain thanks. I really appreciate the thanks, but it makes it harder to find comments that carry pertinent information. I'm also going to try and paste informative comments in the body of the post to make them easier to find.
24 comments
Read more

h5py and multiprocessing

The HDF5 format has been working awesome for me, but I ran into danger when I started to mix it with multiprocessing. It was the worst kind of danger: the intermittent error. Here are the dangers/issues in order of escalation (TL;DR is use a generator to feed data from your file into the child processes as they spawn. It's the easiest way. Read on for harder ways.) An h5py file handle can't be pickled and therefore can't be passed as an argument using pool.map() If you set the handle as a global and access it from the child processes you run the risk of racing which leads to corrupted reads. My personal runin was that my code sometimes ran fine but sometimes would complain that there are NaNs or Infinity in the data. This wasted some time tracking down. Other people have had this kind of problem [ 1 ]. Same problem if you pass the filename and have the different processes open individual instances of the file separately. The hard way to solve this problem is to sw...
Post a Comment
Read more