5 ms·
I was really skeptical of remote work before I took my first and current remote job, which surprisingly paid better than my former non-remote job. Conceptually,
by JMTQp8lwXL 7y ago
I was really skeptical of remote work before I took my first and current remote job, which surprisingly paid better than my former non-remote job. Conceptually, It was totally outside my Overton window. But having experienced it, my perspective completely changed. I don't mind doing a good job, but I underestimated how valuable the autonomy of my time would be, it's such a blessing. An occasional hour or two mid-day break really suits me. Those days, I am stretching my work day, but more relaxed and less stressed. My output is higher than working in an office.
- ebg13 7y ago> An occasional hour or two mid-day break really suits me. What...like lunch? I don't know any software engineer who doesn't regularly take more than an hour for lunch.
- JMTQp8lwXL 7y agoWhen I worked at the office, "lunch" was available onsite from 11:30 to 1:30 and onsite was 30-90 minutes from my house, depending on a very wide range of traffic conditions. It can be food, it can be laundry, it can be errands. Things I couldn't squeeze in before.
- blaser-waffle 7y agoI've made a habit of using "lunch" to make dinner, via a crockpot or slowcooker. As in, I work remote and use my "lunch break" to throw stew (or curry, or soup, or a roast, etc.) together and have that cook for the rest of the afternoon.
- kharak 7y agoI regularly do 15 to 30 minutes. In my current project, it's between 30 and 45 minutes due to socialising with coworkers. These minutes are not paid, meaning I have to stay longer at work, less free time. Long lunch almost always feels terrible to me. Short lunch is like a treat for myself. I've never seen engineers doing longer than 1 hour breaks at a regular basis. Even 1 hour is rare.