101–110 of 136 posts
"here’s what we’ve been fortunate to achieve:"
Even being really good you gotta have some luck too.
Being able to see that I think makes people being not assholes when talking about their achievements.
Thanks from those of us who are stuck with Time Warner Cable ;)
I worked at StreetEasy for 3 years (helping lead the dev team and writing lots of code) when it was a fast growing startup and we didn't work a 4 day week, but we worked normal business hours (9-5,10-6'ish) and never ever worked weekends - unless you felt like working on some code. One of the co-founders there had the opinion that we were in it for the long haul, not for the sprint, so why burn out early. This seemed…
Congrats on your company's success! However, I'm surprised that you single out a 40-hour work week as though it's something exceptional. Isn't that the standard? I would never consider joining a company that expected me to work weekends. I hope that's not as common as you imply.
Congratulation! This is how it should be done. And I have a question.... All professors of management and organizations understand that work week should be defined differently for knowledge workers. And that most the important quality of knowledge workers is initiative. So if you have 80 hours work week and all innovation or initiative is dismissed, that can mean two things: 1) you are not "knowledge worker" but just…
- one was in the 40-50 hour week normal expectation, no serious spikes due to the way we worked over a 2 year period. - one was 40-50 hours per week with regular (every 2-3 month spikes) - one was completely insane and expected 60+ hour weeks (it was saner pre-"coming out party", but barely). This company had no concept of planning, if things were behind, the solution was more meetings rather than cutting features. Senior management on the team was more apt to either not be around or play ping pong while engineers worked away. Technically, it was the most diverse project I ever worked on, but the most poorly run...that was a reflection on immediate management. Launch was 60+ hour weeks plus I got the fun of doing ops since I knew most of the system.
That third company taught me a lot, probably most directly, the value of work life balance and, especially as a lead, pushing back on poor planning and management. My goal as an engineer has always been to deliver and provide end user delight, but that needs to be balanced with balance for myself.
Anyone have thoughts on how 4-day work week compares to a 5-day-but-shorter-days work week (discussed a bit yesterday at https://news.ycombinator.com/item?id=6912645 )?
I work for Treehouse. The 4-day work week is amazing and I feel it'd be very hard to go back to 5 days a week. What do I do on my Fridays? If I have errands, they get run. I usually pop-in and off my computer. Sometimes I actually am working, but I'm "playing". I'm a data scientist and I love my job. I love working on my tools and I love trying new methods. So I might be improving my D3.js skills. Or learning Python…
Congratulation! This is how it should be done. And I have a question.... All professors of management and organizations understand that work week should be defined differently for knowledge workers. And that most the important quality of knowledge workers is initiative. So if you have 80 hours work week and all innovation or initiative is dismissed, that can mean two things: 1) you are not "knowledge worker" but just…
