There is a moral hazard here. By accepting that APIs are forever, you tend to be more cautious and move toward getting it right the first time.
Slower is better... And also faster in the long run, as things compose.
Personally, I do believe that there is one best way to do things quite often, but time constraints make people settle.
At least it is my experience building some systems.
Not sure it is always a good calculus to defer the hard thinking to later.
You will probably have time related free credits for AI usage.
The more you sell stuff that are in demand and ship fast, the higher price you can command.
Otherwise you just get basic income.
People will have to be creative. Creativity doesn't scale to machines. Creative decision making has too many branches.
So time based costs for product manufacturing and procurement.
Everyone will barter again in a sense.
Better money circulation. Those who just want entertainment can also do nothing. But entertainment will be a more important field. Already the case with tiktok, everyone is becoming an interntainer(sic) these days.
You have things such as the police olympics so to speak in the UAE...
:)
So coaching people, personal improvement, wellness, will be good fields to be in.
There will be more of it where it does not matter.
Maybe eventually with times.
At the moment, in my experience, most systems rely on hyperlinear semantics. Especially scalable ones.
Current llms cannot physically handle this at the moment. Maybe with biological or quantum (sic) computing.
But even then it is quite impressive.
Concretely in my use case, off of a manual base of code, having claude has the planner and code writer and GPT as the reviewer works very well.
GPT is somehow better at minutiae and thinking in depth. But claude is a bit smarter and somehow has better coding style.
What is a negative number? What is multiplication? What is a complex "number"?
Complex are not even orderable. Is complex addition an overloading of the addition operator. Same with multiplication?
What i squared is -1 ? What does -1 even mean? Is the sign, a kind of operator?
The geometric interpretation help. These are transformations. Instead of 1 + i, we could/should write (1,i)
A lot of math is not very clear because it is not very well taught. The notations are unclear.
For instance, another example is: what is the difference between a matrix and a tensor? But that is another debate for anyone who wants to think about it. The definition found in books is often kind of wrong making a distinction that shouldn't really exist more often than not.
Isn't it the mathematics that is lagging? Amplituhedron? Higher dimensional models?
Fun fact: I got to read the thesis of one my uncles who was a young professor back in the 90's. Right when they were discovering bosons. They were already modelling them as tensors back then.
And probably multilinear transformations.
Now that I am grown I can understand a little more, I was about 10 years old back then. I had no idea he was studying and teaching the state of the art. xD
What was new was not tensors. It was the representation in SU of mesons for photon-photon collisions. But even saying that is skimming the surface.
I can't read beyond the knowledge gap.
Do these administrations still purchase licenses for software or do they just create open source maintained by government employees?
How much are they willing to pay?
Because people in Europe are notoriously paid less so I am curious of the financial aspect.
Also curious about the logistics of ownership and support...
I know that my city's administration has a quite active development department.
I don't know the current salary ranges,but they offer other values like vacation days, Work-Life-Balance (proper time tracking to avoid extra hours etc), part-time.offera, child care options and some other benefits, which most corporations won't give in addition to being the state, which means they won't go bankrupt, won't do reductions in force in the way companies do it, ...
Islands is just a catchy name I guess. I always thought the markojs terms for it made sense, but are more technical / less catchy: they called it “full page hydration” -> everything needs to be delivered as js and “component level hydration” -> islands, only specific component sub-trees need to be hydrated.
Then “sub-component level hydration” would be resumability like in qwik where only events and their dependencies get serialised as client js.
Yeah. Well to their defense, it is probably to be understood as islands of interactivity lost in a sea of static elements.
The term is definitely more evocative.
At least it is my experience building some systems.
Not sure it is always a good calculus to defer the hard thinking to later.
reply