nenadst

try it with something more "obscure" like e.g. creating an OPC/Ua Server from scratch.

It fails spectacularly - the code wont even compile and there are many things missing to get a working solution.

"... when examining only those who passed the exam (i.e. licensed or license-pending attorneys), GPT-4’s performance is estimated to drop to ∼48th percentile overall, and ∼15th percentile on essays ..."

so this means that ChatGPT is right in the middle of the performance of licensed or license-pending attorneys.

and for essays its still better than 15 percent of the humans.

Still quite impressive ...

from their website ".... can now enjoy the milestone innovations of the 11 Alexandria Pro edition.."

which means that you cannot use "Client-Server" databases (Mysql, Postgres, etc.), only localhost access is supported.

you can use ZeosLib etc. but its just one more hurdle to take.

tldr version:

Principles are like rules:

you are either compliant or you are not. This gives rise to “bounded sets” of rule-followers and rule-enforcers rather than “centred sets” of people with shared values.2

Instead, I started thinking about properties:

qualities or characteristics of code rather than rules to follow.

Properties define a goal or centre to move towards. Your code is only closer to or further from the centre, and there is always a clear direction of travel.

.....

and then he gives a list of five properties that good architectures can aim for.

15 years after Scrum was invented and 10 years after the Agile Manifesto someone writes such an article ?

I agree that knowledge about Agile was not widespread enough in 2011, but this reads like something from the early 90s.

am i the only one expecting the article to be about Service oriented Architecture ? :-)