Meetings, phone calls are distractions, especially in the morning, they could also bring different thoughts far from current task.
To have the best result we must reorganize the company according to this, because most organizations prioritize visibility over results, but compensation, promotion and trust structures reward deep work instead of meeting attendance.
I think the problem is elsewhere. The real advantage of big cloud players isn't their individual services. It's seamless integration and simplicity. We need a service integration standard for infrastructure that enables:
- Service discovery
- Networking
- Observability
- Configuration
This benefits everyone: EU companies, US startups, enterprises anywhere avoiding vendor lock-in. A standard letting services integrate regardless of who provides them.
Not just container orchestration (Kubernetes), but something working across bare metal, VPS, containers, and remote machines.
The more I work (started coding 40 years ago, and data engineering 25 years ago), the more I favor designs that are less coupled to cloud features.
If you do so, the offering in the EU just as it is now is well enough to scale.
In short: more computer science, less delegating to cloud operators, stronger designs.
I also prefer to design solutions that are portable and platform independent, cloud providers simplify and hide something to you, it has a cost (not just money) that you cannot quantify on long term and that's clear for who has experience in both worlds.
It helps to empower control over population and fits perfectly in the social and historical context: the emperor blessed by God, the evolution theory, the epic poems, theory of race, the industrial revolution, and modern times don't escape these patterns too, we just suppose to be neutral.
Anyway I think we have a lot to learn from our ancestors, how were they able to move such heavy megaliths?
Gartner’s EAP category shifts focus from CVE volume to real attack paths across cloud and identity. Most alerts never reach critical assets. EAPs show what actually matters.
This is fascinating. Happy to do the research myself, but do you have any recommended reading/sources to learn more about this?
For the practical 'how-to,' I recommend studying GNU Radio and SDR++; they show how to process IQ data or raw audio streams directly, and for sure there are other libraries. On the 'ancestor' side, look at the AX.25 Packet Radio protocol and AFSK (Audio Frequency Shift Keying). These are the same 'softmodem' principles used in FidoNet nodes decades ago.
GSM Arena can help you find phones with integrated FM receivers. You'll notice that many features are market-dependent, meaning: the receiver is often physically present but simply disabled by software.
However, I apply the concepts of FidoNet almost every day. I often design offline-first devices, where store-and-forward logic is a necessity, not an option. Many are deployed in remote areas where signals are never optimal, there a High-Gain Antenna is the only solution.
I also prioritize binary protocols over structured JSON; you have a much higher probability of delivering a few hundred bytes of binary data than a bloated text object when the link budget is tight. Finally, I never expect Wi-Fi to work beyond 5-10m when the router is placed inside the metal structure (that's why my skepticism about BT on cruise ship).