Engineer is Frustrated With Big Project and Short Timeline
retained text
**BACKGROUND**
Teams are migrating applications into a chosen application. The initiative started implementation recently. All leadership is committed.
My friend is migrating one such application; she's been the first to faceplant into "walls", encounter (*and solve*) all the integration problems, and share guides documenting her experience to help the initiative's other teams' engineers.
**THE GOOD**
Leadership was ***THRILLED***.
**THE BAD**
She was working well past her normal hours because she wanted to make herself and her team look good.
**THE UGLY**
There's **MANY** files touched. She made a PR that roughly copies and pastes application code, and a much smaller glue PR.
She would break the integration PR into smaller PRs, but leadership publicly announced accelerated, aggressive timelines.
Her PRs went through code review for the same amount of time that she spent writing the them. She received a mix of genuinely helpful feedback (*"this will break"*), less helpful but still good feedback ("*use our code's component rather than your code's now-redundant one*"), and a fair amount of feedback equating to "*I don't like how this is written"*.
She dutifully addressed every single comment. After addressing their comments, she asked for more reviews, hoping for approvals, but got more similar comments, though with less important catches and more non-critical nits.
Things also started being discussed which weren't critical to the migration/initiative, like removing redundant dependencies, or performing mass system refactors to make the newly introduced code mesh better with their framework.
She found several issues in their systems too, and had to track down the maintainers of each system and ensure they were informed - anything more would've been huge scope creep and delayed her deliverable. It cost her a lot of time and energy to persuade their engineers that their system had problems.
At a certain point she kept receiving new comments from engineers who previously hadn't been engaged, or who had been but decided to come back for another round. Every time she would address human feedback, she'd receive **much more** feedback from automated AI reviews, especially considering that it'd take a few rounds of back-and-forth before the AI reviewers stopped finding new and "newer" issues with code she pushed to address their initial concerns. People would continue to comment on things that barely mattered, or hint at upgrading designs/systems (massive refactors).
And it all got frustrating. She delivered a lauded demo. Time doubled and she was being dragged through code review. It felt like her face was getting dragged through glass every time she pushed up code addressing a round of PR review feedback. She remarked to herself that she was sure the engineers weren't being petty, but if they were, this is what it would've felt like. She also thought the phrasing on a comment or two was written flippantly or dismissively.
It boiled to a head. A different engineer asked for a review of similar work. An engineer ***much****^((much))* more senior dismissed her rudely, saying it was too much to review.
When my friend read the comment, she exploded. She blasted them for not getting on board with the initiative and not being helpful *at all* throughout *any* of the process.
**THE AFTERMATH**
She deleted the comment. She thinks nobody read it. She was surprised to discover that other engineers were also frustrated. She said she'd seen some public arguments in her time, and what she wrote was with similar spice.
**TWO DAYS LATER**
She is mostly cooled off. She had a great weekend; it really took her mind off things. Now she just don't know what to do. She's being told to slam these huge PRs through this other team's throat like a scene from *blacked\[.\]com*.
She says she can sympathize with the other team; PRs this big are bad. It's got her second guessing herself. How can anyone review a very large PR? She doesn't think it makes sense to tell another team "*please code review nearly our entire codebase, which you've never seen before, because we're putting it into yours*".
This is testing her limits. She has never dealt with a code review this grueling. The pressure she put on herself to deliver this project ASAP in order to add a star to her C.V. is ***NOT*** helping. But there's actual real pressure; her team has a very short timeline, the other teams do too. An initiative leader related to her that they were frustrated because of how unsuccessful they were in getting other teams to start the initiative.
She isn't sure she can break the large integration PR into smaller PRs safely or easily. If she does, it'll make the process take longer too. She thinks she needs to get advice from the other engineers on this initiative.
What should she do next? Leadership wants it fast, but the receiving team wants to review the changes thoroughly. Should she adjust the timeline, try to restructure the PRs, or escalate the conflicting expectations?document fetched 2026-11-09 00:24 · canonical https://reddit.com/r/ExperiencedDevs/comments/1xr5qcs/engineer_is_frustrated_with_big_project_and_short