|
|
|
|
|
by er4hn
921 days ago
|
|
I think this is valuable for those outside of Qualcomm to understand why they have the role that they do in the mobile space. Having worked there as well I have two observations: - So much of that wall of patents was undergrad level CS concepts with ", for mobile device" tacked on the end. Paraphrasing, don't sue me (kidding..), but that was the gist of it. - Their actual development process was pretty bad. I submitted a bug fix within the first few weeks I was there. Due to their CI process being entirely manual and very broken I was informed nearly a year later that my fix did not work. This tied in pretty well with my department being told they had a "budget"[1] of lines of code they could change and that budget being pretty limited. Overall I left with an impression that they were mostly there to license very old technology and make money from patents. Maybe their hardware team was better, I couldn't say. [1] Most of the effort of our team was spent debugging crash dumps determined to be in "our" part of the code. Nearly all of these were caused by other teams calling into an API we maintained with a null function pointer that "our" code would call. When I asked if we could refactor the API to return an error code if the function pointer was null I learned about the "code budget" and how it would cost too much to refactor. |
|