Earlier quoted context omitted.
Some of my best code was written after basically abandoning the problem for a day. Of course, the problem wasn't really abandoned -- I was thinking about how to solve it the whole time. But I wasn't writing any code. Forcing yourself to write isn't necessarily best.
One of the most effective things you can do is become a virtual smoker. Smokers get an urge and step out for a cigarette every hour - or every time they get stuck. I don't smoke (never have) but I am trying to emulate that; the most effective way to solve a problem is to step out and do nothing for about 5 minutes. Take a walk. Look at the trees. Anything. Then when I come back I have either solved the problem or dec…
How to work remotely as a software developer
101–110 of 113 posts
Re: How to work remotely as a software developer
#102Re: How to work remotely as a software developer
#103Earlier quoted context omitted.
I think if you work a whole day in a coffee shop, you're kind of a jerk. I occasionally go to a coffee shop to work for an hour or so. Many times it's been the most focused hour I had that week. The biggest thing is to remember that you're in a place of business. If you're going to take their space, buy something, tip well, and be courteous to the people around you.
THANK YOU A netiquette for coffee shops, I wholeheartedly agree. I work at coffee shops a lot; I keep sitting there when I can see there are plenty of empty tables - that means my sitting there is a net positive for the Cafe: I might consume more, and often do. And having customers is better than having none, it attracts other people. If I see that many customers are coming and that I might actually block people from…
On the other hand I can relate to the concept of doing good by those whom you rely on, a symbiotic relationship and what not. That's a very pro-society thing and I suppose that's respectable.
Re: How to work remotely as a software developer
#104Re: How to work remotely as a software developer
#105I've never tried working from a coffee shop but it seems people do. How does that work out financially? I imagine they aren't too pleased if you just buy a coffee and then occupy space for 5 hours. But I don't really want to spend a fortune on excessive caffeine consumption and $5 bagels.
I think if you work a whole day in a coffee shop, you're kind of a jerk. I occasionally go to a coffee shop to work for an hour or so. Many times it's been the most focused hour I had that week. The biggest thing is to remember that you're in a place of business. If you're going to take their space, buy something, tip well, and be courteous to the people around you.
In turn, they _like_ having me around. I've sold old hardware to one, gotten novel draft feedback from another, and have plans for a weekly anime get-together with another. That, and I even get plenty of free drinks!
Re: How to work remotely as a software developer
#106Earlier quoted context omitted.
THANK YOU A netiquette for coffee shops, I wholeheartedly agree. I work at coffee shops a lot; I keep sitting there when I can see there are plenty of empty tables - that means my sitting there is a net positive for the Cafe: I might consume more, and often do. And having customers is better than having none, it attracts other people. If I see that many customers are coming and that I might actually block people from…
I realize this is awful 4chan of me; but that seems rather beta of you, in that you're essentially swayed by the flow of traffic of the establishment, in a scenario where you're supposed to be getting shit done. You make it sound like you're only privileged to be there when it's convenient for the coffee shop owners, and that seems to me like a tense place to exist. On the other hand I can relate to the concept of do…
If you act considerately and don't cause problems (like occupying space when you are not spending) then this is less likely to happen, so there is certainly a degree of self interest.
Re: How to work remotely as a software developer
#107Earlier quoted context omitted.
One of the most effective things you can do is become a virtual smoker. Smokers get an urge and step out for a cigarette every hour - or every time they get stuck. I don't smoke (never have) but I am trying to emulate that; the most effective way to solve a problem is to step out and do nothing for about 5 minutes. Take a walk. Look at the trees. Anything. Then when I come back I have either solved the problem or dec…
I honestly wish I could do something like that at work. I already do it all the time at home.
Re: How to work remotely as a software developer
#108Earlier quoted context omitted.
I honestly wish I could do something like that at work. I already do it all the time at home.
I do this by going to the water cooler for a refill. I use a small cup, so I go every hour or so. I usually take the slow way there, and think about my work on the way.
Re: How to work remotely as a software developer
#109Earlier quoted context omitted.
I did this for two years. The key is to switch it up. I'm lucky enough that there are many different coffee shops in my area that I can go to. The general rule of thumb, if you're planning on spending multiple hours in a single place, is to buy a little something each 1 to 2 hours. I've seen many, many people buy a single tall coffee, nothing else, and then sit in the coffee shop for 4+ hours. These people are jerks.
If the coffee shop is full and they are inhibiting other paying customers, they are jerks. If they are disturbing the network, they are jerks. But what if there's plenty of seating, and they're working off of their own internet? Are they still jerks?
Re: How to work remotely as a software developer
#110Earlier quoted context omitted.
A man is a fool not to put everything he has, at any given moment, into what he is creating. You're there now doing the thing on paper. You're not killing the goose, you're just producing an egg. So I don't worry about inspiration, or anything like that. It's a matter of just sitting down and working. I have never had the problem of a writing block. I've heard about it. I've felt reluctant to write on some days, for…
Writing code when you know you dont have a solution is a complete waste of time. You end up with bad code you have to throw away. Or worse, you dont throw it away and end up with huge tail end costs of user errors, QA time, futile attempts to fix the rotten, and eventually rewriting the whole thing anyway. Writing is apparently different in this regard.
Programming isn't just about generating more lines of code. It's about understanding the problem you're working on. Sometimes writing code is a good way to understand the problem.