Thread regarding Qualcomm Inc. layoffs

Drop in Quality

This might be just me, but here it goes anyway... Do you have a feeling that our overall quality has been dropping lately. Not sure what it is but I just have feeling that either we've gotten sloppier, or that there is less hands on oversight or general concern for code quality, or we may not be testing things properly. Again, it maybe just me but wanted to see what you guys think?

by
| 581 views | | 10 replies (last August 7, 2015) | Reply
Post ID: @OP+CPALBRC

10 replies (most recent on top)

Terrible coding quality and readability directly correlates to the cheap H1Bs. Welcome back to reality fellow QCOMers.

by
| | Reply
Post ID: @2eFz+CPALBRC

131211: Don't blame the engineers. I left QC due to being downgraded for trying to push for change of management's insistence on using a Windows interface for certain functions--which we had no control over due to proprietary code, and the fact that QC's internal version of Linux was so outdated that it was a potential security risk due to the number of patches. This of course is my opinion. But when you were regarded as being one of the top UNIX/Linux managers/architects in Silly Valley, that carries weight with some people.

by
| | Reply
Post ID: @1rEz+CPALBRC

Guys we all looking for Jobs and trying to market ourselves Excellent quality coders.Please do not post these kind on internal secrets..its hurts in job search.

by
| | Reply
Post ID: @1MyQ+CPALBRC

Does it matter now?

by
| | Reply
Post ID: @13Ra+CPALBRC

It's all Torrey's fault.

by
| | Reply
Post ID: @1UZw+CPALBRC

Unfortunately this is not anything new. Code quality has always been terrible. Managers/leads never made it a priority for engineers. Everything was about execution and pulling schedules in. It comes from the top. Don't you remember Murthy's all hands meetings saying how proud he was of engineering as they brought up a chip in record time. Instead he should be asking did we miss anything? Did we skip a step we had done before?

The same with coding, you are expected to deliver a feature/fix in very short time. There are no code reviews, no comprehensive test plans. Have you ever tried to make changes to an existing code? So many hardcoded values, so many layering violations. We are paying for all this, as the code became impossible to maintain. The number of code lines mushroomed as people did not want to take the time to have a common code base. Management's response was to hire more people to keep up with increasing overhead. All the waste and short sighted vision finally caught up with Qualcomm.

by
| | Reply
Post ID: @11Ef+CPALBRC

meanwhile the quality of steps taken to CYA is getting better.

by
| | Reply
Post ID: @56G+CPALBRC

@Anonymous131111 - I like your number

by
| | Reply
Post ID: @tNS+CPALBRC

This is the natural outcome of having to release a chip every year.. leaves very little time for any overhead activities.. It is also why QCT bloated up so much..

by
| | Reply
Post ID: @RiS+CPALBRC

everyone is waiting and planning for 15th Sept

by
| | Reply
Post ID: @psp+CPALBRC

Post a reply

: