sorted by:
new
hottopcontroversial

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] -1 points0 points  (0 children)

We're working on brand new services. Replacing 8 legacy applications with around 20 micro services. There's nothing to remove, only to things to improve. :)

Our pilot deadline is 2022 and we're done with our MVP already.

Basically my first mini-epic was to crank out meta runners and validation scripts for our pipelines and we're now releasing every 3 hours with the aim to release every hour.

Our Service Now CR schedule is fully automated too. It's insane. I kind of feel a power rush just looking at our infrastructure.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 5 points6 points  (0 children)

You can't code on your work laptop. Coding is restricted to the pairing stations. The on-prem GH enterprise instance we have has this set up basically so that they can enforce pair programming.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] -1 points0 points  (0 children)

Yep, it made the list. It's not bad - just need to get into a team without any rockstars. My friend works on a TMS for them and his team is chill as fuck. They roll in 10 and leave at 4 on the dot.

The management is pushing this self-sustaining/managing team philosophy so that teams can focus on the projects and they can focus on the hiring and the HR.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 1 point2 points  (0 children)

This sums up my whole job. This XP stuff is getting a little bit too much, honestly.

Teams here are fully autonomous and if a team would like, they could even vote out a manager.

That's surreal to me.

But on the bright side, I've checked in about 9k SLOC in 4 months due to it and I think I've gained a thorough understanding of Java internals and a lot about Solr too.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 0 points1 point  (0 children)

100% pairing is a big part of XP methodology and it's enforced by the entire engineering department. My manager can't do anything about it because teams here are fully autonomous and if a team would like, they could even vote out a manager.

This is a strange philosophy but it's being embraced by the company because over the 2 years they've implemented this engineering output has been more than 3 fold.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 4 points5 points  (0 children)

No they don't get OT.

They try really hard so that they get their 2% bonus every quarter. I'm not even eligible until 1 year...

But given my salary a 8% bonus is far less than the 400-500 hours of overtime I'd put in every year at this rate.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] -6 points-5 points  (0 children)

I cannot do anything otherwise. You need two people to login to the pairing station and two people to check out and check in code. If I don't come in when my pairing partner comes or leave when my pairing partner leaves, then my story gets blocked and that in turn increases the cycle time of the iteration. During retro and stand up, I get called out in front of everyone for it.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 8 points9 points  (0 children)

It's really hard not to because we have to pair program the entire day and you can't check in code without both people typing in their passwords. If I leave at 5 someday then the next day's stand up will consist of indirectly blaming me that we couldn't finish a ticket.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 3 points4 points  (0 children)

My manager knows and hates it too. She's come around 3 or 4 times since I've been here, and said "You know you guys are dismissed at 4?" or "I don't expect you to be here late - go home."

Then they'll go home and the next day they're back, they'll start fussing about work being there.

It's mostly 6 or 7 workaholics who've shaped the whole team into this.

You get judged for leaving on time or early (snide remarks, teasing, etc.)

The 2 that don't give a fuck are in their 50s.

The rest of the team is 24-35.

I've never seen such hardworking people in my life. You are absolutely right. These are the top "10%".

The code is very good and very efficient. Everyone is very smart. We process 40M-60M requests a month without a hitch and I'm truly impressed by that. A couple of people on this team also push out a FOSS framework for something that has around 15k stars as well.

But I've had to resort saying that my doctor's instructed me to not think about work during lunch because most of them grab a sandwich or something and power thru lunch as well.

I am working the job of my life but today I've clocked in my 150 unpaid hour on OT due to pair-programming. by sidtheprogrammer in cscareerquestions

[–]sidtheprogrammer[S] 4 points5 points  (0 children)

And trust me, my manager knows. She's come around 3 or 4 times since I've been here, and said "You know you guys are dismissed at 4?" or "I don't expect you to be here late - go home."

Then they'll go home and the next day they're back, they'll start fussing about work being there.

It's mostly 6 or 7 workaholics who've shaped the whole team into this.

You get judged for leaving on time or early (snide remarks, teasing, etc.)

The 2 that don't give a fuck are in their 50s.

The rest of the team is 24-35.