3 ms·
The newbie programer effect is part of the lacking Integration of Zoning in a Codebase. Thus its a IDE problem. You cant go and declare some basic tool classes
by lunchTime42 11y ago
The newbie programer effect is part of the lacking Integration of Zoning in a Codebase. Thus its a IDE problem.
You cant go and declare some basic tool classes only editable by a expert/architect or a newb under "SignOff" Supervision.
There is also no real metric on expertise, and a way to prevent non-experts to go banana on something beyond the scope of there fields. You do not want a assembler coder going first time OO and in reverse. What actually would help is a sort of guild - where one has to accomplish certain feats first, before beeing allowed to level up..
- buserror 11y agoI agree that in an ideal world, it would work like that; however in most companies, 'programmers' are hired, rarely as 'juniors' and sometime are moved across the company to a new team, who then realize they are... err ... 'junior' at best. Then there is the minefield of how to break the news to someone that they can't be trusted 'just yet', with the discrimination minefield that implies etc. And in many companies, you can't even go an tell a colleague that their change is in fact, crap, and has to be redone properly. Never been in a company where that didn't create huge waves, regardless of the level of proof you can attach to it. I hear in some companies (google?) it's expected, but it's an exception, in my experience...