- with AI, bad engineers (bad designs?) lead faster to catastrophe - Frontier AI companies pay their SW engineers very much

--> we need highly-skilled sw engineers and the lesser ones will get out.

Kind of what outsourcing did but x100.

As a manager, I'll still have to think how I grow young SW engineers to top SW managers.

That was geared against telemarketers or abusers, so that the callee could fetch a police officer that would acknowledge the fraudulent call.

Today all this data exists in databases. It would be so easy to check call logs from telemarketers to check if they ever called someone on a do-not-call list.

Or maybe that's exactly the right example...

To be honest, scraping them on broadcast TV will probably have little influence, even though in the wrong direction, because TV is no longer the media with the most influence.

The real failure is that no one cared to regulate ownership of digital medias, i.e. social networks, Youtube, etc. These have shown documented examples of influencing elections directly.

I totally understand why the OP would use only FBV, however when writing REST APIs you will want CBV to reuse base classes such as ListView.

The paper is actually poor in data and mostly requotes other studies.

Great, but since no human has looked at them, how do you know that they are relevant and actually test undesired behavior?

Also, would you be able to point at which tests should be added in the future?

Who needs memory when your model is set in silicon ?

But is there a single UI abstraction that succeeded in affordability for newcomers while maintaining performance and solid architecture?

It is high time to solve the write-3-apps for each usecase (iOS, Android, Windows). I use MAUI on some projects but it is still not perfect.

The way forward for Apple is to open source more and more and let the Swift community build a cross-platform solution.

Open up your mind and learn other cultures.

At the end it is more productive to be focused on the right target, than to gain 15% of productivity because you use whatever tools. Note that this is not mutually exclusive, but putting brain power in thinking about the product, rather than about the productivity hacks, is what matters.

The problem is that most companies don't care about thinking. You may have more chances to get promoted because you are sweating and running everywhere, instead of calmly thinking, looking through the window and developing mental models.

Time to 1st token is faster on the M5 because of HW accelerators helping the prompt interpretation (and it is CPU-bound).

Token generation after that is GPU-bound and will profit from the higher bandwidth of the M4 Max.

- Display drivers don't need access to the network

- Display drivers don't need to write to the window manager

- Display drivers just need to display the data that needs displayed

- If you sign a driver, you take responsibility for it. Else just leave people run any driver they see fit