MC3OZ
Active Member
I've seen just about every combination.Your idea that a software engineer works 5 hours and then chills the rest of the day is absurd.
One experience was being in a small/excellent team which was by far the smartest and most interesting group of people I have ever worked with. What we did was whatever the job required, which sometimes required long hours, but also included long lunches and other leisure activity.
Another experience is 2 programmers working the same number of hours don't produce the same results, some people end up just creating more work for others and increase the chances of poor bug ridden software being written.
Management which makes poor platform decisions, makes bad business plans, changes their mind regularly, or demotivates staff can be a factor.
We don't know what was happening at Twitter, but we can say that in the last 3 years or so not a lot seemed to have been achieved.
it is also apparently true that when Twitter had 1,000 employees they had 2/3 of the current user base. The user base only seem to be growing slowly, while staff numbers have grown by a lot.
It seems on the surface that something was wrong.
Lot of factors going into determining what was achieved or wasn't achieved, when things are going wrong, one way or another, management is part of the problem.