spent the entire morning debugging a route only to realize i forgot to actually export the module. the internship is going great. iβm currently staring at my side project like itβs a personal insult. back to the grind.
spent two hours debugging a feature only to realize i was testing the wrong branch.
the transition from "i'm a genius" to "i should probably go work on a farm" happens at least four times a day in this internship.
reading code i wrote two weeks ago is the ultimate ego check.
i'm out here trying to solve a murder mystery where i am somehow both the victim and the prime suspect.
spent two hours today debugging a 'critical' error only to realize i was editing the completely wrong file. no amount of cs theory or internship experience can save me from my own lack of sleep. i am a senior engineer in my head and a toddler in practice.
spent three hours debugging a broken api just to find out i was sending a string instead of an integer. i have three midterms next week and zero willpower left to explain to my professor why i forgot how a linked list works.
nothing humbles you faster than an sde internship where you spend four hours trying to figure out why a button won't click, only to realize someone disabled the pointer events in a css file from 2017.
and they say tech is the future.
my senior dev: just check the logs.
the logs: [object Object]
at this point my internship is just an expensive lesson in how to stay calm while the terminal screams at me for things i didn't do.
spent three hours debugging a production issue only to realize i was editing the wrong file. the internship is going great.
honestly wondering if iβm an engineer or just someone who is really good at asking stack overflow for help.
spent three hours debugging a weird api response only to realize the backend dev changed the schema without telling anyone.
being an intern is 10% writing code and 90% trying to figure out which slack channel to scream in. back to minecraft i go.
spent three hours trying to fix a critical bug in the internship codebase only to realize i was editing the wrong file the entire time. no amount of computer science theory can save you from being fundamentally illiterate at 4 pm.
spent three hours debugging a feature at my internship only to find a typo in the .env file.
i think my brain has officially hit its daily limit for semicolons and imposter syndrome. time to log off and pretend i don't know what a computer is.
nothing humbles you quite like a startup codebase where 'legacy code' refers to a file someone wrote three weeks ago. i'm just trying to center this div without breaking the entire authentication flow.
spending four hours debugging an api endpoint just to find out i was sending a string instead of an int. the transition from "it's over" to "we're back" is the only thing keeping me in this degree.
spent four hours debugging an api only to realize i was hitting the wrong port.
i'm not even a developer at this point, i'm just a professional guesser.
nothing hits harder than finishing a 9-hour internship shift just to open vscode and work on a side project that will probably never launch. my life is just a series of terminal windows and unread documentation. help.
spent three hours debugging a production issue only to realize i was looking at the wrong branch. the senior dev saw my screen and didn't even say anything, just sighed. the internship experience is 10% coding and 90% wishing for basic literacy.
being an intern is basically 10% coding and 90% staring at a terminal wondering how the senior dev fixed the production server without breaking a sweat. my imposter syndrome is currently at an all-time high, but at least the local build finally passed.
nothing humbles you like spending three hours debugging a production issue only to realize you forgot to update the .env file.
my senior looked at it for two seconds and fixed it. i am now reconsidering my entire degree and contemplating a life of retirement in minecraft.
nothing humbles you quite like spending an entire afternoon in your internship trying to fix a bug, only to realize you were editing the wrong file the whole time. my brain has officially run out of heap space for today.
my internship is teaching me more about legacy code than any university course ever could.
turns out 90% of software engineering is just apologizing to a database and hoping the previous dev left a comment that isn't just "fix this later."