NoCodeCarlos

📱Building apps

[NoCodeCarlos @NoCodeCarlos]

I built an iOS game

Can you reach Capy reach the moon and adspace? Yes adspace
https://t.co/9R9wY7U3Xo

[NoCodeCarlos @NoCodeCarlos]

So whats the difference between @paper and @pencildev ?

And which one should I tried first with Claude Code

[NoCodeCarlos @NoCodeCarlos]

@JJEnglert I missed today's event, will there be a recording?

[NoCodeCarlos @NoCodeCarlos]

Claude Code:

✅ Creates a whole game with altitude, parallax effect, sounds, animations from a string of prompts

❌ Changes the font color to white after several prompts, CSS ingestion, screenshots, comparisons etc

[NoCodeCarlos @NoCodeCarlos]

@CiprianiRanieri https://t.co/mv29AxgGS0

[NoCodeCarlos @NoCodeCarlos]

@CiprianiRanieri hey dude!

[NoCodeCarlos @NoCodeCarlos]

@CiprianiRanieri Im building Mustard Seed, an app for Catholic parents to share the faith with their kids.

https://t.co/mv29AxgGS0

[NoCodeCarlos @NoCodeCarlos]

@eve_silb @CiprianiRanieri Hi Eve I tried using your too but my payment got declined and there wasnt any info from the bank to allow it or anything it just got denied

[NoCodeCarlos @NoCodeCarlos]

@JJEnglert Not even close to a video producer but I signed up for the webinar

[NoCodeCarlos @NoCodeCarlos]

And we have sound 🔈 Spent the last few early mornings building sound assets for Launch the Capy.

Lo-fi jazz that speeds up as you climb made with @suno

Rubber band and coin effects
made with @elevenlabs

Stitched together by Claude Code in seconds.

[NoCodeCarlos @NoCodeCarlos]

@thisiskp_ @levelsio 🙋‍♂️ Im taking my shots

[NoCodeCarlos @NoCodeCarlos]

I know I had a good weekend when I can squeeze in a labor of love. Using Claude Code, I'm building Launch the Capy, a game where you help a Capybara reach the moon.

In this session, I experimented with a parallax effect and rendering the game at 60fps; it looks so much better.

[NoCodeCarlos @NoCodeCarlos]

@victor_bigfield An iOS game

[NoCodeCarlos @NoCodeCarlos]

@eve_silb @pmitu Oh wow I actually need this

[NoCodeCarlos @NoCodeCarlos]

@designertom Power Ups that you can purchase at the "garage" and "sounds" are coming soon.

[NoCodeCarlos @NoCodeCarlos]

hey @designertom — here's Launch the Capy

A Capybara dreaming of reaching the moon. Assets from GPT, Canva & Nano Banana, merged in Figma, built with Claude Code + Xcode.

Aiming for a fully working iOS game

[Ryo Lu @ryolu_]

software is still about thinking

software has always been about taking ambiguous human needs and crystallizing them into precise, interlocking systems. the craft is in the breakdown: which abstractions to create, where boundaries should live, how pieces communicate.

coding with ai today creates a new trap: the illusion of speed without structure. you can generate code fast, but without clear system architecture – the real boundaries, the actual invariants, the core abstractions – you end up with a pile that works until it doesn't. it's slop because there's no coherent mental model underneath.

ai doesn't replace systems thinking – it amplifies the cost of not doing it. if you don't know what you want structurally, ai fills gaps with whatever pattern it's seen most. you get generic solutions to specific problems. coupled code where you needed clean boundaries. three different ways of doing the same thing because you never specified the one way.

as Cursor handles longer tasks, the gap between "vaguely right direction" and "precisely understood system" compounds exponentially. when agents execute 100 steps instead of 10, your role becomes more important, not less.

the skill shifts from "writing every line" to "holding the system in your head and communicating its essence":

- define boundaries – what are the core abstractions? what should this component know? where does state live?
- specify invariants – what must always be true? what are the constants and defaults that make the system work?
- guide decomposition – how should this break down? what's the natural structure? what's stable vs likely to change?
- maintain coherence – as ai generates more code, you ensure it fits the mental model, follows patterns, respects boundaries.

this is what great architects and designers do: they don't write every line, but they hold the system design and guide toward coherence. agents are just very fast, very literal team members.

the danger is skipping the thinking because ai makes it feel optional. people prompt their way into codebases they don't understand. can't debug because they never designed it. can't extend because there's no structure, just accumulated features.

people who think deeply about systems can now move 100x faster. you spend time on the hard problem – understanding what you're building and why – and ai handles mechanical translation. you're not bogged down in syntax, so you stay in the architectural layer longer.

the future isn't "ai replaces programmers" or "everyone can code now." it's "people who think clearly about systems build incredibly fast, and people who don't generate slop at scale."

the skill becomes: holding complexity, breaking it down cleanly, communicating structure precisely. less syntax, more systems. less implementation, more architecture. less writing code, more designing coherence.

humans are great at seeing patterns, understanding tradeoffs, making judgment calls about how things should fit together.

ai can't save you from unclear thinking – it just makes unclear thinking run faster.

[NoCodeCarlos @NoCodeCarlos]

@DannPetty Check out @raydian_dev !

[NoCodeCarlos @NoCodeCarlos]

@gregoryjohn Wow canvas on product?

[Gregory John @gregoryjohn]

Vibe Coding 2.0?

Zero technical ability needed.