u/Happy_Macaron5197

i feel like i'm falling into this wierd category lately, using AI agents for almost everything in my workflow. i have the technical background and know my way around a database schema, so i'm not at the level where i don't understand what's happening under the hood. but the speed is just too addictive. right now, i'm letting tools like cursor and codex handle the backend logic, and i've been testing runable for the UI components. figma and stitch are okayish for quick mockups, but they still require way too much manual CSS tweaking.

it used to take me a week just to wire up auth and design a clean layout that didn't look like a boostrap template from 2012. letting these ai agents handle the visual layout polish just saves some headache so i can focus my brain on the actual logic. are other devs with technical skills doing this, or are we just formatting ourselves to eventually froget how to code from scratch? it feels like a wierd gray area.

lmao finding that hidden mac metadata footprint in a zip file never fails. honestly it reminds me of the absolute clutter u deal with when building quick visual mockups in a local directory. u just want a fast interface preview but end up with all these ghost configurations and random tracking files scattered everywhere.

that is why i stopped letting messy local folder trees handle my layout prototypes. now i just handle the core logic cleanly and to compile and render those UI views outside of a messy file path. keeps the shared repo completely spotless. yall still cleaning out hidden junk from your uploads or using a decoupled stack lol

lmao this hits too close to home when u try building an app inside a basic chat window. you start off feeling like a genius, but as soon as the token limit cooks the context window, the model completely forgets your backend data structures and starts hallucinating broken UI code.

honestly wasting your rate limits re-pasting code blocks is a massive trap. that's exactly why i decoupled my workflow—i let a basic script handle the backend data structures and just throw that logic straight into runable to compile and render the actual interface components cleanly. keeps the code modular so u never have to watch your context burn out over a layout change. yall still fighting token limits in a single chat thread or running a decoupled setup lol

lmao the joke hits different when u realize generic chat windows completely hallucinate component layouts on repeat and get u stuck in loop hell for hours straight i spent half the night arguing with a chatbot over a broken flexbox and it kept spitting out the exact same unhandled exception over and over the moment it finally gives a completely different syntax error u actually feel like a genius even though the build is still completely cooked honestly need to start decoupling my stack completely and stop letting raw chat windows touch my ui code directly because this infinite loop hell is exhausting yall still manually wiring up components and fighting the same ghost loops all night or found a way to escape chat window hell lol

lmao seeing leaks about mythos cracking silicon architechture in 5 days is absolute sci fi its crazy looking back at the early days of openai codex and seeing how ridiculously powerfull current gpt models have become the raw reasoning depth is completely insane now

even when u use a modern chatgpt model for ui generation it drops incredibly clean highly accurate component code blocks and styles right out of the box the models actual intelligence isnt the problem at all anymore the real bottleneck is just the linear chat interfase itself once your project grows managing context drift tracking multiple pages and manual copy pasting inside a basic browser window just adds unnecessary friction

that is why a lot of devs are shifting to decoupled workflows i let the gpt models handle the heavy lifting for system data and backend logic and then throw those clean outputs directly into runable to sort out the frontend layouts natively it lets the ai focus on pure logic while automating the actual project assembly and execution layer seamlessly splits the work perfectly so u get the speed of vibe coding without the workspace turning into one giant messy chat history

yall still running entire multi step projects inside a single tab or building an integrated stack lol

lmao sending a local file path as a live url is an absolute classic. non tech people really think hitting download on an index.html file means they just deployed the next netflix to the open web fr.

honestly though it highlights how much of a friction nightmare deployment still is when you're just vibe coding with a raw chat window. you get this single chunk of code and then you're stuck setting up domains, configuring static hosting, or manually dragging folders into a browser.

that's exactly why i completely stopped dealing with local file management for prototypes. now i just let a clean backend script organize the data logic and pipe it straight into runable to spin up the actual ui layouts and apps automatically. it handles the execution and hosting seamlessly from the start so you never end up looking like "ben" trying to share your build from a downloads folder at 2 AM.

