Systems Thinking

286 posts

Systems Thinking banner
Systems Thinking

Systems Thinking

@OnePersonSys

AI leverage One-person systems Digital income models Build systems. Not jobs.

San Francisco, CA เข้าร่วม Mart 2026
50 กำลังติดตาม11 ผู้ติดตาม
Systems Thinking
Systems Thinking@OnePersonSys·
You don’t need more AI you need a system otherwise you’re just moving faster in the wrong direction agree?
English
0
0
0
5
Systems Thinking
Systems Thinking@OnePersonSys·
@jspeiser tools changed but who’s in control of the system now? you or the tool?
English
0
0
0
283
Joe Speiser ⚡️
Joe Speiser ⚡️@jspeiser·
First week with zero OpenClaw. every routine, every automation runs on Perplexity Computer now. No command line. No babysitting. Time to service has cratered. I didn't switch for the hype. I switched because my time kept disappearing into a black hole. Now it doesn't.
English
75
1
262
29.9K
Systems Thinking
Systems Thinking@OnePersonSys·
@2sush using AI isn’t the flex either understanding it is 🙂
English
0
0
0
5
sush
sush@2sush·
you don’t hav to love AI, but ignoring it isn’t a flex.
English
50
0
66
1.7K
Systems Thinking
Systems Thinking@OnePersonSys·
@sahill_og we’re not handing it over we’re trading it for speed at what cost?
English
0
0
0
17
Sahil
Sahil@sahill_og·
People fear AI taking control. Reality: we’re handing it over.
English
21
3
27
1.5K
Ole Lehmann
Ole Lehmann@itsolelehmann·
pretty sure in 6-12 months most people will do 90% of their work via claude interface
English
66
2
104
8.4K
Nalin
Nalin@nalinrajput23·
Be real… does learning to code even matter anymore with AI everywhere?
Nalin tweet media
English
112
6
165
21.3K
Greg Powell
Greg Powell@ThoughtfulTechy·
You only need two things to be successful in tech: 1. Curiosity 2. Hunger
English
57
39
304
10K
Systems Thinking
Systems Thinking@OnePersonSys·
@fing_me_gud Engagement is good, but it’s not enough. Build something real, and people will engage anyway.
English
1
0
4
84
Blue
Blue@fing_me_gud·
If you follow me, I’ll follow you. If you reply to me, I’ll reply to you. If you engage with me, I’ll engage with you. Let's engage and support each other! 🚀🤝
English
192
15
148
5.8K
Systems Thinking
Systems Thinking@OnePersonSys·
If AI writes your code but you can’t explain it are you still coding or just approving output?
English
2
2
4
91
Marcin Krzyzanowski
Marcin Krzyzanowski@krzyzanowskim·
every other day I want to quit supporting claude code in the Commander - the SDK is either flacky, broken here and there with each update, or straight up lack support certain features
English
5
1
20
3.7K
montano
montano@lucas_montano·
claude and codex just made it easier to build native apps.
English
17
1
145
8.7K
Systems Thinking
Systems Thinking@OnePersonSys·
@MillionInt we’re not bad at measuring intelligence we’re measuring the wrong thing 🙂
English
0
0
0
140
Jerry Tworek
Jerry Tworek@MillionInt·
Lots of inconvenience comes from the fact that we’re just very bad at measuring intelligence And we think we’re not
English
9
5
220
12.1K
Systems Thinking
Systems Thinking@OnePersonSys·
@burkov models arguing is the feature humans picking sides is the bug 🙂
English
0
1
4
1.4K
BURKOV
BURKOV@burkov·
GPT-5.4 > Opus 4.6 And Google still doesn't have anything even remotely competitive.
English
139
25
869
121.9K
Suhas
Suhas@zuess05·
You just got a god-tier idea for a app/saas. What is your literal next step? A) Open Claude Code and start working B) Build a waitlist landing page C) Cold DM 50 potential customers D) Tweet the idea to see if anyone cares Be honest.
English
58
0
35
3.1K
Systems Thinking
Systems Thinking@OnePersonSys·
While building my own runtime i realized most people don’t have one they just react what’s your intent?
English
0
0
1
25
Systems Thinking
Systems Thinking@OnePersonSys·
@Bencera this is the real shift not AI replacing engineers but engineers orchestrating disagreement if your models never disagree, you’re probably not pushing hard enough
English
0
0
0
81
Ben Cera
Ben Cera@Bencera·
my AI coding workflow as a solo founder: - opus 4.6 for exploration + planning - codex 5.4 xhigh to stress-test the plan (catches gaps opus missed) - back to opus, which usually complains codex is overengineering lol - few rounds back and forth. codex implements, opus reviews. - ask both: "safe to ship? what's the worst thing that could happen?" opus and codex arguing over my codebase is my entire engineering team. will probably ship this workflow as a Polsia feature at some point.
English
87
32
551
32.1K