|
brand engager posted:Are estimates supposed to be the entire time spent including time due to other people reviewing the code and QA testing? It's kinda hard to estimate the parts that I'm not going to be doing You do a "dev work" estimate and then you add an "organizational capacity [to allow for that dev work]" estimate, which is always bigger because of exactly that stuff you said.
|
#
¿
Aug 10, 2022 20:09
|
|
|
|
| # ¿ Apr 27, 2024 20:26 |
|
|
Why can't your team deliver, Charlie Brown?
|
|
#
¿
Aug 24, 2022 22:42
|
|
|
Is there anything more fun than asking a team to do something that only they have the power to do, listening to them ask you to make a ticket, watching that ticket go 1 month out of 2-week SLA despite reminding them weekly about it, only for them to say it's out of their scope, re-assign it to yet another team, listen to them say we must now wait for their SLA, and then assign it to a person on their team who's on vacation this week¿ Also the other team's SLA is 3 weeks. Sometimes I feel like I'm surrounded by scam artists.
|
|
#
¿
Sep 21, 2022 16:21
|
|
|
Great post + av combo
|
|
#
¿
Sep 21, 2022 16:33
|
|
|
prom candy posted:Anyone know of a good generic data dashboard service that I can send whatever events or other data I want to? For example I want to write code like SignalFX is cool and good https://dev.splunk.com/observability/reference/api/ingest_data/latest
|
|
#
¿
Sep 22, 2022 14:15
|
|
|
The buzz word right now is https://en.wikipedia.org/wiki/Scrumban afaik
|
|
#
¿
Oct 3, 2022 19:24
|
|
|
Love Stole the Day posted:Is there anything more fun than asking a team to do something that only they have the power to do, listening to them ask you to make a ticket, watching that ticket go 1 month out of 2-week SLA despite reminding them weekly about it, only for them to say it's out of their scope, re-assign it to yet another team, listen to them say we must now wait for their SLA, and then assign it to a person on their team who's on vacation this week¿ Also the other team's SLA is 3 weeks. Update: Eng Director escalated not just to their VP but to the SVP above them and also an adjacent VP... and 10 minutes later not only does the original team start responding to us, but they: conveniently forgot that punted the ticket after 3 weeks of silence, suddenly want to own the task, and immediately schedule a meeting to discuss it with us! Clearly I have a lot to learn about navigating bureaucracies.
|
|
#
¿
Oct 4, 2022 18:10
|
|
|
brand engager posted:Anyone have a good template for doing a "post-mortem" on a issue/ticket? Make a Confluence article timeline of everything that happened, and then highlight stuff to add your commentary on things. Do a 1 hr meeting where everybody reads the article together for the first 10-20 minutes, adding their own comments on stuff as they go, and keep notes on the stuff everyone agrees about. After the meeting, copy-paste those notes at the top of the article in a new section and call it "Takeaways" or "Outcomes" or "Learnings" or something like that.
|
|
#
¿
Oct 5, 2022 15:03
|
|
|
This would be a great April Fool's post in QCS: all moderator and admin actions are now machine learning-based and irreversible
|
|
#
¿
Nov 4, 2022 19:16
|
|
|
Quote of the day:quote:We did all the work, but nobody knew what the requirements were.
|
|
#
¿
Nov 10, 2022 21:15
|
|
|
Nybble posted:got anxiety from reading this thread Each of these bullet points is a great writing prompt for a tech blog, and great "case study" interview question prompts
|
|
#
¿
Nov 19, 2022 00:37
|
|
|
Harriet Carker posted:At a first glance, the best comment you could post is “where are the unit tests?” This is the best way to say it imo. Argue about the unit test cases it needs to cover. Best case scenario, the person's team had already discussed it or wrote about the important test cases in the Jira ticket or whatever.
|
|
#
¿
Dec 13, 2022 00:41
|
|
|
Hey thanks for agreeing to help me with the coding work for this project. I just finished the HLD and LLD. Just let me know when it's done thanks!
|
|
#
¿
Dec 17, 2022 16:26
|
|
|
Never inner source for another team. Ever.
|
|
#
¿
Jan 10, 2023 21:55
|
|
|
New Yorp New Yorp posted:as if it's impossible to be working on multiple objectives simultaneously. Love Stole the Day fucked around with this message at 20:43 on Jan 11, 2023 |
|
#
¿
Jan 11, 2023 20:21
|
|
|
Vulture Culture posted:In truth, 95% of game dev is managing piles of extremely burnt out people, where you want them to have enough camaraderie that they stop literally abusing each other, but not so much that they all quit at the same time or unionize. Out of the engineering team, there are four people who know everything about the engine but never talk to each other, and dozens or hundreds of other people who are constantly in meetings but still work with little or no intentionality at all Please stop doxxing me
|
|
#
¿
Jan 11, 2023 21:18
|
|
|
You gotta document it and remind the managers about it every time you update it, so that they remember what to discuss in their meetings with the other teams' managers. Make an article with a table that has these columns: created (date), updated (date), blocked by (team), severity (low or high), what you think should happen to mitigate the risk, and finally a description of the risk. Delete the row (or gray out its text and move it to the bottom) whenever an issue is resolved. That way, next time you're in this situation, you can say that managers knew the risks from the start. Look at all the unresolved stuff in this article and your suggested mitigation steps that everyone ignored!
|
|
#
¿
Jan 15, 2023 22:29
|
|
|
Rocko Bonaparte posted:The one that's gotten me recently is just claiming they need "more information" until they're just a human shell window being told each key to press for everything. We own this domain and all of its components, so only we can decide and approve the solution design for your use case. ... As for implementing the design we just approved, though, we will use the inner sourcing model for that because we don't have capacity. Of course, only we can review and approve your code changes. Also by the way there is no documentation for the design we just approved. We only talked about it in some meetings, so you will also have to write that document as well. You can't start the coding until we approve it.
|
|
#
¿
Jan 17, 2023 16:50
|
|
|
Pollyanna posted:they found it too worrisome or dangerous to change our code in any non-minimal way. “Why is this change included”, “do we absolutely need this”, the codebase is too fragile to handle changes like these”, etc. (The obvious response is “then let’s add more tests and be more rigorous in its design” but as much as I’d like that, management has different priorities.)  Most recent example here is being told by the owners of a domain that using a design pattern to save hundreds of lines of code (edit: to support new use cases) and be more DRY is "adding contextual complexity to the project". Of course, none of these imaginary coding standards are documented anywhere at all but that won't stop them from trying to influence others with their opinions because that's what Staff levels are supposed to do. Love Stole the Day fucked around with this message at 16:27 on Jan 19, 2023 |
|
#
¿
Jan 19, 2023 16:24
|
|
|
Vulture Culture posted:to be able to draw a line in the sand at implementation time about what is and isn't your/your team's job in making those happen
|
|
#
¿
Mar 17, 2023 14:58
|
|
|
Vulture Culture posted:My unironic favorite thing about shared ownership is that sometimes people will really surprise you with what they're able to do. On one project alone, I watched a data scientist submit a feature to an AWS SDK to get something working in a low-lift way, and another data-centered software engineer with very little Linux domain experience investigate and fix an SSSD configuration embedded into a Kubernetes sidecar through several layers of config management glue. Hey thanks for your PR implementation of this feature but our team was not properly consulted, did not approve this design, your implementation breaks our component's undocumented design principles, and we're not even sure how you were able to get the component to run locally on your machine and execute its functional/integration/acceptance tests, since they all depend on secret magic system property string values which we don't ever share outside of our team. We don't have capacity to review your PR at this time, so please talk with our engineering manager to prioritize a consultation session so that we can align on a better path forward. We might be able to squeeze you in next year.
|
|
#
¿
Mar 17, 2023 20:45
|
|
|
Vulture Culture posted:I don't really understand what the play is that you're trying to make here by involving Company Y's offer. Are you trying to somehow convince recruiting at Company X that they made a mistake by passing on you? I think he's actually asking for advice about his X girlfriend but is disguising it to fit in with the thread theme
|
|
#
¿
Mar 26, 2023 14:37
|
|
|
Vulture Culture posted:If by "sleazy" you really meant "desperate and hopeless", then you're getting closer
|
|
#
¿
Mar 27, 2023 08:46
|
|
|
smackfu posted:Apparently one side effect of all the tech layoffs is that attrition is way down this year at our company. Like low single digits of people leaving. I'd imagine that that's more because of hiring freezes than because of layoffs
|
|
#
¿
May 11, 2023 13:01
|
|
|
Cat Machine posted:mention at your performance review that you'd like to know what you could do to get a payrise in future. Try and get your employer to agree to some measurable performance indicators and then use that as as your goal for the next 6 months/1 year.
|
|
#
¿
Jun 28, 2023 13:14
|
|
|
Bongo Bill posted:
|
|
#
¿
Jun 28, 2023 17:52
|
|
|
prom candy posted:A thing I heard was something along the lines of if you have a poo poo codebase and it's preventing you from iterating and adding new features and you don't rewrite, eventually a competitor will rewrite it themselves and steal your customers.
|
|
#
¿
Jun 28, 2023 20:56
|
|
|
Xarn posted:why the gently caress would you do that? Because in a Large Organization, the expectations of upstream/downstream teams will have many small adjustments as the overall Product feature is being developed, the managers want to save money on the development environment, decades of tech debt and painful Major Incidents prevent you from having any CICD at all, and deployment as a process takes an entire day because of knowledge silos even for the components that your team owns due to lack of documentation and knowledge transfer as people leave the company and go elsewhere.
|
|
#
¿
Jul 9, 2023 20:01
|
|
|
Jabor posted:Once you are feature-complete, you make another PR to flip the flag on in internal testing environments. Once it's been QA'd and approved for release, another PR flips it on everywhere.
|
|
#
¿
Jul 10, 2023 13:08
|
|
|
This is one of the things I've been interested in seeing with Golang and Rust: because they don't do classes, I see people using OOP patterns in there... but since classes and inheritance work so differently, it feels like a round peg in a square hole. I wonder what patterns will be evangelized as those things become more ubiquitous. Then again, we should separate concerns and organize things in a way other engineers can understand... and OOP patterns are what they understand, so it's not wrong, but culture changes faster than language specs.
|
|
#
¿
Jul 16, 2023 14:36
|
|
|
I made this argument to my team last year and they were like "yeah but... naaaaaahh". I failed to influence them.
|
|
#
¿
Jul 17, 2023 13:16
|
|
|
brand engager posted:How do you write unit tests without them? Or were you only meaning integration tests? Pretend your component has a Controller - Service - Delegate way of separating concerns. The Controller takes in the request DTO and returns the response DTO... and the Delegate actually talks to the remote downstream stuff you need.
|
|
#
¿
Jul 17, 2023 15:10
|
|
|
Instead of mocking literally every dependency of literally every class, you're mocking only the stuff that talks to external things... and so you're actually running the end-to-end code of the component itself, in the same way that it's actually used in reality. So, you're covering more lines with fewer tests, you're writing your unit tests in the almost the same way you write your integration tests, and you don't have to worry about fixing your broken unit tests every time you want to make a code change. And since you're spending less time writing and fixing tests, you're also getting stuff done faster.
|
|
#
¿
Jul 17, 2023 15:54
|
|
|
The Fool posted:definitely second this recommendation I got the replacement book by Tanya Reilly and it's really good. One really good recommendation from the book is that we all should create 3 maps of the organization we work in:
We use the treasure map to brainstorm ideas for new projects. We use the topographical map to make our timeline estimates for our design documents, since it will remind us which teams are slower to work with. We use the organizational map to figure out whose specific buy-in we need for our project proposals and on which teams specifically will we be dependent to deliver our projects.
|
|
#
¿
Nov 2, 2023 01:17
|
|
|
Steve French posted:I’ve never understood the idea of standups being for sharing blockers. If I’m blocked on something I’m sure as hell not waiting for a meeting to communicate that This is how the conversations typically go for me at $org: Me: Hey I'm blocked on this thing Boss: Wow that's a lot of words and I'm stuck in meetings all day so let's just talk about it at standup
|
|
#
¿
Nov 2, 2023 10:54
|
|
|
"Where is that documented?" is how we insult each other, in Large Organizations
|
|
#
¿
Nov 12, 2023 13:42
|
|
|
Macichne Leainig posted:Try to delete it, see that even though the service is unused, it's still load bearing, and then shelve it and not touch it for 10 years in my experience Hey I know this component is deprecated, but we have a new feature on the replacement platform, but the Product leadership decided that the legacy components must support it so can you deploy a build 2 Sprints from now to align with our deadlines for which you weren't involved in the timeline estimate meetings or do I have to escalate this up to your VP and make her think you're not a team player ?
|
|
#
¿
Dec 2, 2023 23:59
|
|
|
Every time you guys throw out these 250 numbers or whatever, I wish you could clarify whether it's base+bonus+(new_rsus/years_until_fully_vested), if it's just the straight up base, if it's based on the stock price when it was granted, or if it was based on the stock price when it last vested. Because if you ignore the stock price going down and don't bother annualizing the new grant's vesting period, you'd think I'm doing way better than I actually am.
|
|
#
¿
Dec 5, 2023 21:18
|
|
|
Hey guys I remember there was a conversation a few weeks ago about whether we should calling downstream to component X, because it's supposed to be deprecated soon and replaced by component Y, and I don't remember what the decision was. Oh wow, so we're going to talk to component X anyway? That's pretty weird, was that decision or conversation documented anywhere? ... hello?
|
|
#
¿
Dec 27, 2023 18:03
|
|
|
|
| # ¿ Apr 27, 2024 20:26 |
|
|
Manager: "can we get contractors to write our unit tests for us?" Teammate who the manager trusts most: "Yes" Everyone else: "wtf no lol" Teammate who the manager trusts most: "Please I am feeling so much guilt that it's becoming difficult to code with so many things flying around. Our contractors are good at it!"
|
|
#
¿
Jan 1, 2024 15:20
|
|