Long Hours Culture

Any time you have worked long hours it is a sign of a broken process.--------------------------I see the point they're trying to make, but this is the problem with speaking in absolutes ...My personal preference (and I suspect other developers do this too, but I could be very wrong about that) is to work when I'm in the zone ... sometimes I can go for 8 hours, others I can go 24 hours straight without any trouble (other times I don't get anything done for a couple of days) ... during pr

Yes, if you're starting your own business then it could help you to work as much as you can.However, most people do not run their own business. Most people are low-level code monkeys in large firms where individual efforts aren't business critical. When your project gets cancelled for the 3rd time and you still get a raise, it finally clicks that your work doesn't really matter. This takes a psychological toll. As a result, most people I know in FAANG who are 28+ years old will

In a place I worked, if someone left at 5:30 pm, the CTO used to joke "half day today?", even though the person came in at 9 am.In many places I worked in the US, it is somewhat of a badge of honor to spend long hours at work (how many of those are actually productive, is a different story). And these aren't even startups.This can't continue - an entire generation of people have been brainwashed that hard work = good, costs be damned. It has to change.IMHO, the only

It seems unreasonable to dictate the way your colleagues work because it doesn't match your own value system. If the culture of the company/team is fast paced or long hours, maybe it isn't the right fit for you.Generally speaking though, companies should value output and results over hours. Easier said than done. Additionally, value should be placed on what one commits to do and delivers on. So if somebody is constantly having to pull late nights to complete work, they may be o

Founders want to see what you're doing at all times, they know that you have to out in remote double time to actual get anything done. I can't solve incredible engineering problems with 5 people talking at the same time for 6 hours, I wind up having to work 18 hour days with 8 hours of face time sitting and chatting to make the crew of kids happy. As a senior dev my workload is triple the juniors so it's not unusual for me to have to do 80-120 hours a week for 40 hours pay to not

"The prevalence of social bubble-worthy companies whose value propositions are little more than "cat pictures" suggests an inflated sense of self-importance among the founders, and I can't expect to keep my level of enthusiasm in line with their irrational exuberance."i totally loled :)organizations that expect unreasonable working hours from developers or sysadmins are a bad place to work. the only places i consider it somewhat reasonable to work employees over 50 hrs / week are professio

YES! its worth telling managers and subordinates that we wont be working more than 40 - 50 hours. and that we should work both hard and smart in he alotted time ...then get the F out of work and do other things.i often find it refreshing to hear about the cool things people do when not working and bummed when i hear someone - especially one of my devs - worked through a weekend. then comes the difficult and uncomfortable chore of figuring out what i fucked up that caused them to have to work

I deal with this scenario everyday in a company I work with, where the founder expects everyone to work on weekends and late night (most days). Since it is an advertising agency, he accepts every work that comes his way from clients. He comes from Sales background and somehow believes that more work is equal to more money, which is not true. When it comes to any work where some amount of thinking is involved, Less work (Quality) == more money.Most of the people in the team are stressed and ar

It seems pretty obvious that you work at a very small company with little or no layers of management, and most likely, without any other typical constraints that most workers deal with -- like fixed hours, an inconvenient office or commute, lots of unproductive meetings, limited amount of annual PTO, lack of knowledge/understanding whether anything you do has actual impact at the company, etc. Putting in 70-80 hours week after week in a scenario like that where it's very clear you'

My experience is the same.The 80 hour a week salary (no overtime) culture is also prone to people just goofing off. So sure you are in the office 80 hours but only 30 of those are productive hours (at most).If you know you're expected to work 80 hours you will be on the clock 80 hours but not all of it will be "work."I found that with shorter work days people stay more focussed and make better use of their time because they know they need to.