No, its false, what is complicated is to understand what problems you should resolve, and resolving it. What is overcomplicated is when you try to overengineer because you dont clearly define the problems you are trying to resolve.
Just a clear example : you want an app who planificate booking reservations, do you need to be an expert in postgresql or mysql ? no, you build a first version of this app, without being an expert, and maybe after, you will read more documentation about how to structure the data, improving performance. Why you should be an expert in everything ? just why?
My point is that coding is the easy bit, assuming you indeed understand what the problem and you don't overengineer it. But in order to apply all the (supposed) best practices the amount of stuff you end up doing before writing a single line of code is ridiculous.
That said it does very much depends on the scale you're building for... a simple website doesn't need a code scanner or even TDD, but a bigger piece of software that gets released weekly requires a whole lot more. In the former case just indeed spin a mysql container and get chatgippiti to generate you a couple schema's. Now imagine that it grows to serve 100K+ people, you would need to retroactively introduce automated testing to be able to keep releasing regularly... would have been nice if you started with that right at the beginning. Or lets enable a code scanner on a 2 year old code base... you're not gonna be happy about what it's going to tell you :)
So no, you don't need to be an expert in postgresql to get started. But being able to consider all the best practices and what to apply and continually do that, isn't an easy feat.
No, its false, what is complicated is to understand what problems you should resolve, and resolving it. What is overcomplicated is when you try to overengineer because you dont clearly define the problems you are trying to resolve.
Just a clear example : you want an app who planificate booking reservations, do you need to be an expert in postgresql or mysql ? no, you build a first version of this app, without being an expert, and maybe after, you will read more documentation about how to structure the data, improving performance. Why you should be an expert in everything ? just why?
My point is that coding is the easy bit, assuming you indeed understand what the problem and you don't overengineer it. But in order to apply all the (supposed) best practices the amount of stuff you end up doing before writing a single line of code is ridiculous.
That said it does very much depends on the scale you're building for... a simple website doesn't need a code scanner or even TDD, but a bigger piece of software that gets released weekly requires a whole lot more. In the former case just indeed spin a mysql container and get chatgippiti to generate you a couple schema's. Now imagine that it grows to serve 100K+ people, you would need to retroactively introduce automated testing to be able to keep releasing regularly... would have been nice if you started with that right at the beginning. Or lets enable a code scanner on a 2 year old code base... you're not gonna be happy about what it's going to tell you :)
So no, you don't need to be an expert in postgresql to get started. But being able to consider all the best practices and what to apply and continually do that, isn't an easy feat.
yes the "supposed" best practices.
The point is here