The big risk of using the latest tech and inexperienced people to design and code your systems is that you start off down a dead end because someone can just about make something work.
Nowadays many people with very little training or experience can create applications very quickly and very easily. Although this tends to be more true for business administration applications than for other types of applications.
This is because the latest programming languages include tools that provide almost prewritten solutions to the major parts of many problems and often there are free downloads that solve problems that are too complex to be part of a programming language.
So has designing and programming systems become so deskilled that almost anyone can do it themselves?
For some small business admin systems the answer is quite possibly yes and it is also quite possibly a terrible idea. There are a lot things that we all can do but don't do because we know how badly we will do them.
Also note that I have split up designing and programing, except for trivial systems the two are very, very different skills.
I don't mean visual design, I mean technical considerations such as what database server should we use as well as the database design. Should it be on The Cloud or Local to the business?
Should database access be via stored procedures or APIs? What are stored procedures or APIs?
In traditional IT departments programmers are not given design responsibility until they have a lot of experience and those charged with design may not be very good programmers and that doesn't matter.
Design has not gotten easier over time, way back when, computers had maybe 16-64 users who connected to them with an 80x25 character VDU. Nowadays the Internet has set the expectation that everyone everywhere will have access to the corporate data and this can easily more than offset the gains in computer performance.
It is true that programming mainstream business applications has been quite deskilled as better hardware and more powerful development tools have allowed programs to be written by people with a quite limited understanding of what the program is really doing.
But there is still a very big gap between good programming and bad programming, not just how efficient the code is but how the program handles all those unexpected situations and how easy it is to modify.
Programming non business applications however hasn't gotten any easier, the increase in computer capabilities has just made some things possible that weren't possible before.
For example I wrote PerBI after experience with Cognos Powerplay and when PC memory was jumping up from 4MB, to 8Mb to 16MB, doubling every year or so.
CPU use wise PerBI would have worked quite a few years before RAM increased enough to make it a useful product.
Although this is an extreme example if you look at the code pictured you can see a fragment from PerBi, some C++ code that drops into assembly language. Even with the latest hardware it was worth the development effort to do this because this bit of code can be called a million times per second and the user wants an instant answer.