71–80 of 140 posts
Earlier quoted context omitted.
Just curious, in which country is 36hours/week standard? Or is it just your company?
Here in UK 37.5h is standard. 8 hour days with mandatory 30 minutes for lunch.
Spending 9 hours at work seems awful even if your lunch break is 60 min instead of 30.
I know it's not a popular idea, but here it goes anyway: senior software engineers, please say NO to being on call. It just puts some much pressure on engineers (like me) who don't want to be on call in exchange of more money: managers then think of you as someone who is not very commited to the company, bla bla bla... I'm commited to the company I work at any given time, from 9am to 5pm. That's all the time a compan…
Bugs that get you woken up in the middle of the night are fixed in no time. Documentation that is lacking, or spaghetti code, both preventing you from quickly fixing an issue instead of spending hours on it? Fixed the next day.
If the stakes of writing bad code are low, code quality will suffer. No better fix for those low stakes than being on call.
Earlier quoted context omitted.
In the UK I'm 9am to 5pm, however my contract allows for unpaid overtime. Usually management are pretty good with this though, and give some unofficial time off in lieu if I have to work OT.
> my contract allows for unpaid overtime Unless i was in serious financial trouble, or in a learning situation, i would never accept a contract that "allows for unpaid overtime". Most of the companies i know don't allow for "paid free time", so why should i give away my time for free to increase profits for the company ? The exception to this is of course "job salary", but i never accept those either unless i have a…
At least in the UK the law specifically forbids working more than 48 hours a week, so it's pretty common to see contracts where you opt out of this regulation. Not because the company even intends to make you work overtime, but because if you happened to work more, even entirely out of your own free will, you could still sue the company for working more than 48 hours in a week. So it's a very common thing to add in contracts here.
I know it's not a popular idea, but here it goes anyway: senior software engineers, please say NO to being on call. It just puts some much pressure on engineers (like me) who don't want to be on call in exchange of more money: managers then think of you as someone who is not very commited to the company, bla bla bla... I'm commited to the company I work at any given time, from 9am to 5pm. That's all the time a compan…
In my opinion, it’s almost mandatory for a well functioning software development environment to have developers on call (next to ops people). Bugs that get you woken up in the middle of the night are fixed in no time. Documentation that is lacking, or spaghetti code, both preventing you from quickly fixing an issue instead of spending hours on it? Fixed the next day. If the stakes of writing bad code are low, code qu…
I prefer a company with a strong tech culture: code review, thinkg long-term (marathons instead of sprints) and design systems with architecture-first on mind (instead of feature-first), automated testing, QA people, don't deploy on Fridays...
Earlier quoted context omitted.
Just curious, in which country is 36hours/week standard? Or is it just your company?
I think most of Europe has a 37 hour/week work schedule, and because "we're better" we have 36 hour/week. At least some of mainland Europe: Germany, France, Scandinavia, and IIRC the UK.
Earlier quoted context omitted.
In what hellish sort of company is 9AM "late"?
I sometimes wonder where the hell most HNers work where 9am is not considered late start. At a warehouse I worked at the shift was 6am to 2pm. And it was great that way as you avoided most of the summer heat. The software company where I work now, 8am is standard, that way you're nicely done at 4pm and have the entire evening to yourself. My wife is also a programmer and usually starts at 7:30am because that's their…
I know it's not a popular idea, but here it goes anyway: senior software engineers, please say NO to being on call. It just puts some much pressure on engineers (like me) who don't want to be on call in exchange of more money: managers then think of you as someone who is not very commited to the company, bla bla bla... I'm commited to the company I work at any given time, from 9am to 5pm. That's all the time a compan…
I know it's not a popular idea, but here it goes anyway: senior software engineers, please say NO to being on call. It just puts some much pressure on engineers (like me) who don't want to be on call in exchange of more money: managers then think of you as someone who is not very commited to the company, bla bla bla... I'm commited to the company I work at any given time, from 9am to 5pm. That's all the time a compan…
In my opinion, it’s almost mandatory for a well functioning software development environment to have developers on call (next to ops people). Bugs that get you woken up in the middle of the night are fixed in no time. Documentation that is lacking, or spaghetti code, both preventing you from quickly fixing an issue instead of spending hours on it? Fixed the next day. If the stakes of writing bad code are low, code qu…
90% of developers don't work in these industries or on these types of projects. Hell, I work in healthcare, for a private company, and there is zero reason for any of us to be on call. Patient quality doesn't suffer one iota if our software is down, which it rarely is.
It really sounds like you're advocating that developers be on call to "fix" the "problem" that there's no reason for them to be on call?
Earlier quoted context omitted.
In my opinion, it’s almost mandatory for a well functioning software development environment to have developers on call (next to ops people). Bugs that get you woken up in the middle of the night are fixed in no time. Documentation that is lacking, or spaghetti code, both preventing you from quickly fixing an issue instead of spending hours on it? Fixed the next day. If the stakes of writing bad code are low, code qu…
> No better fix for those low stakes than being on call. I prefer a company with a strong tech culture: code review, thinkg long-term (marathons instead of sprints) and design systems with architecture-first on mind (instead of feature-first), automated testing, QA people, don't deploy on Fridays...
Earlier quoted context omitted.
One could argue the qualities of a soldier or officer (individuals) transcend their organisational context (groups) and time. In other words: politics, technology or best practices change, not the responsabilities. The ability (necessity, even) to adapt to that fact defines a fit-for-service soldier/officer. So, I contend you find remarkable soldiers even in terrible groups, and that they (individuals) should not be…
> So, I contend you find remarkable soldiers even in terrible groups, and that they (individuals) should not be judged on their group but on their own qualities of service. So, we should praise ISIS fighters? I am intentionally picking up example of extreme, but very real organization. Same question can be asked about SS members. They knew what they joined. Does them doing good job in that organization is really prai…
You're distorting it. I was trying to point out that, they have to deform themselves to somewhat non-human states.
It's not valid only for servicemen. Firefighters are same. Police are same. Long haul truckers, cargo ship crew are same.
I think everybody making sacrifices for doing what they find worthy are eligible for some respect. They accept to deform themselves to do something they find value in.
Do not add ethnicity, politics, geography, race into this. It's about being human, and other parts are neither part of my comment nor has place in this specific thread.