|
Good Soldier Svejk posted:I had a (supposedly) senior dev on my team tell me today to just fix up his pull request because its "wasting too much [his] time" to figure it out. have you tried abuse in situations like these? i never run into these problems anymore but it's amazing what dropping a "are you loving stupid" while being otherwise professional can do.
|
#
?
Dec 18, 2018 01:39
|
|
|
|
| # ? May 23, 2024 11:29 |
|
|
New Yorp New Yorp posted:He has that attitude because it has worked for him in the past. In some organizations, it's easy to get other people to do your work for you and fly under the radar.
|
|
#
?
Dec 18, 2018 02:31
|
|
|
I definitely don't solely blame him because no one makes it that far in a career without being enabled by some spineless folks along the way but the question is how much I can dress him down without him going to his leadership (he's a sub-contractor)
|
|
#
?
Dec 18, 2018 03:09
|
|
|
Contractors aren't people
|
|
#
?
Dec 18, 2018 04:22
|
|
|
tortilla_chip posted:Contractors aren't people I'm one of only three permanent staff on my team of 25 contractors. The life of a government developer 
|
|
#
?
Dec 18, 2018 07:43
|
|
|
Good Soldier Svejk posted:I definitely don't solely blame him because no one makes it that far in a career without being enabled by some spineless folks along the way but the question is how much I can dress him down without him going to his leadership (he's a sub-contractor) He's been contacted to do a job, if he can't do it he needs to not be there and you need someone else who can do it. Your main contractor probably loves him because he can pad their bill and being a little more incremental revenue their way while not actually affecting the deadline or the rest of their revenue.
|
|
#
?
Dec 18, 2018 14:54
|
|
|
There are lots of good contractors out there going hungry. Sal here has been driven to do SharePoint integration in order to feed his family because he can’t find any work. The doctors tell me that soon it will be too late for him to recover. For only the price of one “gently caress off” letter, you can give those contractors - like Sal - the opportunity they need. Won’t you please turf an argumentative loser and pour that hourly rate into an actual human being today? This message brought to you by Code Reviewers Without Borders. Seat Safety Switch fucked around with this message at 22:51 on Dec 18, 2018 |
|
#
?
Dec 18, 2018 22:48
|
|
|
tortilla_chip posted:Contractors aren't people As a contractor, I find myself forced to agree. You don't need to play politics with him. If his leadership is dumb enough to complain just explain that if he can't do the job they should find someone who can.
|
|
#
?
Dec 18, 2018 23:24
|
|
|
I've found myself doing the interviewing for developer hires along with one other employee. I don't mind the work and I feel like we've gotten decent at spotting talent. For a while, we didn't bother with any coding questions as just talking with a candidate about previous work experience, spare time projects, and what they're excited about has worked well. Asking about the hardest bug they've ever fixed has become my favourite question. This was fine until one of the senior devs started pushing for some actual algorithm stuff to be added to the interview. We debated it for a while but I eventually acquiesced and threw in some short questions. Thus far, these haven't made much difference. Candidates who do well chatting about their previous experience do well on them. Those who don't, not so much. Then the senior dev asks to see the questions I added and they flip their lid and go on this rant about how insulting and "dogmatic" they are. At first I think he wants meatier stuff and is pissed I didn't really fulfil his request, but instead he starts insisting we remove them all together and that coding questions are a waste of time. This confused me for a while but then I realised he probably looked at the questions and didn't immediately know how to answer to them. He's always been a bit of a diva and he obviously thinks he's the smartest guy in the room, but this took me by surprise.
|
|
#
?
Dec 19, 2018 00:11
|
|
|
Welp, product has decided we need to do a rollout 2 days before everyone goes on vacation, and they're going to get their way despite the senior engineers telling them how stupid it is. Why am I even here.
|
|
#
?
Dec 19, 2018 00:18
|
|
|
Good Soldier Svejk posted:I definitely don't solely blame him because no one makes it that far in a career without being enabled by some spineless folks along the way but the question is how much I can dress him down without him going to his leadership (he's a sub-contractor) i've fired dozens of contractors for less egregious offenses than what you're putting up with.
|
|
#
?
Dec 19, 2018 00:26
|
|
|
steckles posted:I've found myself doing the interviewing for developer hires along with one other employee. I don't mind the work and I feel like we've gotten decent at spotting talent. For a while, we didn't bother with any coding questions as just talking with a candidate about previous work experience, spare time projects, and what they're excited about has worked well. Asking about the hardest bug they've ever fixed has become my favourite question. This owns.
|
|
#
?
Dec 19, 2018 00:29
|
|
|
Whole bunch of bikeshedding erupted on my team today that is honestly just frustrating as poo poo. Our QA opens up a screen and gets an error message. That's obviously not supposed to happen! A team had merged their changes into our branch a week or two ago, so he sends an email to them asking if they know what's going on. A dev on their team pipes up and says he's looking into it. 30 minutes later, he has a code fix and wants to know where to check it in. Our process dictates that each bug must be checked in against a ticket and PR'd into the appropriate branch, so there's a small amount of setup for that to happen. Our QA just goes "Well isn't that for your team to figure out? Your QA should know all the details about the bug." And then it explodes into these back and forth emails, and we now just got off a quick call about it, where we decided we're going to wait until the morning when the entire team is present and then we can actually discuss. We've literally wasted half a day, with more coming, trying to figure out the correct process on how to fix the issue, when the developer could have had it checked in, PR'd and reviewed, built & deployed, and the fix QA'd in an hour, tops. 
Macichne Leainig fucked around with this message at 00:38 on Dec 19, 2018 |
|
#
?
Dec 19, 2018 00:33
|
|
|
Che Delilas posted:Welp, product has decided we need to do a rollout 2 days before everyone goes on vacation, and they're going to get their way despite the senior engineers telling them how stupid it is. Why am I even here. Because our system is set up to force you to sell your labor at a huge discount in order to eat?
|
|
#
?
Dec 19, 2018 04:58
|
|
|
LLSix posted:As a contractor, I find myself forced to agree. You don't need to play politics with him. If his leadership is dumb enough to complain just explain that if he can't do the job they should find someone who can. It is what I like about contracting, stuff is crystal clear what is expected and how to act when expectations are not met. gently caress PDP's and annual less-than-cost-of-living raises, I got a daily rate and if we no longer like each other, I got some place else. This is coming from socialist Europe, take it as such. To be honest, it sounds like a discussion you should have had a while ago already. Too bad everyone and their mother is involved. Good times: I work at a well known global brand on java microservices using AWS on a massive scale. So last week I updated my linkedin and now the stupid generic mails come in being very bland and not offering me anything I don't already have. Being comfortable here, I read the mail to my manager, who not only told me he gets dozens of these a week as well but asked me that if I ever read something in a mail that offers me something I don't have, to let him know and they will pick it up, it might be something for this workplace as well. All in all, a good experience that I wanted to share.
|
|
#
?
Dec 19, 2018 11:00
|
|
|
Keetron posted:So last week I updated my linkedin and now the stupid generic mails come in being very bland and not offering me anything I don't already have.
|
|
#
?
Dec 19, 2018 18:46
|
|
|
Che Delilas posted:Welp, product has decided we need to do a rollout 2 days before everyone goes on vacation, and they're going to get their way despite the senior engineers telling them how stupid it is. Why am I even here. Feeling great about taking this week off to get an extended break right after we launched a bunch of stuff and offshore devs landed a major version language update to our applications in our test environment. Sprint is going to be mostly unplanned, extra super urgent work to stabilize and fix defects while supporting the in-flight offshore stuff before all the other engineers go away for over a week. If you can't stop the train, jumping out of the way is a good backup plan. Not that I really planned for this, but this week often ends up being sort of a particularly lovely one due to product usually trying to sneak stuff out before they would otherwise have to wait a couple of weeks. YanniRotten fucked around with this message at 01:44 on Dec 21, 2018 |
|
#
?
Dec 20, 2018 02:15
|
|
|
Che Delilas posted:Welp, product has decided we need to do a rollout 2 days before everyone goes on vacation, and they're going to get their way despite the senior engineers telling them how stupid it is. Why am I even here. I miss the job I worked at where they realized that team coverage is always terrible during the last six weeks of the year, so company-wide policy was that no releases are to happen between Thanksgiving and New Year. People used the time for learning and paying off tech debt, if they weren't just on vacation.
|
|
#
?
Dec 21, 2018 23:02
|
|
|
kitten smoothie posted:I miss the job I worked at where they realized that team coverage is always terrible during the last six weeks of the year, so company-wide policy was that no releases are to happen between Thanksgiving and New Year. People used the time for learning and paying off tech debt, if they weren't just on vacation. Whereas I just had to make the argument that this time of year is different, and no we should not take a full sprint worth of points for the two weeks covering Christmas and New Years.
|
|
#
?
Dec 21, 2018 23:16
|
|
|
Tell me about it. I just upgraded a project from Webpack 2.x to 4 and Gulp 3.x to 4 along with all the scripts and build tasks and it was a total nightmare. And this project was created using CRA only a bit over a year ago.
|
|
#
?
Dec 21, 2018 23:45
|
|
|
kitten smoothie posted:I miss the job I worked at where they realized that team coverage is always terrible during the last six weeks of the year, so company-wide policy was that no releases are to happen between Thanksgiving and New Year. People used the time for learning and paying off tech debt, if they weren't just on vacation. Our 'freeze' is not a flat ban, just periods where there are extra approval hops. It's just enough of a bar to make releases extra big since we dial down the frequency to avoid pestering VPs constantly, but essentially does nothing as a backstop when someone wants their new poo poo out there like now, whether or not it can actually be supported by a populated engineering team. Given that, I think I'd prefer no freeze or a very firm freeze (nothing goes out but important fixes, for a sane value of important).
|
|
#
?
Dec 22, 2018 00:39
|
|
|
My problem with our freeze is that everyone wants to release to production in early January but no one is around in December to prep for it. So it’s just mayhem once people come back.
|
|
#
?
Dec 22, 2018 16:42
|
|
|
The whole deploy freeze thing makes no sense to me as a long term solution. If your deploy process is that risky, the fix is to deploy more to systematically remove the risk from your system.
|
|
#
?
Dec 22, 2018 17:28
|
|
|
What if your application is a piece of poo poo and that's why it isn't automated
|
|
#
?
Dec 22, 2018 17:31
|
|
|
Find a new job or make a new years resolution to make it less of a piece of poo poo
|
|
#
?
Dec 22, 2018 17:35
|
|
|
Blinkz0rz posted:Find a new job or make a new years resolution to make it less of a piece of poo poo If you care, stop being helpless and fix it. If you don't care, find a job where you can care.
|
|
#
?
Dec 22, 2018 18:03
|
|
|
Vulture Culture posted:Seconded. This doesn't help if the person in charge of managing what you spend time on is a piece of poo poo. Does lead to the second point.
|
|
#
?
Dec 22, 2018 18:17
|
|
|
Yeah, if you care but you're not allowed to spend time on fixing things, GTFO ASAP.
|
|
#
?
Dec 22, 2018 18:18
|
|
|
drat I never felt so spoiled just for having multiple release environments and "freeze" just means nightly releases still get cut and deployed to a full testing system we just forgo our weekly prod deploy.
|
|
#
?
Dec 22, 2018 19:21
|
|
|
2nd Rate Poster posted:The whole deploy freeze thing makes no sense to me as a long term solution. If your deploy process is that risky, the fix is to deploy more to systematically remove the risk from your system. At all of the companies I've worked for, from startup to tech giant, we've had a code freeze. You are never going to remove the need for an on-call team to respond to pages no matter how safe your deploy process is. The code freeze is to make people not work over the holidays.
|
|
#
?
Dec 22, 2018 22:48
|
|
|
Pie Colony posted:At all of the companies I've worked for, from startup to tech giant, we've had a code freeze. You are never going to remove the need for an on-call team to respond to pages no matter how safe your deploy process is. The code freeze is to make people not work over the holidays. That is why you make your culture and pipeline robust enough that your devs ARE the team on-call for their individual services and if they want to deploy over Christmas they can but they are responding to the pages. Our UI team decided to not deploy over the holidays but I saw a couple deploys going to Prod on Friday in our system. Code freeze is a relic from waterfall that needs to die.
|
|
#
?
Dec 22, 2018 23:01
|
|
|
So many bright-eyed and optimistic non-Government developers here 
|
|
#
?
Dec 22, 2018 23:20
|
|
|
Virigoth posted:That is why you make your culture and pipeline robust enough that your devs ARE the team on-call for their individual services and if they want to deploy over Christmas they can but they are responding to the pages. Our UI team decided to not deploy over the holidays but I saw a couple deploys going to Prod on Friday in our system. Code freeze is a relic from waterfall that needs to die. 1) Devs don't usually determine when product features should be released. The freeze is as much for PMs and team leads as it is for devs 2) More things than "individual services" can break as a result of a deployment e: also, at most of these companies I've worked for, if it's truly a low risk change (e.g. fixing a typo on your page) you could still release it Pie Colony fucked around with this message at 23:55 on Dec 22, 2018 |
|
#
?
Dec 22, 2018 23:53
|
|
|
Pie Colony posted:1) Devs don't usually determine when product features should be released. The freeze is as much for PMs and team leads as it is for devs I agree the business should decide when features get turned on, but that is not a reason to stop shipping code. Tech debt and bug fixes are all valid things to work on that shouldn't need sign off from the business part of your company to release. As for #2, that's my whole point. If you can't reliably release things and know if your whole system will work, technical leadership has failed. And you should fight to get that addressed, as it is a fundamental process problem that slows the entire business down.
|
|
#
?
Dec 23, 2018 00:48
|
|
|
2nd Rate Poster posted:I agree the business should decide when features get turned on, but that is not a reason to stop shipping code. Tech debt and bug fixes are all valid things to work on that shouldn't need sign off from the business part of your company to release. Why would you ever work on bug fixes? Your perfect, infallible test automation and CI/CD quality gates should have caught them all before they ever got to prod. All software has bugs, and there's always some level of risk to a release. Good testing dramatically lowers the risk that you'll release a bug; with good tests, you can be reasonably certain that the whole system will work. Having good human coverage tends to lower the risk of a bug turning into a high-impact problem: issues can be resolved or worked around faster with multiple people to investigate what's going on in and fix a complex system. A good release management strategy will take the whole system - including human factors - into account.
|
|
#
?
Dec 23, 2018 03:03
|
|
|
2nd Rate Poster posted:. Thank god you've never made a mistake in your life
|
|
#
?
Dec 23, 2018 06:17
|
|
|
That's not what I'm saying at all. The whole point is to embrace mistakes, you'll gently caress up faster and implement better fixes the more often you bang your head against the problem. In my experience the big gently caress ups happen but the more you lean into the gently caress ups the less they appear. Until you hit some point where you have ironed out the big gently caress ups and are confident in getting rid of some of the guard rails. But yeah all the specifics change and may vary in your specific situation, but I just assumed that kind of goes without saying? 2nd Rate Poster fucked around with this message at 07:15 on Dec 23, 2018 |
|
#
?
Dec 23, 2018 07:07
|
|
|
I'm not sure there is a process that can fix most of the tech department being on vacation for the better part of a month this time of year.
|
|
#
?
Dec 23, 2018 09:21
|
|
|
No vacations, duh.
|
|
#
?
Dec 23, 2018 09:35
|
|
|
|
| # ? May 23, 2024 11:29 |
|
|
We're lucky if our customers update our product once a year.
|
|
#
?
Dec 23, 2018 15:18
|
|
