Vivaan

today i worked on the parser. got basic syntax rules in place.
each statement is like a command — built around simple keywords.

added support for:

variable declaration:
horcrux harry = 7
interpreter reads line-by-line and logs token positions for debugging.
built a small tokenizer that handles keywords, identifiers, literals, and operators.

Missed devlog part 2, after some coding enhancements, i got onto make the hero or top section i dont know what it's called, messed with some css, but overall, it's pretty good, might add some animations like flicker or something so it gives haunted website vibes

styles the ui a more, it looks better now, experimented with the palette, and aligned things a bit, might use tailwind too

Was just reading the harry potter series, and after much votes on my last esolang project, am presenting: Avada-kedavra, a new harry potter inspired esolang!!!

Now i've had some experience with esolangs, so am pretty sure its a good oppurtunity to brushen up my skills, so here we go, started writing the code like a good boy, defined the logic started jotting the grammar, thought of some cool names and just sketched out it overall, from next devlog, i'll be implementing more features

wasn’t planning to build this.
just typed “rims” into a folder and hit enter.

started setting up the html boilerplate
tailwind took 20 minutes to behave
kept changing the font back and forth between inter and space grotesk.
landed on inter. not that deep.

built the hero section.
said “hi. this is rims.”
sat back for a second. felt right.

made a glowing button.
it scrolls. does nothing fancy.
still spent 30 mins tweaking hover effect
even though nobody’s gonna hover for that long. whatever.

made the first section called “what’s inside”
wrote five bullet points. half of them are jokes
decided not to make them links yet
cuz i haven’t built anything they’d link to lol

thought about the site like a toy box
not a dashboard. not a product. just... digital junk drawer
and that’s fine

kept spacing things manually even though tailwind could do it better
might fix that later or never

called it for now
rims exists
hour 3 ends with a page that scrolls
but doesn’t go anywhere yet
and that’s kinda poetic i think

first, made the whole failure card system dynamic — added a list in js with different failures, each one has a title, a short line about what went wrong, and a longer story, all of that gets rendered through js so i don’t have to keep writing html by hand

added a basic toggle to show/hide full text when the user clicks “read more”, pretty simple, no animations, just switches between none and block

also added tags to each failure, like “frontend”, “backend”, “workflow”, so it’s easier to group them later if i want, right now they’re just colored spans showing up under the title

started working on a separate section called “reasons you should not hire me”, it’s just a list of short bullet points like “writes commit messages like ‘fix things’”, or “tests in production”, that kinda stuff

put that in its own div, will maybe make it toggle-able later

in css, made everything align a bit better using flexbox, cleaned up some padding and spacing, still no fonts or themes, just basic black text on white with grey boxes

next i might add a fake filter system for categories, not actual search, just buttons that hide/show cards by tag

also thinking of adding a static section with my worst-ever project screenshots, like visual proof of failure, still deciding on layout

that’s it for now, moving fast now to cover missed hours
also added filters

made the html skeleton, header, main, footer, main’s got a section where all the “fail cards” gonna live, each card’s like, title, short text, and a button that’s like “read more”, in css, did like, basic layout, nothing aesthetic, just boxes, some padding, tried to make it ugly on purpose but not too ugly yk, used monospace cuz it looks kinda broken by default and then js time, kept it stupid simple, made a list of fake fails like accidentally deleted prod or committed node_modules n stuff, rendered them with js using forEach, each card has title, short text, and a button that opens the full fail

dated: 24/07/25, i was to talk to you guys about what's up with my project and my devlogs, but due to a glitch, i lost 25+ hours, but i talked to support and got it back
so am gonna post all my saved devlogs

I was working on my portfolio project, but i thought, hey that's too common tho isn't it, so i started with this: my anti-portfolio, and as the name suggests it tells the user or the employer, about our failures and why should they not hire us. Sorry for the devlog delays, but dont worry i will compensate for all the hours, for the next 2-3 devlogs, the time span will be of 5 mins(as i'll be update y'all about the missed devlogs), so stay tuned. I will be doing this app in only html and css and js, nothing else.

refactored the sync function — it no longer blindly sends msgs to firebase, now it checks for failures and logs them properly. planning to add retry count tracking soon.

added proper message status states: queued, sending, sent, failed. updated the UI to show these clearly so things don’t feel invisible anymore.

built a useMessageQueue hook to manage local storage — handles read/write/update/delete. added cleanup logic too, so sent msgs don’t pile up forever in asyncstorage.

polished the queue screen — added fade-in animations with reanimated, cleaned up the message cards with color-coded status labels + timestamps.

