Now, I am using SQL statements to read out the necessary information from the database (PostgreSQL) containing the simulation results.

"SQL is really cool"

I'm very impressed.

Once you get used to SQL statements, you can easily create the columns of data you want, with the freedom to link between tables. It's like magic.

I am now using it in conjunction with QGIS (a GIS application), and it is very easy for me to create drawings.

-----

However, SQL is a very counter-intuitive interface, and if you are going to use it in an advanced way, it can be quite cumbersome.

Even though it is SQL,

"You'll have to work very hard to be easy"

This is a common contradiction in programming.

-----

I'm confident that if I had access to SQL (or Golang) all year round, I would be able to write processing programs on the spot.

(For C/C++, I believe I'm close to this realm)

Annual reports, patent specifications, Excel spreadsheets for budget management, invention consultations, executive briefing materials, external presentation review documents, customer demonstrations, conference presentations, etc.

If I can live in a world where there is no such thing, I can declare, "I will become the SQL King!"

-----

If I don't create things myself and outsource the programming and SQL, it is natural that my technical skills will decline.

However, it is also true that I cannot continue to be a member of society if I am obsessed with making things.

On the other hand, if senior engineers, who have neither humanity nor connections, lose their technical skills, what will be left?

The difficult part is "resource allocation" - in other words, "balance"。