31–40 of 64 posts
In my experience, the gap was more between "people that do things/makers" (designers, hackers, texters, testers, linguists, statistics people) and "people that talk" (aka business type people, usually economy students). It occured that the talking-only people where at some point so out of touch from the work that actually happens, but yet in charge, and interfering with everybody.
"Not getting along" is what happens when one believes that "I" is more important than "we".
Once one gets beyond themselves, one can "get along". They still may not agree, but now they've put themselves in a position to solve problems, not perpetuate conflict.
This is also true in the general class "Why x can't get along with y," not just for programmers and business type people.
That said, there are plenty of conflicts between programmers and their managers. Usually, it's because the management doesn't understand programming.
In my experience, the gap was more between "people that do things/makers" (designers, hackers, texters, testers, linguists, statistics people) and "people that talk" (aka business type people, usually economy students). It occured that the talking-only people where at some point so out of touch from the work that actually happens, but yet in charge, and interfering with everybody.
b> How long it will take?
p> About 2 months.
b> We need it in 1 week.
....
I believe it's largely down to short term goals versus long term goals. From the business perspective, the company should do things quickly because that means the jobs are more profitable, cashflow is stable, and the business team believe that they can always find more clients even if the product is horrible. This is the short term outlook. From the programmers perspective the company should do things slowly because…
Also, programmers are usually "to the point" people, while business people love buzzwords.
There are good and bad communicators on both sides.
I believe it's largely down to short term goals versus long term goals. From the business perspective, the company should do things quickly because that means the jobs are more profitable, cashflow is stable, and the business team believe that they can always find more clients even if the product is horrible. This is the short term outlook. From the programmers perspective the company should do things slowly because…
I think you're being very optimistic about programmer motivations, to be honest. > From the programmers perspective the company should do things slowly because that leads to more maintainable software, less technical debt, and higher quality products with fewer faults. Less money comes in, but the clients stick around for the quality goods. This is the long term outlook. This is the good version. But as we all know,…
I believe it's largely down to short term goals versus long term goals. From the business perspective, the company should do things quickly because that means the jobs are more profitable, cashflow is stable, and the business team believe that they can always find more clients even if the product is horrible. This is the short term outlook. From the programmers perspective the company should do things slowly because…
Also, programmers are usually "to the point" people, while business people love buzzwords.