kinda a messy 4hr stretch but productive fr. started off trying to fix a weird crash when composing a msg offline — turns out asyncstorage was saving fine, but nothing was reading it back. so I wrote a hook to fetch + reverse-sort msgs by timestamp

it’s still very barebones UI-wise, just a list of pending msgs and their status (queued/scheduled)

built a first-draft sync function — checks NetInfo + loops thru local msgs and pushes them to firebase. no retry logic yet, plus ran into some problems

okay so these 4 hours were kinda all over the place ngl. i started w/ trying to make the compose screen not crash when offline and finally got asyncstorage working properly. i was saving msgs before but they weren’t showing up anywhere sooo made a queue screen where it pulls all that local data + just lists it out in reverse timestamp, still basic and will be working on it, wrote a lil sync function that pushes pending msgs to firebase. didn’t add retry logic yet, but planning to do so, and spent the rest of the time on css!

Spent about three hours working on local message logic. I updated the way messages are stored — they now include a timestamp, a delivery delay option, and a message type like ping, text, or reminder. It’s not complex, but it makes the whole thing feel more real and structured.

I also worked on the queue screen. It now actually loads saved messages from storage and displays them properly. Still using basic styling, nothing polished yet, but it's functional. You can now send a message from the compose screen and see it appear in the queue.

Started working on the sync trigger — right now it just logs when the internet comes back using NetInfo. No actual Firebase upload yet, but the detection works, and that’s one step closer.

what i did today:

finally made the repo (after 15 mins deciding if “deadzone” is edgy or cool)

created the project with npx create-expo-app deadzone — got Expo + React Native rolling

setup the basic folder structure like a good lil dev: screens/, components/, services/

made a super simple Home screen that just says "Deadzone 📡
added NetInfo to check if I’m online/offline
logged everything on HackaTime

yes i use windows (sry)

YES IT'S DONE!! FINALLY, after adding the last sections, and polishing the content of the your impact page more, we are done, now, let me ship the project, i asked gpt for recommendations to add emojis in

Added multiple sections, copied styles so it want very tough, but alas to avoid monotonous tone, i had kinda had to tweak with the css a lot, but it's ok, it's alr, i'll add more, stay tuned.

setted up the file structure, brainstormed a bit about the ui, going with the signature apple classy look, created a basic website, did not add any feature till now, but wrote a lot of css.
wrote some js functions in script.js, nothing crazy, just setting up the base for live preview.
also added font imports and tested out a few typography combos

Heyy!! Setted up the file structure, doing it in only html and css, created a basic portfolio website, listed my projects with ul and wrote very minute css, so its just a skeleton now, but we will be working on that lol, found my pics, and is going to start adding the pics instead of placeholder photos

Formatted the code, created the documentations and readme, and did some final touches on the ui, polished it with a minimalist black theme.

next, part of the devlogs and the hours, i created the esolang and also created a web interpreter such that you guys can play with it without installing the boring cli tools and stuff like that, excited for you guys to test this, lemme just add documentations and create the readme, cya guys later!

setted up the file structure, brainstormed a bit about the ui, going with the signature apple classy look, created a basic website, did not add any feature till now, but wrote a lot of css

part of the 7 hour devlog) next i created a your impact page for the navbar button that had been there till the highs and lows of our journey with the broken code.(yes my sense of humour is as broken as my code), but together with the power of friendship we shall persist(credits: tommyinit), here's the picture, and the 7 hour phase is coming to the end, next devlog shall be including documentations, readmes and final touches!

next i added another section with a water usage calculator, and please as much as it looks like i did this in 5 mins, i did it over the 7 hours devlog, i forgot to log the time cuz of my broken code, and now am compensating, created a script.js for the calculator logic, and designed the html and styles with css

Next devlog, part of the previous one (7hours)

i added 5 new section which took me like an hour for styling and such, css does gets long!

planning to make a water calculator next!

Sorry for the lasped devlogs, dw i'll update it, but hear me out first, i got lost!! (in my own code {rightfully so}), i haven't coded in python much and although it was fairly gentle project to begin with, i never coded this much at one stretch, but i'll update, i'll do, lemme start

1. I started defining logics, and started coding the interpreter, atleast i had the basics down, i saw other people do this, so why not and off i went, little did i know, how tiresome it was, i kept on running into errors, until finally i broke my code for good, (i used gpt to ask it what might go wrong) but later fixed it....