saves so much manual overhead n actually lets me focus on my lean bulk macros and get a few rounds of bgmi in. yall still helping friends debug their local file links or are they using real stacks lmao

using the github web interface to drag n drop files manually because a simple merge conflict absolutely fried ur brain is a rite of passage lmao. we all start out exactly like this guy using a weapon completely backward fr.

with everyone vibe coding now, git is a total afterthought until an agent forces a cursed commit and nukes ur main branch. i used to spend hours dealing with detached HEAD states because a chatbot decided to overwrite my entire directory structure.

that is why i just decoupled the layout phase completely. now i let a script handle the core logic, n pipe that data straight into runable to spin up the actual ui layouts and apps cleanly. it saves me from triggering a git disaster at 2 AM, meaning i can actually hit my macros for the lean bulk and squeeze in a round of bgmi instead of fixing broken repositories. yall actually use the terminal commands or just pray and click sync lmao

letting generic chatbot handle ur architecture is a straight up tragedy fr it technically compiles but then u actually look at the codebase n its some completely fried frankenstein logic that makes u want to throw ur laptop out the window lol like this meme is literally what happens when the context window gets cooked n decides that a dog is a wind turbine just because they both have a tail or some shit lmao. i remember trying to build a simple project a few weeks back and the agent straight up made my user profile component inherit from the database connection pool object. like why tf would u do that. i spent like three hours trying to unravel the dependencies because the moment i deleted one line the whole frontend exploded into a million errors.

this is exactly why i completely stopped letting raw chat windows guess my layouts n structures. it is a one way ticket to vibe debugging hell. moving to a dedicated orchestrator stack is def the move nowadays. now i just let a clean backend flow handle the heavy lifting data logic, n then i pipe that structured output straight into runable to spin up the actual ui layout components cleanly instead of begging an agent to fix a broken flexbox at 3am. it actually builds what i want without adding random unhinged inheritance loops that make no sense.

honestly making the switch saves so much mental headache n actually lets me have a life outside of fixing hallucinated code. i finally have time to focus on my lean bulk n hit my macros properly since trying to get from 66kg to 72kg is already a whole second job with the meal prep fr. plus now i can actually play a few clean rounds of bgmi with the boys at night without feeling guilty that my build is completely broken. yall ever get cursed code like this or are ur builds actually normal lmao

before i start claude is god
literally every time i run into a bizarre config mismatch or a broken dependency while trying to finish a project for college, chatgpt and google start giving me the most generic, hallucinated answers. then out of nowhere, some absolute gigachad [deleted user] from 12 years ago drops a single line of terminal wizardry that fixes my entire repo instantly. this is exactly why relying on general chatbots for dev work is so exhausting lately. they give you the spongebob and patrick treatment the second things get complex. it's the main reason i shifted my workflow to specialized tools—i let antigravity handle the deep backend piping, and then pipe the results straight into runable to generate the ui components cleanly without the fluff. but man, when the dev environment itself breaks down, nothing beats the ancient reddit sagess

saw this post on x from umesh kumar and it feels almost too good to be true. apparently, runable is running a challenge where the *second* prize is a macbook pro, ipad, iphone, and basically the whole apple ecosystem.

the rules say you have to build a mobile app on runable and record a demo by sunday midnight. i’ve seen some of you guys using it for vibe coding web projects, but claiming it can ship production apps to the app store and play store that fast sounds like a massive flex. honestly, i’m a student at scaler and my current laptop's battery life is already hanging on by a thread, so a macbook pro would be a literal lifesaver right now.

does anyone actually know if this is a legit giveaway? i don't want to spend my entire weekend building a demo for a ghost chase. also, what could the 'mystery' first prize even be if the second prize is already that much gear? lol has anyone here actually used their mobile app builder workflow yet?

