|
Yeah, I'm leaning toward just saying I won't be in the office during the last week of the year and waiting until my boss knows before I tell anybody else. It's just annoying that the next sprint technically starts today, with my boss out, so my announcement can't line up with it. I absolutely do want to give notice no later than tomorrow, because our insurance is in the middle of changing and I want to give HR plenty of time to not gently caress up whatever COBRA situation happens between now and whenever I become eligible at my new job (#SinglePayerNow).
|
#
?
Dec 7, 2017 17:51
|
|
|
|
| # ? May 10, 2024 05:47 |
|
|
Gounads posted:Don't tell them.
|
|
#
?
Dec 7, 2017 17:58
|
|
|
CPColin posted:Yeah, I'm leaning toward just saying I won't be in the office during the last week of the year and waiting until my boss knows before I tell anybody else. It's just annoying that the next sprint technically starts today, with my boss out, so my announcement can't line up with it. I absolutely do want to give notice no later than tomorrow, because our insurance is in the middle of changing and I want to give HR plenty of time to not gently caress up whatever COBRA situation happens between now and whenever I become eligible at my new job (#SinglePayerNow). Yea, say when you will about taxes and poo poo, but not having to worry about this kind of very essential crap when changing jobs is a nice thing to have.
|
|
#
?
Dec 7, 2017 17:59
|
|
|
A bug came up in sprint planning where logging in as one user and using another tab to log out and back in as a different user made the first tab look weird, because it still claimed the first user was logged in, but the asynchronous requests acted like the second user was logged in. Okay, pretty standard issue with single-page web apps, no biggie. Then one of the developers said, "Oh yeah, that's weird, because there's this bug I filed..." The bug he brought up was that you could access various admin pages, regardless of permissions, as long as you knew the URL. Because all the permission checks did was show and hide stuff in the UI. The controller didn't do any permission checks. This is the (new version of the) information hub that all the various Criminal Justice departments in  Edit: Obfuscated which county I was talking about, for security. CPColin fucked around with this message at 20:00 on Dec 7, 2017 |
|
#
?
Dec 7, 2017 19:38
|
|
|
Development process is predictably garbage at my new job. It turns out that we just recently moved to a “push-every-Thursday” process where we have to get all the new features and changes we decided on for the week out by then, with predictable results (i.e. bugs out the wazoo). This means that dev work is a weeklong scramble to get stuff done and speed is valued over correctness, which ironically slows us down. The morning before we push, someone puts together a spreadsheet with prioritized bugs and assigns everyone something in a process completely separate from our ticketing system. All deployments and code merging is manual (no PRs as far as I can tell), and bugfixing is done by everyone pushing their changes to the same branch at the same time. I’m being outspoken about how problematic and clunky the process is and I’m planning on taking my manager aside and explaining how this is slowing us down and making dev work more of a pain than it should be, but I don’t know how far I’ll get. Remote status and time zone issues aside, the organization seems to be in a “work harder, not smarter” mentality, so who knows what will happen. Wish me luck guys 
|
|
#
?
Dec 7, 2017 19:55
|
|
|
The opsec training I have to take every year is screaming at me to tell you to remove that last detail.
|
|
#
?
Dec 7, 2017 19:56
|
|
|
The current version everybody uses doesn't have the problem; it's just the new version on Dev that's stupid. But message received.
|
|
#
?
Dec 7, 2017 19:59
|
|
|
Pollyanna posted:All deployments and code merging is manual (no PRs as far as I can tell), and bugfixing is done by everyone pushing their changes to the same branch at the same time. AAAAAAAAAAHHHHHHHGGGGGG (loud screaming while clutching at eyes) I am in a more or less similar situation, where the three teams decided a few weeks back to use feature branches so that the builds could be green now and then. We got told the process but not how the tools (git and bitbucket) work so I took it upon myself to organise a small git knowledge session where I was planning to explain to a few freshers how and why git works, what the difference is between local and remote, how to push, pull and fetch and how to branch and merge and make PRs. Nothing more. Booked a room for 12, I thought that in a team of 22, that should be more than enough. Well, seems more than half of my team expects to learn something new that hour! At least one guy was honest and declined with "This is way to basic for me and they should terminate anyone who accepts your meeting request. Great initiative, really!" Keetron fucked around with this message at 20:38 on Dec 7, 2017 |
|
#
?
Dec 7, 2017 20:35
|
|
|
When a fixing a bug, when do you band aid and when do you burn everything down and start from scratch? Asking for a friend.
|
|
#
?
Dec 8, 2017 00:27
|
|
|
Ither posted:When a fixing a bug, when do you band aid and when do you burn everything down and start from scratch? The big problem with burning everything down is that a) The code you burn down becomes your problem until you switch jobs b) It's going to take a while, and it's almost certainly not what your boss/po asked you to do c) If your new thing doesn't turn out better, you'll piss everyone off. Good reasons to throw stuff out: 1. The old code is based off a technology your company is getting rid of 2. The performance really bad and it's not obvious why the task should take as long as it does 3. The code has never hit production and just sucks 4. The requirements of the product have radically changed and it's not worth inheriting the technical debt of the old project. Sometimes engineers will mysteriously hold on to stuff that's not worth saving. 5. There are lots of intermittent issues that are difficult to troubleshoot. 6. You spend days reading code in classes seemingly completely unrelated to the problem you're trying to solve, but actually is totally related for reasons. 7. There are no tests of any kind. Sometimes you'll get a project with no unit tests but an army of QA - don't junk a project like that, it'll be like going to the dentist. But a project with no tests whatsoever that also doesn't work and QA doesn't know about it is totally worth junking. 8. The majority of the code of the project is unrelated to the project domain. Like if your spreadsheet app has 300,000 lines of code reinventing the dropdown menu, something is hosed up.
|
|
#
?
Dec 8, 2017 01:55
|
|
|
Ither posted:When a fixing a bug, when do you band aid and when do you burn everything down and start from scratch? Blowing it up would've been a year of work.
|
|
#
?
Dec 8, 2017 02:42
|
|
|
Pollyanna posted:Development process is predictably garbage at my new job. ... honestly did you ask any questions in your interviews at all
|
|
#
?
Dec 8, 2017 04:25
|
|
|
vonnegutt posted:honestly did you ask any questions in your interviews at all
|
|
#
?
Dec 8, 2017 04:41
|
|
|
Ghost of Reagan Past posted:If the effort to blow it up is less than fixing the bug. I had a bug to deal with that was fragile and insane and it took me a month of work and [bold]I started to have nightmares about that code[/bold]. Did the code chase you around and try to kill you?
|
|
#
?
Dec 8, 2017 11:31
|
|
|
Ither posted:Did the code chase you around and try to kill you? I have SQL dreams sometimes 
|
|
#
?
Dec 8, 2017 13:20
|
|
|
Ither posted:Did the code chase you around and try to kill you?
|
|
#
?
Dec 8, 2017 14:04
|
|
|
Ither posted:Did the code chase you around and try to kill you? I had a dream that our dick HR person sent out an email giving my office away because I've been working from home sick most of this week.
|
|
#
?
Dec 8, 2017 14:08
|
|
|
Pollyanna posted:Development process is predictably garbage at my new job.
|
|
#
?
Dec 8, 2017 14:24
|
|
|
Pollyanna posted:I’m being outspoken about how problematic and clunky the process is and I’m planning on taking my manager aside and explaining how this is slowing us down and making dev work more of a pain than it should be, but I don’t know how far I’ll get. Remote status and time zone issues aside, the organization seems to be in a “work harder, not smarter” mentality, so who knows what will happen. Wish me luck guys I genuinely hope your place of work is the unicorn where someone will listen to you, you will be able to drive change, and people will be on board with updating processes. However, unicorns don't exist, so uh thanks for giving me some more questions to ask in my next interview 
|
|
#
?
Dec 8, 2017 14:44
|
|
|
Che Delilas posted:I have SQL dreams sometimes I've dreamt in X(A)ML before. It was about as bad as you'd think.
|
|
#
?
Dec 8, 2017 15:01
|
|
|
ChickenWing posted:I genuinely hope your place of work is the unicorn where someone will listen to you, you will be able to drive change, and people will be on board with updating processes. Don't forget to ask "Are deployments automated, or manual?". If the answer is "manual", expect to be told to deploy something yourself eventually, and expect that to be a lovely and frustrating process. Also, expect it to go wrong. It is up to you to determine how the answers to this question, among many others, influence your decision. 
|
|
#
?
Dec 8, 2017 15:37
|
|
|
Munkeymon posted:I've dreamt in X(A)ML before. It was about as bad as you'd think. All my XML dreams were nightmares.
|
|
#
?
Dec 8, 2017 17:45
|
|
|
Coworker, via IM: Hey, do you know where (ID) came from? Did you enter it? Me: Don't think so. Coworker: The highest ID on Production is (much lower ID). *Coworker comes over to ask the same questions in person* Me: Let me just come to your desk and see what you're looking at. *Coworker shows me a record that caused an exception. The "last updated by" field is very clearly not me.* Coworker: So when you test stuff like this, if the ID doesn't exist in the central database, it'll throw an exception. Me: *points at the "last updated by" field* It wasn't me. I haven't done any testing yet today. Let me look in the database for more info. (a few minutes pass) Coworker, via IM: *sends me the stack trace of the exception* Coworker, in person: So when you test stuff like this, make sure to insert the ID into the central database, so it doesn't throw an exception. Me: It wasn't me, but okay. Giving my two-week notice this afternoon. 
|
|
#
?
Dec 8, 2017 18:49
|
|
|
CPColin posted:Coworker, via IM: Hey, do you know where (ID) came from? Did you enter it? He also just changes your code if he can't make it work on the first attempt, which is of course some nutty behavior, and usually then requires you figure out what he's doing wrong.
|
|
#
?
Dec 8, 2017 19:09
|
|
|
I had a co-worker that would delete foreign key constraint from his dev databse when he had integrity exception pop up. God... that me us so mad, he was completely clueless as to why we were pissed.
|
|
#
?
Dec 8, 2017 19:19
|
|
|
Ghost of Reagan Past posted:He also just changes your code if he can't make it work on the first attempt, which is of course some nutty behavior, and usually then requires you figure out what he's doing wrong. Oh yeah, when I was looking at the code to see why it tried to send an invalid ID (answer: because the person typed it that way), I discovered that some of the tests were failing suddenly. Remember when the code wouldn't build because the server couldn't handle C# 6? Well that same coworker commented out the part of the code that was looking up credentials, because it was using the ?. operator. She told me yesterday morning that we didn't need a follow-up task to undo the few changes we made to try to work around the C# 6 problem. Guess she missed that one! (No, I don't know why the fall-back credential lookup is working on QA, but not when I run the unit tests. And I don't much care!)
|
|
#
?
Dec 8, 2017 19:29
|
|
|
Portland Sucks posted:I just looked this up and had no idea this exists which brought me to a larger question. I'd recommend looking over the C# version history. It details each new language feature as it was added and this allows you to go from 1.0 and see how the language has incrementally improved and zoom in on each specific thing to learn more.
|
|
#
?
Dec 8, 2017 19:41
|
|
|
CPColin posted:Remember when the code wouldn't build because the server couldn't handle C# 6? Why on earth isn't your build system running the same tooling? Should we move to the Coding Horror thread?
|
|
#
?
Dec 8, 2017 19:59
|
|
|
Pixelboy posted:Why on earth isn't your build system running the same tooling? We have one of those - on just one of our build boxes, the metrics inspector (not the compiler itself!) doesn't know C# 7. Since "uh just rerun it on a good box" is an effective workaround and nobody wants to spend time digging around on something this stupid it's just lingered for months now.
|
|
#
?
Dec 8, 2017 20:12
|
|
|
Pixelboy posted:Why on earth isn't your build system running the same tooling? The real horror is how much work one of my other coworkers had to do to get the right version of the compiler onto TFS! Edit: T-25 minutes until my weekly one-on-one. Currently getting antsy for no reason! CPColin fucked around with this message at 00:36 on Dec 9, 2017 |
|
#
?
Dec 8, 2017 20:18
|
|
|
CPColin posted:Edit: T-25 minutes until my weekly one-on-one. Currently getting antsy for no reason! When I quit my last job I tried to pull the old “meeting request with no specific agenda” on my boss and he ended up being free slightly earlier and saying hey want to meet now and I had to rush to print out my resignation in an incredibly unsubtle way. It owned and I hope you have fun
|
|
#
?
Dec 9, 2017 05:37
|
|
|
vonnegutt posted:honestly did you ask any questions in your interviews at all Seriously quote:How big are your teams?
|
|
#
?
Dec 9, 2017 12:52
|
|
|
Phobeste posted:This is a great feeling "Meeting request with no specific agenda", and even weekly one-on-ones, have always utterly terrified me.
|
|
#
?
Dec 9, 2017 13:49
|
|
|
No agenda meetings are awful. I usually skip and if they actually matter someone comes and finds me. I rather like weekly one-on-ones. It gives me a chance to ask questions about the company and product direction. It also gives me an opportunity to discuss pain points, blockers, inefficiencies, and improvements I'd like to make. Best of all, its the least stressful way to discuss what my supervisor would like to see to recommend me for a promotion or raise. Once I started doing that more often, my reviews became pro-forma with both sides knowing ahead of time how it was going to go. I do still get nervous before one-on-ones though, and probably always will.
|
|
#
?
Dec 9, 2017 15:19
|
|
|
Pollyanna posted:"Meeting request with no specific agenda", and even weekly one-on-ones, have always utterly terrified me.
|
|
#
?
Dec 9, 2017 15:25
|
|
|
Sagacity posted:Just curious: Did you not ask about how their process works when you were interviewing?
|
|
#
?
Dec 9, 2017 15:43
|
|
|
Vulture Culture posted:Any long-term performance problem that's a surprise to hear about is a symbol of an utterly inept, thoroughly incompetent, conflict-avoidant manager Exactly. At the start of every written review presentation I preface it with, “There is nothing in here that should come even remotely surprising, if it does than I’ve failed and the time we spend in weekly 1:1s have been wasted.”
|
|
#
?
Dec 9, 2017 16:09
|
|
|
I once received a negative review and asked why the concerns never came up before. Boss didn’t have an answer. Started a job search that night. 
|
|
#
?
Dec 9, 2017 16:16
|
|
|
Vulture Culture posted:Any long-term performance problem that's a surprise to hear about is a symbol of an utterly inept, thoroughly incompetent, conflict-avoidant manager Hughlander posted:Exactly. At the start of every written review presentation I preface it with, “There is nothing in here that should come even remotely surprising, if it does than I’ve failed and the time we spend in weekly 1:1s have been wasted.” Pretty much. I had a manager who didn't follow this very well and was liable to randomly drop bombs during 1:1s, usually when the 1:1 was preceded by the words "let's go take a walk". Since then, I've been suspicious of them. I really hated that guy.
|
|
#
?
Dec 9, 2017 16:48
|
|
|
|
| # ? May 10, 2024 05:47 |
|
|
Pollyanna posted:Meeting request with no specific agenda This is how I got fired back in January, but it's also how I got promoted last week. 
|
|
#
?
Dec 9, 2017 17:10
|
|
