3 ms·
I've tried working in the library on a number of occasions. The one bad thing I've discovered is that the WIFI sucks at pretty much every public library I've wo
by dlevine 16y ago
I've tried working in the library on a number of occasions. The one bad thing I've discovered is that the WIFI sucks at pretty much every public library I've worked at. And I think that's a sample size of 4 or 5 libraries. I live almost right next to the main branch of the San Francisco Public Library, and every time I've gone there to work, I've left after a while because the Internet was too slow or didn't work quite right.
So if I want to get any coding done, and need access to the Internet, I have found the library to be a pretty bad place. If I'm just doing some quiet reading, the library can be great.
- ja27 16y agoI've worked from two libraries near my house quite a bit as well as a couple sandwich shops. (I can't stand the smell of burning coffee.) The sandwich shops are less distracting to me. All the conversations and background noise blend together for me. I try to avoid rush times and busy days so I'm not tying up a table when they need them. The libraries are ok but have some problems. Neither really get many homeless guys but both have a lot of kids, especially in the afternoon. With big open floorplans, that's more noise than I can ignore. The availability of books sometimes distracts me, but to be honest, the book collections are now so old and unimpressive that it's not a big deal. The other problem is that the libraries block a number of things on their network, like most webmail, instant messengers, and most VPNs. I'm still able to use https for GMail and my work tunnel so I can work there, but it seems unnecessarily restrictive.
- wtn 16y agoYes, SFPL wireless network internet is terrible.