3 ms·
OP is right and wrong. I am currently a technical lead on a highly complex build that has been in development for a couple years now. A good chunk is in product
by wonderwonder 3y ago
OP is right and wrong.
I am currently a technical lead on a highly complex build that has been in development for a couple years now. A good chunk is in production, tens of millions of complicated 'product' is moved through the system every year. This will eventually scale to billions. Not making that number up, its the existing volume that will be moved over from the myriad of legacy systems we currently use as we build additional functionality.
We are using lots of consultants and they are very expensive. They also don't build with the same quality as our in house teams.
I can build any app I could during my full stack days quicker with no code.
Obviously there are some limits but I have not had to deal with them and they are edge cases in the day to day of a web developer.
It definitely helps to know how to build software and there is a world of difference between the work produced with the tool by a developer and someone that has not coded before.
I went into it expecting to very much dislike it and that it would only allow for toy development. It blew me away.
A team of devs that know how to architect software and this is the key; plan well, can crush projects with this. With that said, if you don't plan and just go in and start building its incredibly easy to build a mess of non maintainable spaghetti no code.