Pin: My weekly series (pragmatic, reflective):
Mon - Decision Craft
Tue - Systems Thinking
Wed - Signals & Sensemaking
Thu - Resilience & Readiness
Fri - Foresight
Sat - Strategy Studio
Sun - AI & Thinking
Daily: Current Affairs Everyday briefs (cross-cutting).
ENERGIES (MDPI) told me that I should promote my work ... They published it... so, here is the promotion ;-)
Title: Dynamic Knowledge Management in an Agent-Based Extended Green Cloud Simulator
Link: https://t.co/njKuB4c6bU
I have so much gratitude to people who wrote extremely complex software character-by-character. It already feels difficult to remember how much effort it really took.
Thank you for getting us to this point.
The current wave of vibe-coded AI systems resembles the spreadsheet era in how it decentralizes capability and embeds critical business logic outside formal engineering controls, but with a more opaque and potentially more hazardous failure surface.
Grok isn’t being judged on “AI potential.” It’s being judged on the distribution loop: personal data → generation → virality → harm. EU/UK regulators are testing whether “safety by design” is real or just a blog post. Where should liability sit?
@marcinpaprzycki Full agreement that formal verification is the only TRUE 100% test. I'm mainly referring to common unit/integration testing here though. I decided to try and was able to get one of my code bases to 100% in about 12hrs using GPT-Codex-5.3. I had done about 53% manually.
For years I've thought of the idea of cloning myself to get more work done. Now we have fairly capable agents that are easy to spin up and direct. I'm happy.
AI will draft you a plan that sounds like it survived a staff brief. But if you can’t trace where each claim came from, you’re outsourcing judgment—not typing. Habit: demand provenance (“source / assumption / confidence”) before you act.