26h 19m 9s logged
Vibe Check — Devlog
said last devlog i’d be tackling the UI redesign next. did that. also did about four other things i didn’t plan on. classic me.
two days, and somehow: bug fixes, the redesign, AI integration, a whole landing page, and deployment setup. CSS changes enough to make me question my existence 💔
bugs that were silently ruining everything
found out half the buttons in the app weren’t even styled because the css class they used literally didn’t exist 😭
also discovered template search wasn’t searching anything because the input id was missing.
the search bar looked functional.
it was not.
meow.
fixed a bunch of cursed unicode issues too because apparently some checkmarks had transformed into ancient artifacts from another dimension.
the redesign arc 🥀
this one was planned, but it still spiraled way harder than expected.
changed one thing. then another. then suddenly popup.css was over 700 lines.
goodbye neon cyberpunk.
hello warm golds, soft reds, glass panels, crystal backgrounds, rounded corners and way too many blur effects.
the whole thing feels a lot calmer now.
less “rgb gaming keyboard”
more “expensive thing i can’t afford” :3
ai brain upgrade
probably the biggest change, and definitely not planned.
vibe check can now use Cerebras gpt-oss-120b for prompt enhancement.
ended up building support for:
- local development
- chrome extension mode
- production deployment
all using the same enhancement pipeline.
if ai dies the app automatically falls back to local enhancement so users don’t get hit with a giant error message.
because nobody likes giant error messages.
built a whole landing page because apparently i enjoy suffering
didn’t even plan this one.
but now there’s:
- animated hero section
- glassmorphism everywhere
- feature cards
- demo section
- platform showcase
- responsive layout
and enough floating visual effects to make my gpu slightly concerned.
production stuff nobody will notice
added deployment configs.
serverless functions.
environment variables.
request validation.
api key protection.
cors handling.
all the boring stuff that becomes very exciting when it’s missing.
stats
files modified: basically yes
popup.css: 730 lines
popup.js: 1300+ lines
new files:
- landing page
- serverless ai endpoint
- deployment config
:3
Comments 20
26 hours??? damn you actually programmed it, and made the most ai looking ui for a non ai site, although you could of just had ai do the ui and you did something else…
Dude how did you make that line between two headings
@lowpolyphosphorus pretty bold of u to think that i only made the frontend in the whole 26hrs 🥀 this was my first time making a chrome extension so backend was really something and then had to do cyber stuffs js so no one spams my api etc and i have mentioned the ai use in teh project inbfo u can check it there
@codecraft07 separate sections using this “—”
those are 3 dahes btw… stardance turned it into a em-dash lol
--- idk if this will render as a code block but also 26 hours is alot more than some of them vibecoders making wholeass programs and shipping them with 3 hours logged 🥀
it didn’t render as a code block but the auto em-dash didn’t happen
also the people making ai journals i literally comment on all of them and they just have no defense they don’t respond
wut it auto truns — into em dash for me… waw
lol fr 🥀
@lowpolyphosphorus see my project, Thalamus, 96+ hours logged, doing something I dont think anyone would be doing in this event(training your own ai).
@subhansh Liked yr project.
@lowpolyphosphorus I wouldn’t rely on the “hours” counter to determine if a project was vibe coded, just take a look into their repository, their commits. AI vibe-coded projects are so obvious with massive commits of code, or sometimes loads of over-explaining code in comments, etc. Just a suggestion: Its like fact-checking, try it out its good.
For example: https://github.com/subhansh-dev/vibe-check/commits
only has 4 commits, obviously vibe coded.
Another Example: https://github.com/Cassetu/Novara/graphs/commit-activity
Over 100+ commits spanning several weeks, clearly has human effort
Just look at these comments in here, if you really were coding this, do you really need to add this:
--bg-primary: #06060a; /* Deep black, NOT grey */ --bg-secondary: #0c0c12; /* Slightly lighter */ --bg-tertiary: #12121a; /* Card/panel backgrounds */ --accent-primary: #00E5FF; /* Cyan — primary action */ --accent-secondary: #B388FF; /* Violet — secondary */ --accent-amber: #FFD740; /* Warnings, highlights */ --accent-crimson: #FF1744; /* Errors, danger */ --accent-green: #00E676; /* Success */https://github.com/subhansh-dev/vibe-check/commit/369eaec474da93b50985f4b99b05157dfc3d2d8d
its just colors what possible reason besides ai vibe code would this be here??🥀
@cassetu its not universal for everyone that they need to commit every small change on git when version control is not needed, its my personal preference that i only commit after every update for complex projects only… u can check my other repos :3 so saying that something is vibe coded cause its has less commits is inaccurate and now about the comments about the colors in the code, i have clearly stated in the ai use declaration that i used ai for frontend polishing as stardance allows 30% ai use and ur seeing those comments cause i told claude code to change the colors which i set while coding cause they were not looking gud
@subhansh i put the three dashes into triple backticks but many computers themselves just turn it into an em dash — (not backticks) --- (backticks)
also your entire ui is def ai but like atleast you dont get completely lazy with it like 26 hours is definitely better than the people with only like 2 hours and they try to ship that. @Cassetu commit history isnt the BEST indicator because many programmers such as myself pull the code into VS first and just forget to commit as often
and this comment activity might be pushing your devlog in the homepage 😭
lol fr
@lowpolyphosphorus i mean commit history is just one of many things, code consistency, code to hour percentages (some projects are impossible to make within certain hours even with extremely high wpm or autofill), js look around a bit, thanks. Keep in mind hours can most definetly be faked, although i dont know the TOS for it, its definetly possible (if ur gonna lie about ur project being ai or human, faking hours isnt exactly improbable. Also im curious what part of my ui is ai, because I designed it personally (im a big fan of simple brutalist designs, and if you look at earlier versions u can see how it developed slowly through iterations) Anyways, have a nice day, and “honesty is the best policy”.
Sign in to join the conversation.