tech brook
94 posts

tech brook
@techbrook32
Just a vibe coder building and breaking projects
Katılım Temmuz 2025
231 Takip Edilen9 Takipçiler

Got my 2nd AWS cert.
And the best part of preparation was using my own site for practing mock test.
davco2.netlify.app

English


tech brook retweetledi

Vibe-002
Another Landing page for marketing agency using vercel v0.
Link: grow-pido.vercel.app
@vercel @v0



English
tech brook retweetledi

Trying to clone UI using @GeminiApp
original website: hanzo.framer.website
Just use @GeminiApp to create the UI below 👇




English
tech brook retweetledi

Experimenting with @GeminiApp for UI code generation.
Reference: revento.framer.website
Result below 👇




English

@piyush100x So that's why they call you piyush100x. Doing things at 100x
English

my first in office job salary was 35k as intern, got converted to fulltime within a month with 1L/month - since then every 6months it nearly roughtly doubled and last year my salary reached 1cr(base ofc) sitting in India.
I just did what i loved, went to hackathons, won them, build products (not personal , but for companies) and went to events and talked tech.
English

2025, I won you.
✅ $300k+ total revenue
✅ Crossed 23k followers here
This is huge for a 21 year old from Tamilnadu, India, who grew up and still lives in a village.
Praha@Praha37v
2025, I'm Here!
English

@Motion_Viz Hey ,even I use the same approach and it really saves a lot of time . brainstorming with claud for 30-40 min to have a clear flowchart/plan really save hours while coding or vibe coding.
English

the biggest mistake i see people make when building AI apps?
they jump straight into development.
no system design. no architecture. no flowchart. just vibes and code. then they wonder why their app feels disjointed...
why? users drop off after 30 seconds... why the "AI magic" doesn't land.
here's what i've learned building 20+ AI projects in the last few months:
the flow matters more than the features.
every app follows the same skeleton:
onboarding → core experience → end goal
but most builders obsess over the middle (the AI part) and completely ignore the entry and exit points.
think about it...
>if your onboarding is confusing, users never reach the AI
>if your end goal is unclear, users don't know what "success" looks like
>if the middle is bloated, users get lost before they get value
here's how i approach it now:
step 1: define the end goal first what's the ONE thing users should walk away with? screenshot? insight? generated asset? start there.
step 2: reverse-engineer the onboarding what's the minimum info you need to deliver that end goal? collect only that. nothing else.
step 3: map the flow visually before writing a single line of code i use a simple diagram: onboarding → [2-3 core steps] → end goal. if it doesn't fit on one screen, it's too complex.
step 4: build the skeleton first navigation, state management, data flow. the AI integration comes LAST, not first.
the apps that feel magical aren't doing more AI — they're doing better architecture.
your users don't care about your model. they care about getting from A to B without friction.
next time you start a project, spend 30 minutes on the flowchart before you touch the code.
you'll save yourself 30 hours of refactoring later.
English

@Motion_Viz @The_Sein_ It look good. I use google AI studio right now. But definitely try mobbin and @v_computer.
Here is what I have built
- davco2.netlify.app
- neumorui.netlify.app
English

@The_Sein_ websites i build for people :
apply.agentintegrator.io - @ damianplayer (X)
pjc-media.com - @ pjc media (Insta)
and 2 more under work.
- all in last 2 months alone.
Shifting to APP dev for next projects. will update later for sure.
English

how I will be building apps in 2026:
most people: idea → figma → code → debug → ship (3 months)
me: idea → Claude Code → Mobbin → Vibecode → ship (3 days)
the workflow:
STEP 1 — CLAUDE CODE (Planning)
→ describe your idea in plain english
→ Claude writes full PRD: user flows, features, edge cases
→ outputs technical architecture + component breakdown
→ no guessing. no "I'll figure it out later"
STEP 2 — MOBBIN (UI References)
→ search real apps, not dribbble concepts
→ find patterns that actually work in production
→ screenshot flows: onboarding, dashboard, settings
→ real apps > designer fantasy
STEP 3 — VIBECODE (Build)
→ feed PRD + Mobbin references
→ @v_computer generates full frontend + backend
→ iterate in natural language
→ ship same day
the secret: planning with Claude Code Opus 4.5 first.
90% of build problems come from bad specs.
Claude eliminates ambiguity before you write a single line.
like + reply "WORKFLOW" for the full breakdown + my Claude prompts.
(must be following for DM)

English

@goyalshaliniuk Half way through the video. And his way of explaining things are just amazing

English

Want to learn AI/ML but don’t know where to start?
These YouTube channels will guide you step by step.
Whether you're building Agentic AI workflows or just starting with Python, this llist covers everything:
1. Agentic AI & ChatGPT
Watch creators like Krish Naik and Freecodecamp for hands-on projects with GPT, LLMs, and automation tools.
2. Machine Learning & Deep Learning
Explore channels like StatQuest, Yannic Kilcher, and DeepLearningAI for algorithm intuition and implementation walkthroughs.
3. Python & Data Science
From Corey Schafer to Ken Jee, these channels help you master the foundations of Python, analytics, and deployment.
4. Math for AI
Need help with the math behind the models? Start with 3Blue1Brown, Khan Academy, and PatrickJMT.
5. Big Data & Data Engineering
Follow Alex The Analyst, edureka!, and Data Engineering to scale your AI pipelines and manage large datasets.
6. Tools, Productivity & AI Assistants
Stay up to date with Ansh Mehra, Jeff Su, Skill Leap AI, and Howtoai to explore ChatGPT hacks, AI agents, and productivity automation.
Start with 1–2 channels that match your current level and niche. Be consistent, practice what you watch, and explore new tools as you grow.

English
tech brook retweetledi
tech brook retweetledi

If I knew Medium pays this much for writing just 32 articles.
I would've started way earlier.
P.S. but my Medium account got suspended 😭

Kalash@amikalash
If I knew Medium pays this much for writing just 24 articles. I would've started way earlier.
English

@Sidhart64113485 @piyushgarg_dev @kubernetesio His explanations are too good. Currently watching his "How video streaming work breakdown" to build a video streaming app
English

Another master-level project idea just clicked
Watched a system design breakdown of Kubernetes by Piyush Garg, and it completely changed how I think about distributed systems.
Instead of just using Kubernetes, I started asking:
“How does this actually work under the hood?”
Key takeaways from Kubernetes architecture:
>Control Plane acts as the brain
->API Server is the single source of truth
->Scheduler decides pod placement
->Controller Manager maintains desired state
->etcd stores cluster state reliably
>Kubernetes workflow (simplified):
->User submits desired state (YAML)
->API Server validates & stores it in etcd
->Scheduler assigns pods to nodes
->Kubelet runs containers on nodes
->Controllers continuously reconcile failures
Huge thanks to @piyushgarg_dev for the clarity and inspiration 🙌
Time for deep R&D and hands-on learning.
Building systems > just using tools.
#Kubernetes #SystemDesign #DistributedSystems
#DevOps #CloudNative #BackendEngineering
#BuildInPublic #LearningByBuilding

English













