Eryk Orłowski

[Eryk Orłowski @eofek]

VW-1755210459 – unique run with buffer

[Eryk Orłowski @eofek]

typefully test

[Eryk Orłowski @eofek]

Engineers should engineer, not write bureaucracy.

Write structure, not standards.
Manage outcomes, not prompts.
Direct AI instead of fighting it.

That's Vibe Coding.

Not because it sounds cool, but because it actually fucking works.

https://t.co/lInQ48EhOV…

[Eryk Orłowski @eofek]

I watched a team of 5 architects spend 3 weeks writing development standards on Confluence.

Cost: $120,000
Pages: 200+
Actual usage: Zero

Today I did the same thing in 2 hours.

Thread on why engineers shouldn't write boilerplate 🧵

[Eryk Orłowski @eofek]

How to start tomorrow:

1. Pick your most boring task
2. Spend 90 min decomposing it (<2h chunks)
3. Write the task to CREATE the standard
4. Point AI at it
5. Measure what happens

Track: Time saved, quality metrics, issues prevented.

Then share the data.

[Eryk Orłowski @eofek]

2025 reality:

Best AI teams won't have prompt engineers

They'll have context architects who get:
- Info retrieval
- Compression
- System design

Revolution is here: $0.68/month

#Future #AI #TechLeadership

[Eryk Orłowski @eofek]

Prompt Engineering is Dead.

Found 50k lines where an LLM wrote regex to make itself dumber.

The future isn't better prompts. It's Context Engineering.

Thread on transforming a chat system from regex to AI 🧵

#AI #ContextEngineering #TechLeadership

[Eryk Orłowski @eofek]

Builder lessons:

1. Check existing code first
2. Engineer pipelines, not prompts
3. Read research (20+ papers)
4. Test real data
5. Compound gains

Solutions might already exist

#AIBuilder #Engineering