Sando George

Futurist | Software Engineer | Strategic Advisor | Military Officer

Opinions are my own.

[Sando George @sandogee]

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).

[Marcin Paprzycki @marcinpaprzycki]

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

[Sando George @sandogee]

I think about this everyday. The coding models are standing on the shoulders of giants.

[Sam Altman @sama]

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.

[Sando George @sandogee]

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.

[Sando George @sandogee]

Reading: Reuters / AP (Feb 17, 2026) — fast overview + wider context.
https://t.co/IzKTrrf5bw
https://t.co/1JcmjikIEd

[Sando George @sandogee]

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?

[Sando George @sandogee]

Reading: Ofcom update (Feb 3, 2026) — what online-safety enforcement can/can’t do for AI chatbots. https://t.co/U0d1Xnv8Mq

[Justin Skycak @justinskycak]

Do it scared.
Do it tired.
Do it doubting.
Do it imperfect.
Do it alone.
Do it anyway.

[Sando George @sandogee]

@marcinpaprzycki That's a deep philosophical question 🤣

[Sando George @sandogee]

Is 100% test coverage still unrealistic/suboptimal when it's agents designing and writing tests?

[Sando George @sandogee]

@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.

[Sando George @sandogee]

It just hit me that we're probably not authoring GitHub project readmes for humans anymore.

[Sando George @sandogee]

GPT-5.3-Codex. The vibe is strong with this one. This is the way.

[Sando George @sandogee]

@Jayyanginspires Writing forces a level of accountability that is often ignored when speaking.

[Sando George @sandogee]

Remember when boilerplate generation tools made you feel good as a coder?

[Sando George @sandogee]

So will the mythical 10x engineer now be replaced by a solid 1x engineer doing agentic coding?

[Sando George @sandogee]

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.

[Sando George @sandogee]

Reading: https://t.co/H0YibHtdrV — shows how tool vs memory conflicts can quietly break reliability; provenance makes the mismatch visible.

[Sando George @sandogee]

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.

[Sando George @sandogee]

Reading: https://t.co/DHY9tv3Qns — argues for “LLM audit trails” (tamper-evident provenance) as a practical accountability mechanism.