Timeline for Dealing with a large pull request
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2021 at 1:05 | comment | added | OutstandingBill | The problem may have been caused by things outside of the developer's control. For example, a manager might say "I want this big feature developed, but I don't want it to contaminate production code until X date" (real-world managers do that kind of thing all the time). In fact, you'd have to wonder what the manager was thinking if they're still paying a developer whose code isn't reaching production. In any case, I'd advise against playing the blame game because that just makes your organisation an unpleasant place to work. | |
| Jul 30, 2018 at 23:46 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 | added 39 characters in body |
| Apr 8, 2014 at 1:22 | history | answered | Michael Shaw | CC BY-SA 3.0 |