|
CPColin posted:Thankfully, he backed off, once he realized how absurd his request was! To say nothing of how if his team needed to rely on head-starts in their PR's to get stuff in before the end of the sprint, maybe his team was over-committing! And then you woke up, right?
|
#
?
Sep 25, 2017 19:42
|
|
|
|
| # ? May 10, 2024 05:03 |
|
|
I messed up the construction of that last paragraph. He did not come to that last realization, because of course not.
|
|
#
?
Sep 25, 2017 19:55
|
|
|
CPColin posted:I messed up the construction of that last paragraph. He did not come to that last realization, because of course not. Oh good I was worried for a second that something had gone right
|
|
#
?
Sep 25, 2017 20:13
|
|
|
Pollyanna posted:He's now claiming that my solution does the opposite of what it actually does, so I don't think he's even investigated or tried to understand my solution. He clearly doesn't trust me to implement anything and I'm just going to chafe further under him. Do you have unit tests to prove it does what it does? I'm not trying to get after you; I'm assuming if you don't it's because of stupid policies outside of your control. I am just trying to figure out how much more flabbergasted I should be.
|
|
#
?
Sep 25, 2017 20:29
|
|
|
Rocko Bonaparte posted:Do you have unit tests to prove it does what it does? I'm not trying to get after you; I'm assuming if you don't it's because of stupid policies outside of your control. I am just trying to figure out how much more flabbergasted I should be. Yep, I've got unit tests.
|
|
#
?
Sep 25, 2017 20:37
|
|
|
Do it the wrong way while you actively job hunt.
|
|
#
?
Sep 25, 2017 20:58
|
|
|
I was gonna say just add some !! and hope he's too swamped with other crap to notice butVolmarias posted:Do it the wrong way while you actively job hunt.
|
|
#
?
Sep 25, 2017 21:02
|
|
|
I keep happening to be at the keyboard during various meetings, so my Product Owner has seen me move stuff around in the backlog, link tickets together, etc., in TFS. Today, she said, "Colin should be the PO! He's good at TFS!" I think she was joking, because I'd be pretty goddamn atrocious at it! I've been here a month and have no idea what anything's priority would be. I'm pretty sure she still has no idea what a PO is actually supposed to be doing.
|
|
#
?
Sep 26, 2017 00:45
|
|
|
CPColin posted:I keep happening to be at the keyboard during various meetings, so my Product Owner has seen me move stuff around in the backlog, link tickets together, etc., in TFS. Today, she said, "Colin should be the PO! He's good at TFS!" I think she was joking, because I'd be pretty goddamn atrocious at it! I've been here a month and have no idea what anything's priority would be. I'm pretty sure she still has no idea what a PO is actually supposed to be doing. You should be the scrum master too.
|
|
#
?
Sep 26, 2017 03:24
|
|
|
CPColin posted:[I] have no idea what anything's priority would be. Just like most other PO's.
|
|
#
?
Sep 26, 2017 07:18
|
|
|
Man, SOAP is the loving worst. That is all.
|
|
#
?
Sep 28, 2017 00:31
|
|
|
What do most teams here have for a scrum master? Is it just a random developer getting voluntold to do it? We have no PO and our scrum master is just a random guy who knows nothing about software and goes "welp, thanks for coming to standup today. Have a good one" and that's about it.
|
|
#
?
Sep 28, 2017 00:45
|
|
|
Ours is a developer who's primarily doing maintenance tasks and isn't on a Scrum team. He was certified already before we did the week of training. I took the test and got certified after the training, but nobody asked me if I wanted to do it. v vAt my last job, we had to share the one scrum master across four teams. She spent 1/5 of her time in sprint planning meetings. I don't know how she did it. She eventually told us we had the hang of it and ditched us when they added a fifth team. By the way, it wasn't until I went through the training at my current job that I learned my old company should have had a single backlog that everybody shared and a single person who was empowered to order the whole thing. That would have been a delightful disaster! CPColin fucked around with this message at 00:50 on Sep 28, 2017 |
|
#
?
Sep 28, 2017 00:47
|
|
|
My last job had full-time scrum masters, each split between two teams, much like POs there. At my current job the scrum master is a senior developer, and being senior he knows how to unblock problems.
|
|
#
?
Sep 28, 2017 00:52
|
|
|
My Rhythmic Crotch posted:What do most teams here have for a scrum master? Is it just a random developer getting voluntold to do it? We have a full time scrum master. She works with the product team and the product owners mostly. She also facilitates other meetings such as GV sprints that we do a few times a year and also is basically in charge of Jira. She has a few other responsibilities as well, but most of it is a big help in managing expectations and constantly keeps management away from us and throws a red flag if we start slipping towards waterfall-ish tendencies. She rocks at the job and it really let's us focus on actually defining and developing the product.
|
|
#
?
Sep 28, 2017 01:15
|
|
|
Okay, I see. When discussing this stuff, it's so tempting to say "yeah but our organizations are structured like <blah> so how how could we really make this work?" But looking back I think I can kind of identify times when I was acting like a PO, scrum master, or developer as the situation called for it. Those were the good, successful projects that got delivered quickly and mostly painlessly. The really bad, horrible projects, I was never able or allowed to get into a role that would really ensure things moved along.
|
|
#
?
Sep 28, 2017 02:35
|
|
|
My Rhythmic Crotch posted:What do most teams here have for a scrum master? Is it just a random developer getting voluntold to do it? Theoretically it's supposed to be a full-time dedicated scrum master, but unless your teams are big and complicated, odds are pretty good the company will just pick some rando developer to do it.
|
|
#
?
Sep 28, 2017 02:54
|
|
|
Main Paineframe posted:Theoretically it's supposed to be a full-time dedicated scrum master, but unless your teams are big and complicated, odds are pretty good the company will just pick some rando developer to do it. Really? I thought it was supposed to be a rando (and rotate periodically) because the scrum master's job is just to poke people like "hey did you set up a meeting with PM about that feature?" or "it's time for stand-up". Pretty sad if it's a full-time position. Just middle managers getting shittier pay.
|
|
#
?
Sep 28, 2017 03:15
|
|
|
A lot of consulting agencies I've known have had dedicated scrum masters, usually a junior project manager.
|
|
#
?
Sep 28, 2017 03:15
|
|
|
Just to make sure we're on the same page here, some people define "scrum master" to be "team leader" whereas others define it to be "the person who leads the five-minute standup meeting we have each morning". On my team, the team leader is a fixed role held by a senior developer, but responsibility for actually running the scrum rotates among team members each day.
|
|
#
?
Sep 28, 2017 12:36
|
|
|
Doom Mathematic posted:Just to make sure we're on the same page here, some people define "scrum master" to be "team leader" whereas others define it to be "the person who leads the five-minute standup meeting we have each morning". On my team, the team leader is a fixed role held by a senior developer, but responsibility for actually running the scrum rotates among team members each day. From my personal experience, the scrum master is neither a team leader nor the person who only leads the standups. He/she has a bigger role, essentially being the bridge between the development team and the rest of the people (qa, project management, client representatives, etc.). The main role is to ensure that the developers have everything they need to do their work: a prepared and prioritized backlog for the planning meeting, answers to any questions that may come up, lead and prepare the demo meetings, the pretty charts and reports for the execs, etc. Leading the standups is but one (and a minor one at that) of their roles. But yes, it does happen more often than not that the team lead takes on all those responsibilities. Or ... nobody does and everything is chaotic. A good scrum master can be the difference between a successful project and a failure.
|
|
#
?
Sep 28, 2017 16:12
|
|
|
I was assigned as the scrum master of our small team on top of regular dev duties. It worked well for a little... Unfortunately, the expectation from my colleague and from my boss didn't align. My teammates excepted me to help them solve all their blocking issues while my boss didn't see this as something I should be doing. It didn't work so great. I'm not taking on scrum master duties anymore. We still do standup every morning but there is no scrum master anymore. Everyone is responsible for their blocking issue and to unblock themselves. Good thing is it develop everyone's resourcefulness. We're a small company with a small (7) developer team.
|
|
#
?
Sep 28, 2017 18:19
|
|
|
Volguus posted:From my personal experience, the scrum master is neither a team leader nor the person who only leads the standups. He/she has a bigger role, essentially being the bridge between the development team and the rest of the people (qa, project management, client representatives, etc.). The main role is to ensure that the developers have everything they need to do their work: a prepared and prioritized backlog for the planning meeting, answers to any questions that may come up, lead and prepare the demo meetings, the pretty charts and reports for the execs, etc. Leading the standups is but one (and a minor one at that) of their roles. Uh, a lot of that stuff there is the product owner's job. I can't remember if technically a PO may also be SM, but I'm pretty sure it's not encouraged.
|
|
#
?
Sep 28, 2017 21:44
|
|
|
pigdog posted:Uh, a lot of that stuff there is the product owner's job. I can't remember if technically a PO may also be SM, but I'm pretty sure it's not encouraged. A more succinct way of putting it may be "I talk to the god damned PMs so the engineers don't have to! I have people skills! What the hell is wrong with you people?"
|
|
#
?
Sep 28, 2017 21:49
|
|
|
Skandranon posted:A more succinct way of putting it may be "I talk to the god damned PMs so the engineers don't have to! I have people skills! What the hell is wrong with you people?" Yes. Except when it has to do with the product that the team is developing.
|
|
#
?
Sep 28, 2017 21:53
|
|
|
pigdog posted:Uh, a lot of that stuff there is the product owner's job. I can't remember if technically a PO may also be SM, but I'm pretty sure it's not encouraged. Umm...no. The product owner is the client (or the client's representative). He's not the bridge to anything. He has the backlog, sure, but unless the scrum master will have meetings with him before planning, that backlog will be a complete mess by that time. And those meetings will, of course, not involve the developers. Now, you can come and say: in every company I've worked at the PO is the client and the PM and the CEO and the janitor and the IT guy. And yes, there are companies who do that but in ideal conditions those roles are filled by different people with completely different skills.
|
|
#
?
Sep 29, 2017 01:22
|
|
|
Dedicated scrum masters serve a purpose when teams aren't empowered, or when team leads are very poor at their job, or when there is no team lead. The rest of the time, distributing their salary among the devs would be the best outcome.
|
|
#
?
Sep 29, 2017 02:13
|
|
|
necrobobsledder posted:I forgot about this article by the Nginx folks with some detail on component refactoring. Normally when people talk about breaking apart a monolith it usually involves some talk about microservices, and they are not mutually exclusive at all. You can have a series of monoliths each acting as a "microservice" (relatively speaking). In fact, if you don't have all the good stuff needed, I recommend splitting out only one module to a service and pick something somewhat used and important. People tend to try to pull out something low-risk, learn the wrong lessons about running a new service (ie. oh gosh, that was easy, we don't need monitoring! derp) and continue to repeat mistakes of bad design. I got the green light from the VP to prototype this during the next sprint  It would never get approved if it was for something that already existed. We're understaffed so dealing with tech debt keeps getting pushed aside (though there is a massive piece of debt that is slotted for 2018 - finally). So instead, we're doing something completely new and basically is going to be the new "landing page" when someone logs in to our system. Is it ideal? Maybe/maybe not (but if we don't take advantage of the timing now, we won't get this chance again for a while). Even with it being new it is relatively safe. It's basically a 30,000ft view for our clients and it's read-only (minus setting a few filters) running off of indexed data in Solr. I would love to do this in Kotlin to match our API project, but that might be one thing too much for the time we have to turn this around. And also the response is already ready, so there's no real need to anything other than a single endpoint. My kickass sys admin is all in and is pushing to revamp our load balancers and to improve our monitoring capabilities (she's been through monolith -> containerization before), so I think we're in good hands. I kind of paved the way for this getting nginx reverse proxy server installed locally for everyone and the sys admin I'm working with on this is going to centralize the reverse proxy in the next couple of weeks so I laid a bit of ground work to make this possible. Really this is something that should have been done years ago, but there was never anyone pushing it. I still have to read the 12F link you included. That's for this weekend.
|
|
#
?
Sep 29, 2017 03:29
|
|
|
Volguus posted:Umm...no. The product owner is the client (or the client's representative). He's not the bridge to anything. He has the backlog, sure, but unless the scrum master will have meetings with him before planning, that backlog will be a complete mess by that time. And those meetings will, of course, not involve the developers. Although they are quite rare, competent product owners do exist. In my opinion the scrum master should lead the scrum team (that includes the PO) in continuously improving their own process. Part of that is the process of backlog refinement, so it may involve helping the PO sort out the backlog and making sure the right meetings take place.
|
|
#
?
Sep 29, 2017 06:24
|
|
|
Messyass posted:Although they are quite rare, competent product owners do exist. If you need a dedicated external person to unblock things for your team then you don't have everything you need in your team to deliver the product. That person could be providing real value and it's probably fine for them to be the SM as well but it's not a requirement of the SM role that they run around doing that stuff for you.
|
|
#
?
Oct 2, 2017 18:25
|
|
|
Kind of a crosspost from forza: I played Forza late last night and have been working on containerizing my company's applications. I had a dream I raced the Docker Whale through the Dubai tunnel only to find out I hadn't configured it correctly an dmy sys admin coworker was my crew chief. I just had a vacation and I already need another one.
|
|
#
?
Oct 4, 2017 03:27
|
|
|
geeves posted:Kind of a crosspost from forza: At this point you are already having the mental break so you might as well ride that wave, no need to spend PTO or your money to go somewhere else to do that...
|
|
#
?
Oct 4, 2017 03:52
|
|
|
Two days ago, I was looking at some of our C# code and noticed it was doing a bunch of database work by hand. So I read up on the Entity Framework and figured, "Hey, this could simplify stuff a bit." Scrolled to the bottom of the backlog and added an item that would cover the existing code with automated testing (yep), add new utility functions that use the Entity Framework, and file follow-ups to convert existing code to use the new utilities. Yesterday at 4:54, one of my coworkers emails me (as opposed to commenting in the ticket) to say we should talk about this plan before we "tear apart" the code, because other stuff in the codebase uses the same structure. Also, "I like that it's at the bottom of the list for now." Now I have to resist the urge to say of course it's at the bottom of the list, because that's where it belongs until the Product Owner moves it up, and of course we're going to talk about it, because we can't work on it until it's in a sprint and it can't be in a sprint until we talk about it! It's like, hi, I know I'm new here, but I have ten years of industry experience and I know how to handle a refactor project. I'm probably overreacting.
|
|
#
?
Oct 5, 2017 16:30
|
|
|
What is the business value of the refactor? Also: probably his design you eant to kill.
|
|
#
?
Oct 5, 2017 18:29
|
|
|
CPColin posted:So I read up on the Entity Framework and figured, "Hey, this could simplify stuff a bit." That will be quickly proven wrong. It's been a few years since I used it, but I really hate EF.
|
|
#
?
Oct 5, 2017 18:36
|
|
|
Keetron posted:What is the business value of the refactor? The value is that it might make a certain new developer consider sticking around for more than a year. And I have no idea if it's her design because the code was very obviously copied and pasted across several projects. I've seen the same couple of interfaces over and over, all of them with a comment in there saying something like, "This is part of the XYZ web service." and I have not seen the web service they're talking about. New Yorp New Yorp posted:That will be quickly proven wrong. It's been a few years since I used it, but I really hate EF. What did you find wrong with it? The stuff I was considering using it for was pretty straightforward code that was like, "select the one row that matches this ID," or, "select all the rows that match this ID." Speaking of which, those "select one row" and "select all rows" methods are pretty much exact copies of each other, except that the former loops through all the rows and sets the return variable to the current row, while the latter loops through all the rows and adds them to a list. Heaven forbid the former would call the latter and just return the first row. Or would just return the first row itself, instead of looping over all of them and returning the last row. Or would actually use a query that returns only one row. Whatever!
|
|
#
?
Oct 5, 2017 18:49
|
|
|
CPColin posted:What did you find wrong with it? The stuff I was considering using it for was pretty straightforward code that was like, "select the one row that matches this ID," or, "select all the rows that match this ID." It's great for very simple queries. It falls apart when it starts generating complex, hugely unoptimized queries and you have to spend hours scratching your head trying to figure out why it's generating awful garbage SQL.
|
|
#
?
Oct 5, 2017 19:03
|
|
|
I got promoted  My mini-project is going swimmingly professional life going good guys
|
|
#
?
Oct 5, 2017 19:35
|
|
|
ChickenWing posted:My mini-project is going swimmingly actually technically this is "went swimmingly" released it, QA picked it up really well, rolled out a second release with some requested features, currently doing support on that, QA picked that up less well because I didn't have any documentation and we didn't do a proper teaching session, still mostly going well and bug-free.
|
|
#
?
Oct 5, 2017 19:38
|
|
|
|
| # ? May 10, 2024 05:03 |
|
|
New Yorp New Yorp posted:It's great for very simple queries. It falls apart when it starts generating complex, hugely unoptimized queries and you have to spend hours scratching your head trying to figure out why it's generating awful garbage SQL. Cool, thanks. The stuff I was proposing is pretty simple. The code that's there now includes all kinds of stuff for performing inserts and updates, but nothing ever calls it. It led to me scratching my head for a bit, wondering what the code was doing, because of how much extra functionality was available, relative to what was actually necessary. Also, all the code does stuff like this: (new PersonFactory()).GetPersonById("xyz"). Like, everything is constructing these factory instances and nothing ever uses them for more than the one call. All the factory classes extend an abstract base and have to provide implementations for a bunch of stuff.
|
|
#
?
Oct 5, 2017 20:51
|
|