Am sorry for the lost devlogs, i spent so much time on fixing broken code, that i lost count of my hours, but i'd give a detailed info on what i have done in the 7 hours!

            first) I noticed that my projec's ui was close to that of climate iq (my other shipped project) and i did not want it to be similar in any way, so off i went, i searched some uis on a website that has cool ui's of many websites, and selected a professional polished ui (shoutout to apple ), instead of going up with the trendy cartoonish look

so deleted and modified code, my formatting of the divs were extremely messy and i had to split code everytime, or else i would forget my class names (apple, bananass, monkey) yeah ik i should have named them a little more precisely, but hey where's the fun then!

So that's where it took a little time, i was also busy with twist, grup and hackmate, so sorry for the delay!

                   i'll give you guys the lost devlog in the next one

                the formatting's off in Som so i'll js add spaces(a lot of it)

i hope it works

Yo, just finished reading the pj series and came across ysws-twist, so i though why not, lets get into esolang, read the requirements, setted up the file structure, researched a bit on how do people create it(its ez) so started up, coded a bit js, though of creating a web interpreter too, so coded a smol index.html as well, and yeah that's about it, like 1/3rd the work is done...cya later

Changed the name of the project from DropCount to Drenched as it sounds way cooler this way, changed the navbar to dynamic, and added 2 new sections, started working on the calculator(js) that will help the users calculate their water use, ran into broken css code this afternoon, so sat down to fix it, wrote the readme, so that's like 15 mins, but yeah, that's about it.

It does not allow me to upload more than one photo, and video seem to breakdown, so yeah ig we are stuck with one section photo at a time.

Can't rush greatness huh? haha lets goo!!

Added new sections, mess up with colors, going with apple like classylook, not white bg as sm text are not quite visible that way, so went with gray, tweaked the texts color, stopped using ids and figcaption(yes it took sm time, but i learned from freecodecamp) and went with div, i get quite confused with # and . selctors, but i manage at the end of the day... Have a look at the photos of the new sections i made, (not so real data, js sm clever maths), (it does not allow me to post more than 1 photos, so next photo in another devlog)

Just updated the readme a bit, and sm broken code in the navbar

changed the ui code, shifting my focus to the ui as it's a static site, found some cool colors on colorpallete, created a basic frontend with some ideas from my previous project climate iq, searched some apis to find accurate water usage data but was unable to find a completely free one....but yeah, in terms of coding, i coded it in js index.html and masters.css

setted up the file strucutre, collected some mock data, created a template website andd found some cool water photos(yes they exist haha), created the ui....

Final stretch, it is done, ready for shipping, hope y'all like it, had to manage both exams and this but huff i did it slow but i did it, the code actually broke last night so had to fix it again, wasn't able to use any ai as my copilot ran out of credits last week, but we did it, changed the color scheme a little, wrote pretty simple js for calculator logic and pretty much more minor improvements.

FINAL stretch. Last minute ui additions, a simple scroller bar, and a new section which i spent a lot of the time editing and talking with chatgpt on how's what (am transparent this way💀🤙), will create a new page to show how to lower your carbon footprint and will also add a mini game I guess becuz it might attract votes :)

Created a new indexnew.html to test out new styles. used tailwinds css heavily in it, as i like the new styles more as i created div for everything it was pretty easy to style, compared to the index.html where i gave ids to differnt h1s and buttons, but that's alr.

fixed the broken css, started using tailwind too in it as its much easier tbh, started replacing big css blocks with tailwind for easy access, renamed classes to match its purpose, good job overall

Just tried to figure out the math, shortened some code, add some more animations and yeah, am pretty slow to code ig

Nothing much, just added tables and a new category that i spent most of the time styling on

Updated the ui completely, add navbars, tables and counter using mock data, founded colors, and other stuff...

changed the ui code, added new colours, added the co2 emission of popular apps,
and started writing the math for the code

setted up the file strucutre, gathered apis and mock data, created a basic website, created the ui....

Day 1: CarbonIQ - First Seeds Planted
Today was day one for CarbonIQ, and it's already feeling like a solid start. I got the project initialized with Next.js (TypeScript), which is my go-to for a robust frontend, and integrated Tailwind CSS without a hitch. Clean styling from the get-go is always a win.

I immediately set up a logical folder structure: components/, sections/, data/, and other essentials. This disciplined approach will definitely help with scalability down the line.

The first visual piece is a Hero section that's high-contrast and centered, welcoming users with bold text about tracking India's internet carbon emissions. Below that, I added placeholder category tabs like Streaming and AI—the idea is to make these interactive for live impact tracking.

Finally, I created a static multipliers.json file with some fake data (e.g., 0.2g CO₂ per Google search). This will be key for future calculations. No backend yet, but laying this foundation feels like planting the first seed for something big. 🌱