Live data from Hacker News

Cutting your salary by 40%

codewithoutrules.com

171–180 of 451 posts

Re: Cutting your salary by 40%

#171

Earlier quoted context omitted.

I'm far from a low level grunt in my orgs. So far working hard has proven to be key in moving up. While in my field there isn't such a clear line between management and non management my last two titles have have had a foot in the management side. In seems to be en vogue to despise hard work today (unless it is manual labor).

There are certainly fields and/or companies where ones pay and position can be commensurate with their effort. Most would agree that these are the exception not the rule, congratulations if you happen to be in that position.

I really do think that is true of most field though. And carry that attitude around is the easiest way to make it true.

Re: Cutting your salary by 40%

#172
post #80

Earlier quoted context omitted.

What is your methodology for determining the change in defect rates and code quality?

We use Pivotal Tracker, and it's pretty easy to see how many bugs are popping up and how often. Code quality shows up in your velocity over time. My favorite saying right now is "quality is future speed". We also do regular reviews to assess things like cyclomatic complexity and how well SOLID principles are being followed.

The quantity of bugs popping up and code quality haven't got what I'd call a well-understood relationship. How do you reconcile that?

Re: Cutting your salary by 40%

#173
post #159

Earlier quoted context omitted.

What would you say if I told you in a given work day, I only work maybe 3-5 hours (including meetings) and still meet all targets? This has been consistent for every job I've ever had.

I can definitely believe that. But in my line of work I'm expected to bill at least 8 hrs/day to the client regardless of my personal productivity.

> Pfft. A man-hour of labor is a man-hour of labor

> I'm expected to bill at least 8 hrs/day

I bet you're capable of far deeper, more intellectually stimulating and rewarding work than you're doing now.

Re: Cutting your salary by 40%

#174

Earlier quoted context omitted.

You can progress in your career very rapidly by doing 40h of high quality work per week. I know many young people (my generation) who are in their late 20s or early 30s and have made a very fast career progression already and didn't need to work 80 hours per day at all. Also for software engineers you have to take into account continuously upskilling yourself to know the latest tech is something which takes a lot of…

Like a lot of people in financial technology and HFT, I dont work outside projevrs very much. I get a lot of my experience with newer tech inside my job and as well have to deal with some fairlt heavy secrecy issues. But aren't you just trading the location of work for the most part? I get that experience from within my firm on projects I'm working on while others still work on their skills just outside their employm…

>> But aren't you just trading the location of work for the most part? I get that experience from within my firm on projects I'm working on while others still work on their skills just outside their employment? It is still "work" in a sense.

Not really because it doesn't feel like work. You don't have to code in your free time, you can go out with family / gf / friends and do some fun social activity, you can do sports to maintain healthy and fit body, you can travel, read a good book etc... so you get the choice how to spend your free time.

For example with sports, if you are working 80 hours per week it is not possible to do any sport seriously. You need at least 5-6 hours per week if you want to really get good at any sport. It is also incredibly unhealthy to work 16 hours per day. You are literally destroying your body.

And if you decide to write code or do something technical in your free time you are in charge of defining the project you will work on, interesting in AI/machine learning, big data, distributed systems, specific algorithms or problems? You can work on the exact problem that intrigues you. Can't do that for a company as your work is not decided by you.

>> I realize many don't get the same intellectual benefit from employment that i enjoy but trashing people who do and take advantage of it doesn't seem appropriate.

I am not trashing anybody. Just saying that you don't need to work 80 hours per week to get promoted and progress in your career. Quality and productivity matters, not hours you spend sitting in the office.

Re: Cutting your salary by 40%

#175
post #121

I enforce a militant "40 hours only" policy for my employees, and it's incredible for productivity. When you work longer hours defect rates increase, code quality drops, and things are on fire all the time. You also lose really good people due to burnout. Sustainable pace is super important for creating and maintaining high performance teams. Crassly, it's just a more profitable way of doing business. I wish more man…

I partially agree with you, but personal productivity varies. So in our company we have a rule "work as much as you like, usually we expect no less than 30 hours, but it is OK to do 50. Anything beyond these ranges is odd".

Some thinking-intensive work can bring you at the edge in just 3 hours a day. After that, you generate more problems than solutions. Especially mathematicians are prone to this. Similar cases in software development need to be respected.

Re: Cutting your salary by 40%

#176
post #21

As much as I'd love to believe the "work more than 40 hours a week, because SCIENCE!" party line, I have a hard time accepting it, and I think so do most people who hear it (outside of HN, at least). For one thing, it's highly convenient that the standard US work-week happens to be the exact "correct" amount of hours to work to maximize productivity. For another, anecdotally at least, most people know plenty of peopl…

"For one thing, it's highly convenient that the standard US work-week happens to be the exact "correct" amount of hours to work to maximize productivity."

