|
raddevus wrote: It shouldn't have to be that way. If everyone were truly invested at the same level then it would not be that way. It has to be that way, that's how nature works and how we are programmed. The individual tries to gain as much as possible, because that's advantageous in reproducing. The group as a total has to check the individual.
raddevus wrote: You know that is the story that the Agile Methodology uses. I think my explanation works better for human nature
The agile thing will pass eventually. We don't build houses or cars "agile", because we want something decent. With software, we just want something new. Agile caters to getting sh*t to the market, not to develop some good long-term foundation.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
Eddy Vluggen wrote: Agile caters to getting sh*t to the market
Don't hold back. Let the world really know how you feel.
|
|
|
|
|
While most people WILL try to do as little as possible, I believe this is self-optimization over laziness.
Next, Paretos Law says that 50% of the productivity belongs to the square root of the number of workers. So if 10,000 farmers are out there... 100 of them make 50% of the output.
This is nature at work. Skills and abilities are not distributed evenly.
But the next part is Motivation. A manager (or management) that motivates his employees to really show up (and not phone it in, like they do under socialism/communism [the govt pretends to pay us, so we pretend to work])... Is the one that gets the most done.
Right now, that appears to be Amazon. But EVERY hard working employee there has their own self-interest at heart AS WELL as working to make the company better. Over time, it will fail. Just like MSFT, IBM, DEC, and so many others did before them. Capitalism requires these failures, to give birth and make room for new ideas.
The essence of this thread is true. Any Methodology will work with suitably (motivated, responsible, and intelligent) people on a project.
The counter proof is, lets staff the project with Low(65) IQ individuals to program, and to represent the users. And lets apply the Best Methodology and Whatever motivation you want... Good Luck!
|
|
|
|
|
Very good and interesting points.
Kirk 10389821 wrote: But EVERY hard working employee there has their own self-interest at heart AS WELL as working to make the company better.
I agree 100%. If any party in the work relationship doesn't get something out of the situation then they are not going to stay around.
Kirk 10389821 wrote: Over time, it will fail. Just like MSFT, IBM, DEC, and so many others did before them. Capitalism requires these failures, to give birth and make room for new ideas.
I think that is a great point. Systems were meant to be useful for a while and then decay. That's how it works. But we see these HUGE companies that try to keep going forever and they become total garbage.
I just read this principle in Tom Peter's book Re-Imagine[^]
|
|
|
|
|
raddevus wrote: We've promoted them to positions in management. Ahhh, the Peter Principle. I find it holds true more often than not.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
David Crow wrote: Ahhh, the Peter Principle. I find it holds true more often than not.
Yes, unfortunately, in these enlightened times the darkness still prevails.
|
|
|
|
|
Another reason I miss my cube, nap time.
|
|
|
|
|
(being awakened by noise) : "Can all you people keep that Agile noise down over there! Do you really have to iterate so much?"
|
|
|
|
|
Promoted to their level of incompetence often because they have been to the right schools.
|
|
|
|
|
Yeah, it's very difficult to deal with managers who've never done tech work themselves. Much better if a manager has been in the trenches too.
|
|
|
|
|
raddevus wrote: Contrast that to a project where you stand the chance to make a $1 million.
Hypothetically (with a big H!) if I were to work at one company for 30 years...
...there are actually quite a few people at the company where I work that have worked 30+ years for that company, though the only devs that are 30-yearers are COBOL devs and they're retiring left and right, haha....
and my average salary over those 30 years, say, $90,000 / yr....
I would earn $2.7M, pre-tax, etc.
I propose that one should look at employment as "the big project." But then again, this is all so totally hypothetical because most devs never stick around for 30 years. If I were working for NASA or SpaceX, or even Apple, Microsoft, IBM, Google, or Amazon, maybe that would still be possible.
raddevus wrote: There is a lot of separation on software dev projects.
I would use the word "disconnect." Particularly between management and their team.
Latest Article - A Concise Overview of Threads
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: I propose that one should look at employment as "the big project."
That's a very good point. Very nice re-framing of the idea.
However, I want the $2.7 all at once. It's not near as fun getting it over time.
Marc Clifton wrote: I would use the word "disconnect."
That is a better term for the situation. It is a disconnect and it happens a lot.
|
|
|
|
|
raddevus wrote: I want the $2.7 all at once.
Chances are that if your product is making you that much money, then you are also having people on your payroll, and company overhead, etc. At the end of the day you are making 90K a year.
Very few people have a software product that earns good profits every year, and they are the only one on the project. Notch with Minecraft is a great example, but even after a couple of years he had to hire help.
|
|
|
|
|
Slacker007 wrote: but even after a couple of years he had to hire help.
Just send the $$$, not the people.
|
|
|
|
|
raddevus wrote: If You Were Developing a Product With Chance of Making $1,000,000
Contrast that to a project where you stand the chance to make a $1 million. Aren't those the same?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
Oh, the one was the header, the other was the sentence following the previous paragraph.
|
|
|
|
|
raddevus wrote: Scenario-Focused Engineering: A toolbox for innovation and customer-centricity
Could they not have come up with a slightly less-buzzwordy title? Something like:
Scenario-Focused Engineering: A proactive blockchain-orientated power-toolbox for agile dev-ops innovation and running enterprise-level-customer-centricity up the flag-pole to see if it flies blah, blah, blah. Cloud!
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
PeejayAdams wrote: Could they not have come up with a slightly less-buzzwordy title?
No. because, in the end, it isn't the product...it's the marketing. I mean look at stuff people are paying billions for...facebook, etc.
|
|
|
|
|
I haven't seen that book, but MS was talking about those ideas back in the 1990's
And I've work with that methodology ever since. It works!
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Walt Fair, Jr. wrote: I haven't seen that book, but MS was talking about those ideas back in the 1990's
And I've work with that methodology ever since. It works!
Very cool. And I believe that it would/does actually work.
Those few principles are very, very good and get to the core of what should really happen.
|
|
|
|
|
Buzz word laden hype. I just want to know what the users are trying to accomplish.
Maybe I'm just bitter.
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
|
|
|
|
|
When you find out -tell the users.
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
S Douglas wrote: Buzz word laden hype.
Wow, you really thought those few bullet points were buzz word laden hype?
That's fine. Maybe you have a lot of experience and you know how to get to the point on a project?
That's probably it. I notice that after 25 years of software dev / IT work, projects are so repetitive it can seem like everything is hype.
|
|
|
|
|
So many devs are not business focused.
Just look at the complaining we had here recently about being asked to dumb down their code.
Had a case recently where a dev was complaining about being taken off a task because it had been given to him in order to make senior engineer.
My response was 'take care of the product and the career takes care of itself'. ie, focus on the product and nothing else. Not how cood your C++ is, how many fancy, nerdy, features of a language you can use, but instead on how quickly you can push good product out the door.
|
|
|
|
|
Munchies_Matt wrote: So many devs are not business focused.
That is a very true sentence. Devs often become way too focused on tech and tech is meaningless by itself.
Munchies_Matt wrote: 'take care of the product and the career takes care of itself'
That's a good mantra to work by.
|
|
|
|