This is the typical german mindset. You better be avarage, following the german mediocrity.
-3 karma · joined April 24, 2017
This is the typical german mindset. You better be avarage, following the german mediocrity.
A good product matches people's desires, is easy to use and of high quality.
I write JS-code on a daily basis for over 10 years now, mostly in a functional fashion, and I get things done on time without much headache. Also I know the platforms well and their issues.
The bad side of JS is not the language or the underlying platforms, but the huge amount of substandard programmers creating aweful libraries and frameworks which are used by even less capable hackers.
Experience doesn't need to be an indicator for productivity. Also often you can find programmers who seem not productive at all, but without their contribution the whole project might fail.
The best thing to do is to set your milestones, and put trust in the people you hired. Then check your progress regulary. Talk and listen to your employees. Be trustworthy yourself.
You don't want to know how much code a new hire can put out in a month. It doesn't matter. You want to know weather you reach your business goals. So communication, trust and transparency will improve every contribution of your engineers.
What you can do is start writing tests. Cover the pasta you're working on and use common coding standards. With some examples at your hand on how to improve things, meetup with your lead and explain him your sorrows without criticizing him. Tell him what makes it hard for you and others to work with the code. He'll also have valuable ideas for improvements.
Real nnpps are less common than you might think.