wants to learns computer programming languages /codes then go to the link for tricks and tips to learn coding
https://trickytricktolearn.blogspot.com
https://trickytricktolearn.blogspot.com
What I Learned from Working 32 Hours a Week
41–50 of 111 posts
Re: What I Learned from Working 32 Hours a Week
#42Earlier quoted context omitted.
This is why working remotely is fantastic for work life balance. I can do my personal tasks, travel, visit my family, etc. and still be available.
How are you available when you are traveling and visiting your family?
Family: Laptop, internet at family member's home, work in the day.
"Vacation" travel: Haven't done this myself (outside visiting family) but have had colleagues who did it without issue. Available and worked in the day, did vacation things in the evening presumably.
Re: What I Learned from Working 32 Hours a Week
#43We've been doing 4-day/32-hour weeks at Wildbit for over a year now, and it's been great. We're a remote-first team of just under 30 people spread across quite a few time zones. It's a mental hurdle at first, but the company has continued to grow and be as productive as we were before.
We're all just much more mindful of how we each spend our time these days. We also strive to reduce meetings and lean more on asynchronous communication in order to reduce interrupting each other. That lets everybody focus more and get more high-quality work done in fewer hours.
Our initial write up: https://wildbit.com/blog/2017/05/31/experimenting-with-a-4-d...
The follow up with what we learned and what we adjusted: https://wildbit.com/blog/2017/10/19/4-day-work-week-update
Re: What I Learned from Working 32 Hours a Week
#44The author had a lot of vacation days left, and instead of taking them all at once, decided to give himself a bunch of 4-day work weeks. I wondered recently about the feasibility of doing this, does anyone know how open the average employer is to this sort of thing?
Vacation days are fine for short-term, but why not negotiate a permanent 4-day workweek? Lots of programmers have done it, e.g. https://codewithoutrules.com/2018/01/08/part-time-programmer... (also linked elsewhere in the comments).
Re: What I Learned from Working 32 Hours a Week
#45Earlier quoted context omitted.
That's what i notced with my friend in the managerial position. He can spend most of the time in Work From Home mode, has really good pay grade, and can't rest. He's looks like he's on a wrist band leash getting mails every 2-3 minutes and needs to somehow react on 10%. He doesnt do much other than be available 12-16h 6-7days a week. It's taking more toll than one would expect.
I could never understand why would someone accept these jobs. What's so great about becoming a manager and work 60h/week? How's that better than 40 a week as a subordinate and letting someone else worry about all the office drama?
I'm guessing it is something to do with money in most cases.
Re: What I Learned from Working 32 Hours a Week
#46Earlier quoted context omitted.
That's what i notced with my friend in the managerial position. He can spend most of the time in Work From Home mode, has really good pay grade, and can't rest. He's looks like he's on a wrist band leash getting mails every 2-3 minutes and needs to somehow react on 10%. He doesnt do much other than be available 12-16h 6-7days a week. It's taking more toll than one would expect.
I could never understand why would someone accept these jobs. What's so great about becoming a manager and work 60h/week? How's that better than 40 a week as a subordinate and letting someone else worry about all the office drama?
Cannot speak for all but usually its money. Many companies cap technical tracks pretty fast while management is uncapped. Next as as you go further in your career then management as a nearly universally considered a valid next step. For me, my manager was fired and rather than having to deal with hiring my boss (for second time), I took the role even though I knew I would dislike the politics/drama.
Re: What I Learned from Working 32 Hours a Week
#47Earlier quoted context omitted.
This is a good point. If you're a go-to expert in some category at your workplace, your availability and responsiveness might be too valuable to give up.
you might want to avoid having "go-to" experts at work because when they leave you might be screwed
Yep, definitely agree. Increasing the bus factor is always a good idea.
Re: What I Learned from Working 32 Hours a Week
#48Earlier quoted context omitted.
How are you available when you are traveling and visiting your family?
Family: Laptop, internet at family member's home, work in the day. "Vacation" travel: Haven't done this myself (outside visiting family) but have had colleagues who did it without issue. Available and worked in the day, did vacation things in the evening presumably.
I've done vacation travel before. Worked out well as we were able to take a longer trip and relax a bit more (traveling with two kids under 2 can be stressful). I only ended up taking 3 days vacation on a two week trip.
Re: What I Learned from Working 32 Hours a Week
#49Earlier quoted context omitted.
That page was worth a visit just for the Rosario font.
Something about it feels satisfying.
I think it ticks several boxes at once:
- It's a sans-serif with contrast, which is a rarity per se, doubly so with stroke widths that don't look weird (considering that the brain is unused to sans-serifs with contrast and usually begins mildly panicking at seeing them in body text). Triply a rarity with interesting letter shapes. Rosario has the perfect contrast: just enough for it to be noticed, but not so much as to look unnatural.
- It has humanistic features, but with sliiight hints at serifs. The glyphs are playful as heck if you look closely, but again just enough to not overstep the boundary of taste.
- Stroke widths, the blackness, is perfect for reading the body text, at least on the screen. It's not one of those twiggy and feeble grotesks. At the same time, its (semi)bold doesn't look like a forest of black concrete slabs: it again has just enough weight to stay out, but not more.
It would be a perfect font for me! If not for one ailment: it only has variations on Latin scripts, and no Cyrillic. Sigh...
Re: What I Learned from Working 32 Hours a Week
#50I've often felt that a 5 day work week is about availability , not raw productivity. I could easily compress all of my weeks work into 30 hours or less, but that's not what my managers and clients value. What they value is the fact that I'm making progress on my tasks, and that my reachability is not preventing anyone else (people above me or below me) from making progress on their tasks
This is a valid point, managers and clients value availability and that's mainly the reason why they want you full time. In fact IMHO many prefer availability to productivity. Being available 40-50h a week is rather tiring though and it can affect productivity. For example I found that I perform better on a 32h/week. The availability problem can be solved by having the team cover the full week (different shifts with…
I think "the reason why they want you full time" is usually because they can (very few people push back) and/or they are in roles where more time put in equals more work done. For example, as a manager doing 1:1 is still tiring, but if you aren't paying 100% attention, that doesn't cost money unlike bugs in code.
Almost nobody can do more than 3 hours of heavy concentration/flow work regularly. Add another two or three hours for meetings, answering emails, triaging bugs, etc. and you get ~30h per week. When I'm in a position to do so, I tell my team that I'd rather have 3 hours of great work than 6 or 8 hours of mediocre work full of mistakes.
Still, it's an uphill battle culturally. And sometimes even developers don't like it, since they can't hide a lack of output behind hours in the office. I think this is a positive, because as a team lead you notice issues quicker, e.g. if someone is having a rough week. But it's also a good way to "unmask" people who e.g. embellished their skill level during the hiring process and maybe aren't a great fit for the role. That way, you can get them the training they need, or find them a different role.