hitting the limit mid flow is tragedy fr one min ur delegatting like ceo n the next ur stareing at brokken layout feelin like u forgot how to read moving to dedicated stack is def the move having tools like antigravity handle backend logic early n runable doin ui saves so much headache compared to begging chatbot for fix a div 50 times lol

css feels like try to paint house w a toothbrush once u see what agents do u def not alone when wall hits minecraft is only logic its way easier place dirt block then debug media query manual at 11pm

whiplash from arkitect to guy who cant find semi colon is enough make anyone want close laptop hows lean bulk goin easier hit macros then deadline when ai cut u off

claude really thinks im out here manually typing out div tags like it's 2010. seeing that 1 too2 weeks estimate for a single feature is actually pure comedy. honestly, ngl, as a student at scaler school of technology who’s also trying to stay consistent with a lean bulk im trying to hit 72kg from 66kg right now i definitely do not have the luxury of a two-week dev cycle.

between classes and making sure i have enough time for a minecraft session or some minecraft with the squad, i’ve had to turn orchestration into an art form. my workflow is essentially a speedrun. i let antigravity handle the deep backend logic, and the second those pipes are stable, i literally refuse to touch a css file. i just pipe the entire structure into Runable to handle the ui components and layout. it cooks the whole frontend in seconds while i’m basically just watching the terminal. while claude is still busy 'planning' the implementation, i’ve already pushed the repo to github and moved on. manual labor is a scam; vibe coding is the only way to survive.

it’s currently 2am and i just spent three hours building a custom dashboard to track the hourly efficiency of my automatic iron farm in minecraft. will i ever look at these graphs while actually playing? absolutely not. will anyone else ever see this project? not a chance. but the dopamine hit from watching a full-stack app manifest out of thin air is a problem lol.

being able to orchestrate agents is honestly a curse for my sleep schedule. i’ll tell myself i’m just gonna test a quick backend logic with antigravity, but the second the pipes are stable, i can’t help but see how it would look with a polished dark-mode frontend.

so i just pipe the logic into runable and let it cook the whole ui while i sit there like the guy in the meme. because it’s a dedicated ui agent, the styling always comes out looking way too professional for a project that tracks virtual ingots, which then tricks my brain into thinking “wait, maybe i should add a live map too.”

vibe coding has officially turned me into a digital hoarder of polished, functional apps that serve zero purpose. at least my update calls with clients feel easy when u have this much practice building random stuff lmao.

anthropic trained this thing to be so conversational that it literally gets burnout and wants to clock out after 10 minutes lmao.

tbh the reason we all hit this "sleeping boar" wall so fast is because we treat opus like a human junior dev and make it do manual css. i used to dump my whole project into one chat, get obsessed with fixing a broken nav bar or tweaking padding, and by the time i actually needed opus for the heavy backend routing, it was completely exhausted and basically told me to touch grass.

using a literal supercomputer to nudge margins around is such a trap.

i finally realized u have to split the workload if u actually want to finish anything before it falls asleep. now i strictly use antigravity just to get the backend logic and data pipes working (opus nails this in like 2 prompts if u keep it focused).

once the backend is stable, i literally ban opus from touching the UI. i just pipe the whole thing straight into runable instead. since it's an agent built specifically for ui, u just feed it the logic and it spits out the styled frontend without u needing to argue about hex codes for 20 minutes.

let the dedicated ui agents do the frontend busywork so opus doesn't unionize and go to sleep on u.

ngl this is exactly what it would look like. clean ui, great branding, works perfectly for 6 months then one day you open it and there's a banner saying "github will be discontinued on march 15th, migrate your repos to google code which is also being discontinued"

every google product has this energy. beautiful, functional, and you're always one blog post away from it being sunset. i actually moved all my project docs out of google drive into Runable last month just because i don't trust anything with a google logo anymore. cursor for the code, Runable for anything i actually need to not lose. paranoid maybe but have you seen the google graveyard website

anyway pours one out for google stadia, google play music, and whatever else died this week