>It's not just the company that suffers. These situations usually result in the rest of the team having to pick up the slack to get things done. The person doing little to no work is taking advantage of their peers' productivity
Had a gig like this, the codebase was so shit it took days to do simple stuff, it was highly domain specific logic I cared nothing about and I was going to leave ASAP.
Most of the time l bulshited my way through turns out a lot of the features got scrapped because they weren't necessary in the first place (ie. there was another way to do it for eg. or client didn't really need it), requirements got updated that would have made any progress I did worthless,etc. There were two crunch weeks before releases where I did some OT to help push stuff out the door (wasn't even my backlog) other than that yeah - did two months of work in 6 months I was there.
Had a gig like this, the codebase was so shit it took days to do simple stuff, it was highly domain specific logic I cared nothing about and I was going to leave ASAP.
Most of the time l bulshited my way through turns out a lot of the features got scrapped because they weren't necessary in the first place (ie. there was another way to do it for eg. or client didn't really need it), requirements got updated that would have made any progress I did worthless,etc. There were two crunch weeks before releases where I did some OT to help push stuff out the door (wasn't even my backlog) other than that yeah - did two months of work in 6 months I was there.