4 ms·

Juniors fall into this pitfall so quick. Our newest hire actually set boundaries early on and I was pleasantly surprised

by ramon156 10mo ago

nottorp 10mo ago
So it's the kind of work place where you have to set boundaries? :)
- fifilura 10mo ago
  What workplace is not?
- ManuelKiessling 10mo ago
  You need to set your bounds in every single workplace, because no one workplace can set the right boundaries for everyone.
- y-curious 10mo ago
  “Set your own boundaries, or someone else will do it for you” Turtles all the way down
  - ramon156 10mo ago
    I think this mostly speaks about setting boundaries with your higher-up, which is revolved around you. So, I guess it would be "Turtles all the way up"
- ramon156 10mo ago
  We work in different timezones so it's a mess. Either people give up their morning or they give up their evening time. I'm at the bottom of the chain here and have no authority to change this. Given that I'm being let go soon there's not much reason for them to care about my mental state either. But from the time I've been here, yes, you need to set boundaries or they'll do it for you. It seems like most PMs are used to talking to robots, because that's how they talk to us lately.
madduci 10mo ago
I hope they were work-life balance boundaries
georgeburdell 10mo ago
Disagree. This kind of comment is furtively pulling up the ladder behind you. Do as I say not as I do. Junior is the time to learn as much as possible and take risky bets (and suffer accordingly). When I was in a junior in a factory, the night shift knew me well. Nowadays, I've pared it back to 50 or so hours per week, because I now have a family, which is fine but it came at the cost of basically zero time to learn or do things other than what my manager asks.
- kamaal 10mo ago
  This is a correct view point to have. As you get to the downswing of your career, you should have already worked and made enough mistakes to have most of your experience. You must cruise on that experience when you are older. When you are old, that is not the time to work and make mistakes. That is, most of the heavy work must be done as early as you can. Eat that frog.
  - nasmorn 10mo ago
    I agree. When new programmers come from uni they sometimes barely did any programming. So at some time in their life they got to actually put in the time and learn how to be a competent developer. It is obviously great if you can do it on somebody else dime in a 9 to 5 but if you can’t get that you should just put in the time and learn. In the end you can at best get paid for the value you can create and if you are incompetent that is not going to be a lot
- BeetleB 10mo ago
  > Junior is the time to learn as much as possible and take risky bets (and suffer accordingly). When I was in a junior in a factory, the night shift knew me well. That would require a whole, separate article. Many (most?) juniors grinding like that in a major company will work hard to get nowhere. Speaking from experience. Yes, I learned some lessons: 1. Get a different job. Deadend jobs definitely exist, and are quite common. 2. Ignore senior folks who say "You're whining. It's crappy everywhere. Just learn to take it." Number 2 has been wrong every single time someone said it. > Nowadays, I've pared it back to 50 or so hours per week, because I now have a family, This is not the endorsement you think it is. I've done quite well by insisting on 40 hour weeks. I'm going to assume you're doing much better than I am, because otherwise it seems like a life wasted. Don't get me wrong. If you want to go much farther than I have, you likely will have to grind and work hard and smart and be lucky. But I assure you - most of the people I know who worked hard are not in a better position than I am (or if they are, the difference is incremental).

Juniors fall into this pitfall so quick. Our newest hire actually set boundaries early on and I was pleasantly surprised

nottorp 10mo ago

So it's the kind of work place where you have to set boundaries? :)

fifilura 10mo ago
What workplace is not?
ManuelKiessling 10mo ago
You need to set your bounds in every single workplace, because no one workplace can set the right boundaries for everyone.
y-curious 10mo ago
“Set your own boundaries, or someone else will do it for you” Turtles all the way down
- ramon156 10mo ago
  I think this mostly speaks about setting boundaries with your higher-up, which is revolved around you. So, I guess it would be "Turtles all the way up"
ramon156 10mo ago
We work in different timezones so it's a mess. Either people give up their morning or they give up their evening time. I'm at the bottom of the chain here and have no authority to change this. Given that I'm being let go soon there's not much reason for them to care about my mental state either. But from the time I've been here, yes, you need to set boundaries or they'll do it for you. It seems like most PMs are used to talking to robots, because that's how they talk to us lately.

madduci 10mo ago

I hope they were work-life balance boundaries

georgeburdell 10mo ago

Disagree. This kind of comment is furtively pulling up the ladder behind you. Do as I say not as I do. Junior is the time to learn as much as possible and take risky bets (and suffer accordingly). When I was in a junior in a factory, the night shift knew me well. Nowadays, I've pared it back to 50 or so hours per week, because I now have a family, which is fine but it came at the cost of basically zero time to learn or do things other than what my manager asks.

kamaal 10mo ago
This is a correct view point to have. As you get to the downswing of your career, you should have already worked and made enough mistakes to have most of your experience. You must cruise on that experience when you are older. When you are old, that is not the time to work and make mistakes. That is, most of the heavy work must be done as early as you can. Eat that frog.
- nasmorn 10mo ago
  I agree. When new programmers come from uni they sometimes barely did any programming. So at some time in their life they got to actually put in the time and learn how to be a competent developer. It is obviously great if you can do it on somebody else dime in a 9 to 5 but if you can’t get that you should just put in the time and learn. In the end you can at best get paid for the value you can create and if you are incompetent that is not going to be a lot
BeetleB 10mo ago
> Junior is the time to learn as much as possible and take risky bets (and suffer accordingly). When I was in a junior in a factory, the night shift knew me well. That would require a whole, separate article. Many (most?) juniors grinding like that in a major company will work hard to get nowhere. Speaking from experience. Yes, I learned some lessons: 1. Get a different job. Deadend jobs definitely exist, and are quite common. 2. Ignore senior folks who say "You're whining. It's crappy everywhere. Just learn to take it." Number 2 has been wrong every single time someone said it. > Nowadays, I've pared it back to 50 or so hours per week, because I now have a family, This is not the endorsement you think it is. I've done quite well by insisting on 40 hour weeks. I'm going to assume you're doing much better than I am, because otherwise it seems like a life wasted. Don't get me wrong. If you want to go much farther than I have, you likely will have to grind and work hard and smart and be lucky. But I assure you - most of the people I know who worked hard are not in a better position than I am (or if they are, the difference is incremental).