The "culture" behind this is endemic to industry and isn't anything unique to Huawei.
People have already commented on this not being a "team". Let me focus on "programmers".
What probably happened is that many of Huawei's programmers are EEs who happened to take a programming course or two in college.
But learning to think and behave like a good programmer is much more than that. It requires a certain mindset. It may require a certain amount of avocation and enthusiasm, beyond what is taught in an introductory programming course. It requires one to grok good software practices.
Most non-CS majors in college (USA or China or whatever country) probably don't get much of that cultural indoctrination during the few programming courses they take. The engineer wants to pass/ace the programming course. Learning the aesthetics or nuances isn't a priority.
Programming is just too easy. Type a few lines into a file, compile, debug syntax errors, tweak until you get something that looks right. There's no rigor involved. No style. No aesthetic.
Don Knuth called it "The Art of Computer Programming". I submit that many engineers don't think of programming as an art. It's just a means to an end.
E.g. here's an example from a large codebase that was extensively reviewed. The context was Toyota's unintended acceleration problem of about 15 years ago. The design review found things like: Other egregious deviations from standard practice were the number of global variables in the system. (A variable is a location in memory that has a number in it. A global variable is any piece of software anywhere in the system can get to that number and read it or write it.) The academic standard is zero. Toyota had more than 10,000 global variables.[1]
None of this will ever change until and unless a company's top level management understands the problem and mandates change.
Additionally, there's always an incredible push to bring new products to market. That's 1000x more important than it is to follow best software practices.
[1] http://www.safetyresearch.net/blog/articles/toyota-unintende...