If that means you only need to work 5 hours a week, so be it.
Ask HN: Are most of us developers lying about how much work we do?
241–250 of 1001 posts
Re: Ask HN: Are most of us developers lying about how much work we do?
#242Long time manager here. I call this "work-shy" and it is neither ubiquitous nor rare, I'd guess about 10%-20% of all employees, and it's certainly not unique to software or even to white-collar work. You should think of this as a problem. Even if it's not for your boss or your teammates (and it will be, eventually), it is for you. It is soul-crushing to fill up the hours. Two pieces of advice: 1) The "good" solution…
Why should I work more? How will that improve my life? My self-worth is derived from what I do outside of work to the extent that I don't prioritize professional validation. The primary reason I work is for money. I make enough money that I can live a comfortable life, I have few material wants, and I can be generous with my money. I am on pace to likely be able to retire in my mid-50s. I recognize that I likely could be making more money if I worked harder, but it wouldn't be proportional because compensation is not tied closely to production for individual contributors. A 50% increase in effort won't yield a 50% salary increase. Most of the added value from my increased effort would be captured by people above me in the org chart and our company's stockholders.
As it currently stands, I don't find it that difficult to find a new job. I do spend some time keeping up with the industry, I am on HN after all, which tells you I care more about software development as a skill than some of my coworkers. It isn't that I dislike the profession, I simply don't see the reward in working harder primarily for the financial benefit of other people.
Re: Ask HN: Are most of us developers lying about how much work we do?
#243Earlier quoted context omitted.
> I know a few of those developers, and they sit right near me... In fact, this is so common that I can name the exact people at several jobs I've had. And I could mention them to my coworkers and they'd know exactly what these people's reputation are. Our feeling toward them is a mix of being impressed and being embarrassed. Impressed because there's something to be said for someone who works the system to their adv…
>but it's that getting something cool done is rewarding in its own right. Why don't they want that feeling… ? Cant speak for everyone, but in my case, Ive done the grind to get something cool done in my younger days. Ive designed, programmed and tested a differential braking system for a sizeable unmanned aircraft technology demonstrator, from hardware to drive the master cylinders, to the software with control of st…
Re: Ask HN: Are most of us developers lying about how much work we do?
#244Re: Ask HN: Are most of us developers lying about how much work we do?
#245I've been in companies, mostly smaller ones, where I've "crushed it" and shipped consumer products with small, scrappy teams and been very proud of my team and the goals we all achieved. And there was no way to hide in the cracks, and people spoke up if someone tried too.
I've also worked in soul crushingly terrible companies (Facebook, Intel, Microsoft, Ericsson, eBay) that cannot get out of their own way where tasks and features are wildly mis-estimated or just take an interminable amount of time to actually deliver.
Prior to my current position I was Lead developer for a big telecomms company, and I went from "highly productive" and delivering results with a small team -- we were small and we moved fast and we broke things. And it was glorious. Then I got "promoted" to a differnt team and regularly attended 19 scheduled, standing meetings per week, not including impromptu meetings with individuals of the team, and in a classic Office Space scenario, I had six different people I reported too. And I was still expected, by two of the people I reported too, to get 40+ hours of hands-on-keyboard time.
I am now back to a small, scrappy start-up team of four individual contributors and we have done more in five months than the team of 40+ was able to achieve in over 18 months.
A lot of the time, the environment will beat out of you any inclination to reach for the brass ring. It will actively beat you down. You either subsume yourself to it, or you find a different company.
But then, there are also those individuals which you just know are phoning it in, no matter the environment.
Re: Ask HN: Are most of us developers lying about how much work we do?
#246Re: Ask HN: Are most of us developers lying about how much work we do?
#247I've been a software engineer and managed software engineers for 20 years and worked in all kinds of businesses. This is both normal and mostly acceptable, in my professional opinion. Doing just as much work as your employer requires and no more is way less of a problem than employees who actively steal, commit fraud, bring drama and distract other team members, or are introducing defects because they've faked their…
It's definitely not acceptable.
It's a form of White Collar / 1st World Corruption.
Taking money from people with expectation of value, while not providing that value is Fraud.
Just because we don't always have great oversight, does not abnegate our responsibilities towards trying to do a good job.
This notion of 'I Can Get Away With It' and 'Other People Do It' is exactly the kind of logic that someone in an corrupt and dysfunctional system would use to accept taking bribes, or to commit other forms of common crimes.
'Wealthy Nations' are wealthy because people are organized rationally and effectively, - but we can't have oversight over everything.
'Wealthy Nations' run into dysfunction and bloat often due to systematic reasons, but also due to these kinds of scenarios and it's an example of where it breaks down.
Workers are adamant that they want to be 'trusted' to do their jobs and to work remotely - at the same time they want the ability to do 'nothing' in systems which necessarily can't have a lot of oversight, or don't because 'trust' ?
This is unreasonable populism: "Pay me, trust me, but I'm going to do nothing, and if you lay me off over Zoom, you're going to see it on CNN!"
If you want to live in a world of trust, it means you have an obligation to at least try to live up to your obligations.
Re: Ask HN: Are most of us developers lying about how much work we do?
#248I am a freelance dev and I only bill the hours that I work. But I am quite sure a lot of freelance devs just bill 8 hours of work a day, even if they only work 3 hours. My conscience wont allow me to do this in a remote work situation. Back when I worked in the office as freelancer, I did bill 8 hours a day, since I was expected to sit in the office 8 hours a day, regardless if I performed or not. In the past I worke…
http://hourlybillingisnuts.com
Ever since I read his stuff, I've been doing value-pricing, i.e. "here's what we both agree will solve your problem, and here's 3 price options, depending on my level of involvement".
Then if I can get it done in an hour or in a year, either way I get paid the same and the client gets what they paid for.
Realistic time estimates, though, are a separate matter.
Re: Ask HN: Are most of us developers lying about how much work we do?
#249You are not operating in isolation.
Your work has upstream dependencies (well defined requirements, things owned by other people being done first, communication from other parties, etc), that will form blockers on being able to execute on what is important.
Likewise, there are downstream bottlenecks; code you write has to be peer reviewed, tested, released, whatever else.
This, alone, is like a Kanban process; so long as you are not the bottleneck, you are going to have a lot of downtime, even while some other part (that is the bottleneck) may feel stressed and overworked.
But that's not even the only consideration! The 80/20 rule applies to software development, same as everywhere else. Is there more you -could- be doing? Almost certainly! Does it have anywhere near the value to you, the team, or the business, to warrant it getting attention? Assuredly not. Even if you devoted your remaining hours to things you felt you could get some traction on, the return on investment would be super low; likely so low as to not even be noticed.
Between the two of those, it is quite possible for people, a majority within a company even, to still provide close to if not their actual maximal value, while not actually being productive 40 hours a week, and with it being neither organizational dysfunction (not to dismiss that as being true some places, but just to highlight it doesn't have to be), nor individual laziness (also not to dismiss that as a possibility, just that it doesn't have to be).
Re: Ask HN: Are most of us developers lying about how much work we do?
#250> Do people regularly run into coworkers like me during their career and simply ignore it because they find it too awkward to criticize them? Yes exactly this, especially at larger companies. I know a few of those developers, and they sit right near me... They find a way to make any task take forever... If it was a smaller company they would be called out, but at my [very, very] large company - its very hard to get f…
I have worked in startups and small companies and after a recent aquisition have worked in large companies for the first time in my career spanning 30 years. I am absolutely blown away at the environment and the behavior it breeds. I have lost most respect for the human race that continues to endure this as though it is acceptable. So many managers, so much busy work: remediating vulns that have no impact, CBTs, forced collaboration and sharing, layer upon layer of shared services, arbitrary policies, byzantine draconian change orders, and all the crap that the afore-mentioned cause.
Every problem results in a new arbitrary policy (authoritarian bureaucratic reflex) that gets layered on top.