I hear that they still plan to have a mechanism for patching zero-day vulnerabilities. Don't know how exactly, but a slide in one of Hanselman's talks mentioned it.
I've been thinking about this a lot lately. The ideal solution seems to be to encrypt traffic between all hosts on the local network. Are there any good resources for how to setup IPSEC or something on a local wifi network?
The solution already exists in the form of WPA2-Enterprise auth (802.1x), but support is still fairly sparse on consumer devices like cheaper WiFi routers or media streamers. It's also difficult to configure and manage, for the average user.
And today most people I know who mention it keep saying XP when they mean pair programming. Not as if it's one of many practices in XP, but as if the two were synonymous. Please tell me this isn't common.
People latch on to what aspect they don't like of a thing and it becomes synonymous with the thing itself.
With XP, sadly, this is true. Most times you bring up the XP practices individually, and they're "good ideas". You say XP, and they say "fuck pairing!"
Even if certificate authorities are compromised by major governments, SSL is still enough for now to keep my credit card safe from the shady guy in the back corner of the coffee shop. Or to keep my Google searches private from the techies at my ISP.
There are some upcoming workaround that will help too like cert pinning or DANE.
OpenVPN can be set to route only certain IP blocks to the tunnel. I sometimes do prefer to route everything over the vpn though, especially at coffee shops that filter specific ports.
The standard sshd does not log failed passwords. A few years ago I was seeing a lot of brute force attempts and I was curious to see the passwords. The only way I could do it was to edit the source code of sshd to add my own logging line and recompile the whole thing.
I used to start a lot of my sentences with "I think...", "In my opinion...", or "To me it looks like..." and I noticed my emails would commonly go unresponded to, or worse: the conversation would go directly opposite of the point I was trying to make.
Lately I've been experimenting with just saying "x is y" or "x is broken the fix is y". Things seem to be working out better for me that way. It keeps my emails from getting cluttered and the words are obviously my own perspective and opinions, which I will sometimes make explicit at the end.
It is irritating that facts and opinions and everything else can't be kept separate from technical discussions, but that's just how many people communicate and there's not a lot that can be done if you want to include them in the conversation.
I did it for a few months while moving to a new city before I had my own place. It wasn't too bad. I'd buy a basic coffee (and sometimes a cheap bagel) and find a corner to setup in. At lunch, I'd pack up and find something to eat, then head to a different place and buy a coffee. Sometimes I'd go to the library instead. It wasn't any more expensive than going out with coworkers for lunch every day...
Most businesses did't seem to mind people hanging out, makes the place look busier I guess. I figure as long as there are other empty seats I'm not in anyone's way. That said, if I did it again I'd probably tip a lot more than I had been tipping.
This is pretty much exactly the way I do it. Best places are usually the big chains with low wage workers who do not care the slightest how many hours you are hanging around there. I have about 4-5 shops within walking distance and rotate them around. In half of them they already discount my drinks and greet me like an old friend.
I was working in coffee shops for 2 years and thats what I did.
As for getting stuff done, if you find a coffee shop where people are working / studying, its great.
I have worked remotely from SE Asia for the past 8 years; Id go to visit clients in the USA two times a year and they would give me a cubicle in Palo Alto. I really enjoyed the company of my co workers, all great folks and it was great to see them face to face after IM ing them for 6 months. But to get actual work done, Id go outside and sit in a Coffee Shop...
The article is spot on about the downsides of working remotely - the biggest issues are routine, discipline, and communication.
What it does not mention are the downsides of working in the office:
- Distractions by chatting with friends
- Distractions by meetings
- Lack of discipline because they pay you to warm your chair for 8 hours. If i am in the office, its work time - obviously. When I work remotely the only way to prove I was actually working is getting shit done.
I've coded in coffee shops for a few years. I usually spend the first half of the day at one and then switch at lunch. It can get expensive, but I usually justify it by telling myself I'm earning money (not completely logical).