Maybe the gov't set the standard informed by our biology?

Actually 40 hours isn't "exact". It's close though. Why?

First weekends. Weekends mean that a 7 day week has 5 work days. Typically weekends are still off (bros' gotta climb El Capitan). If instead of 2 days off every 7 we had 1 every 10 (a failed metric innovation pushed during the French Revolution) we would work 26% more, or 50 hours/week @ 8 hours a day. I don't know that 2 of 7 gives us much more needed reset than 1 of 10, but that would be a sucky weekend.

To test, at an interview try to hire someone with "we work 11.1 hour days, 9 days in a row". 11.1 hour days 9/10 days = 70 hour 5/7 weeks. You'd hire no one.

So 2-7 weekends are the first restraint.

Then we have our biology. 8 hours of sleep (give or take an hour or two), leaving 16 hours.

Not doing the same activity for 16 hours straight is necessary for all humans except the most severe case of autism. 8 hours to bath, eat, greet your spouse, play with your kids, ect. These are things we're evolutionarily wired to do btw (we're social beings whose parents both contribute, typically, to child rearing).

So why 40h? Could be 30 (B. Russell argued 100 years ago that we need half that). Could be 50. Having a balanced life @ 60hr weeks (12 hr work days) is already impossible.

Finally, I want to point out two things:

1. I really doubt any of these 70hr. proponents will out-produce a 70 year old Carthusian monk who make their hipster beers. And they spend most of their days praying. Why? These monks are focused. We're all dibbling about on Facebook. 70 hrs? @ 100% yeah right! More like 70 hrs @ 30%!

2. Most developers live in our own filth (kinda hard to clean @ 70 hr weeks). That's literally[x] unbecoming.

[x] to be human is to, among other things, have a sense of aesthetic beauty and to be an animal is to have some basic sense of self-care. Even high order animals take care of/decorate where they live. Therefore, to live in our own filth, to neglect our hygiene, is to reject or very nature. Therefore, we are literally unbecoming.

Re: Cutting your salary by 40%

#177
post #121

Earlier quoted context omitted.

I partially agree with you, but personal productivity varies. So in our company we have a rule "work as much as you like, usually we expect no less than 30 hours, but it is OK to do 50. Anything beyond these ranges is odd".

What would you say if I told you in a given work day, I only work maybe 3-5 hours (including meetings) and still meet all targets? This has been consistent for every job I've ever had.

Well many managers and execs might respond with "well then, give 'em more work! We obviously aren't giving them enough to do!"

Salary exempt is usually a losing game for developers. Crappy places will say "we pay you a salary to get the work done" and under staff and/or overwork. If it takes you 60 hours then you have to work 60 hours. But if it only took someone 30 hours they can't leave early because a) deadlines will be tightened to ensure 40+ hours or b) more work and assignments will be given.

Re: Cutting your salary by 40%

#178
post #23

Earlier quoted context omitted.

That sounds really horrible. I'd rather be out of a job than work for some place like that. What kind of a job are you looking for? I assume you're some kind of engineer, but on my phone so didn't look into anything.

I'm a Level 2/3 SysAdmin/Engineer in the ATL area. But I do "develop" in POSH if you can call that coding. I'm learning python now.

Are you interested in working remotely?

Re: Cutting your salary by 40%

#179
post #121

Earlier quoted context omitted.

I partially agree with you, but personal productivity varies. So in our company we have a rule "work as much as you like, usually we expect no less than 30 hours, but it is OK to do 50. Anything beyond these ranges is odd".

Some thinking-intensive work can bring you at the edge in just 3 hours a day. After that, you generate more problems than solutions. Especially mathematicians are prone to this. Similar cases in software development need to be respected.

Grothendieck worked twelve hours per day every day of the week for a decade.

Source: https://math.stackexchange.com/a/874290/161054

Re: Cutting your salary by 40%

#180
post #21

As much as I'd love to believe the "work more than 40 hours a week, because SCIENCE!" party line, I have a hard time accepting it, and I think so do most people who hear it (outside of HN, at least). For one thing, it's highly convenient that the standard US work-week happens to be the exact "correct" amount of hours to work to maximize productivity. For another, anecdotally at least, most people know plenty of peopl…

Well said. I share your suspicions about 40 turning out to be the magic number. I also notice that these articles never seem to allow for differences between people, which flies in the face of my 25 years of experience. I've always felt most comfortable working seven days a week, at a manageable pace each day. Other people need those weekends, and are happy to put in long hours in the week. One of the most productive people I ever worked with seemed to work literally all the time.

As for whether or not it's "exploitive", I'm sure it is, under some circumstances. Some poor dev, trapped by an H1-B, getting ground up with hours upon hours of billable work, for example. But a lot of us are paid through equity. In such a case it's perfectly reasonable to sacrifice for the good of the company in which you have a stake.

Post reply on HN