null
...
It is standardisation because it proscribes how you should do it.
Because you don't understand them, their capabilities and what they are doing / will do.
Why the team should have to suffer for management weakness is beyond me.
Software Development and Programming Careers (Official Discussion Thread)
- Thread starter Blackking
- Start date
-
- Tags
- careers programming
It is standardisation because it proscribes how you should do it.
Because you don't understand them, their capabilities and what they are doing / will do.
Why the team should have to suffer for management weakness is beyond me.
I'm not sure who you mean by don't understand their capabilities. Are you talking about management or other team members?
The reason its not standarization is because if its not working, you adjust how things are working. Its not supposed to get in the way of projects getting done on time and on budget. If its getting in the way, management isn't managing the project well.
That's almost always the crux of the problem. Managers are completely inept and what they do.
Yea I agree. Bad managers will always make for a bad experience on a project, because they don't know what they're doing. My experience with project management at my current company vs past companies is greatly different. Like, you either get the managers that are too p*ssy to stand up for the development team or you get the ones that try to squeeze every bit of efficiency out of the developers (o man, this brings me back to the dumbest project I've ever worked on, lol). My current company is pretty good with the project management, so I try to only work on projects where we have some control over it rather than the client.
tangent: Good discussion. I don't get to have these convos at all these days
null
...
Why can't a bunch of Iron Men Challenge winners beat the winners of last year's superbowl in a one off game. despite the Iron Men being fitter?
Why can't a bunch of beach footballers beat the winners of the last world cup?
Why when a top soccer player is asked "how did you know to pass the ball there to the striker for the goal" do they often say "i just knew he was going to be there".
Why do experienced staff need to keep an eye on the apprentice aka trainee?
That dynamic is a sliding scale. Managers are on the more ignorant side of that equation so need explicit guidance to know what is going on. They cannot "just know" to the same degree as people who know what they are doing. Otherwise it is too confusing.
Just like how for kids numbers are 1, 2, 3, 4 etc, for secondary school pupils numbers are tools and for university professors numbers are definition mutable abstractions. The kids need a simplistic system to work within otherwise it would be too complicated for them. They need simplifications. They need hard-rule paint-by-numbers systems (defined by someone else) to follow. The acadmics don't need that because of their depth of understanding.
Daily Scrum is nonsense outside of a naroow set of project cicumstances. Have you read what scrum is intended to do? I would prefer not to have to quote text here.
That is not what standardisation means. It is a standard process.
Did you study CS?
-
@Regular Developer I edited the post. You might want to revise that "dap"
Last edited:
Kind of. I did computer engineering, but did more software than electrical.
Ok, I thought it meant as a way to make people conform.
EzekelRAGE
Superstar
Im enjoying learning/working with backend more than I did frontend in this bootcamp. 
I enjoy the JS frontend stuff on trying to get something to work behaviorwise, but didnt like messing with html/css trying to make it look good
I enjoy the JS frontend stuff on trying to get something to work behaviorwise, but didnt like messing with html/css trying to make it look good
There's a duality. It's a standard process, that's supposed to be flexible to fit the team, but as soon as you start to stray from the framework people complain about how you're doing scrum/agile wrong.
This was my realization when working with emberjs and angular.Im enjoying learning/working with backend more than I did frontend in this bootcamp.
I enjoy the JS frontend stuff on trying to get something to work behaviorwise, but didnt like messing with html/css trying to make it look good
null
...
I'm not even sure what to say to that
. Whatever it is it is pre-defined. Even the "you can do what you want as long as you stay within this (sheep) pen" is pre-defined and limited by the area of the pen.
How big are the projects that you work on?I'm not even sure what to say to that
null
...
Some big, some small. Some multi-year projects. Some minor tasks that only take a few days end-to-end. It depends.
I edited the post above to expand on what I meant. Still somewhat truncated but I want to avoid "para-graphs"
Software Development and Programming Careers (Official Discussion Thread)
When done correctly on the right type of projects, I think its useful. Its not supposed to be standardisation, It is standardisation because it proscribes how you should do it. It helps me communicate with the team, because I also tend to be heads down on tasks. Because you don't...
www.thecoli.com
That's the point I'm getting at. But even when you start to make it their own, somebody comes by likeI'm not even sure what to say to that
and says you're doing it wrong. I tried to make a point about sizing user stories on my team to make it make sense for us. They told me that was the wrong way to do it 
, then in almost the same breath told me that scrum is designed to be tailored to each individual team's needs.
Nah, lol, the dap was because I appreciate the discussion. I think its important as developers to talk about things that influence what we do
As to the rest, i know what you mean. Sure, you can say its nonsense in the incorrect project, but thats anything. If the opposing soccer team won't press us, why would we follow the same tactics as when a team pressed us? Scrum is just a part of how an Agile based project is run. It can feel useless when there's nothing to talk about (in those cases the meetings should be 5 minutes). Tasks are completed and no blockers. But when there are blockers or there is new information, its the time that brings it up, which is in my opinion, more valuable than the meetings where nothing is discussed is unvaluable.
Last edited:
Updated my last...
I'd also like to point out that I enjoy projects with a bit of a startup feel, so the project has an initial direction, but we may need to pivot along the way as we discover more about the project or the environment.
I'd also like to point out that I enjoy projects with a bit of a startup feel, so the project has an initial direction, but we may need to pivot along the way as we discover more about the project or the environment.
Last edited: