It's not a simple as that. If you are on a team of developers who are building applications on top of clearly defined APIs, all the heavy lifting from a systems perspective should already be done for you. This is to ensure the company doesn't end up with 15 different versions of the same code in each release that needs to be maintained in the future. I think mostly it comes down to the bottom line: a business doesn't want to spend money on building the same library over and over again.
There are instances when low level systems programming is needed, and whoever is assigned that task should have the freedom to do what is needed to ensure the systems provided can perform at the desired level and provided whatever is necessary for security and so on. There is nothing canned that can do that, so you better have your best developers on that given the potential impacts to your customers and therefore to your bottom line.
If you work for yourself - then do what you want since you're calling the shots.
Policy choice is relative to your business risk/exposure. Ultimately whatever you choose to do with your own programming (if you work for yourself or you're just a hobbyist) will be proved out by your clients/users when they use (break) your software and systems. On the other hand, if you work for someone else as an employee, then you are bound to follow their rules, regardless of your views. You can try to change it, or you can find another job elsewhere.
It's not simply a matter of these things being beyond anyone's ability, but it is also true that there are different levels of skills and experience that exist in a business environment. A good choice would be to partner your systems developer with your brightest applications developer to cross pollinate. Unfortunately, my experience also suggests that many companies don't do a good job of mentoring and growing talent within the company. People get assigned to silos and languish unless explicitly transfered to the group with a different focus. It really comes down to the philosophy of your employer.