๐ฐ๐๐๐๐ ๐ฐ๐๐๐๐๐
3.6K posts

๐ฐ๐๐๐๐ ๐ฐ๐๐๐๐๐
@ashirashraf
Digital construction worker. เดฎเดฒเดฏเดพเดณเดฟ. Linux enthusiast.


you just made food. you're at the table. laptop open. what are you watching first?



Learning lessons from Jurassic Park

I present to you - Cursor Hats






I am really dumb today, I Had interview โ everything was going smooth. I answered almost everything. They explained their startup, it was really good. Then in next round โ they gave me a project to build in 1 hour. By godโs grace I built it, fixed some errors, everything was working. Then they asked for the deployed linkโฆ And thatโs where everything broke Vercel started giving build errors. I tried EVERYTHING for 1 hour nothing worked. Iโve deployed many projects before, but never faced this issue. Issue: Vercel was using an old Node version from a previous commit + Git wasnโt even detecting my changes. Fix? Added a SPACE โ commit โ redeploy โ it worked Sometimes debugging makes you question your life existence.

An employee just asked for a second monitor. Standard request. Usually takes 3 clicks to approve. But they submitted the ticket under Software Procurement instead of Hardware Request. If I process it, my internal audit metric takes a hit for cross-category resolution. So I rejected it and told them to submit it correctly. They submitted it under Network Outage. I rejected it again. They emailed me directly, CCing their director, asking why I am blocking their productivity. I replied all with a link to our KB article on How to Select the Correct Dropdown Menu. The director replied to me privately to just give them the monitor. I said I would, pending a properly categorized ticket. Eventually, the ticket arrived in the right queue. I approved it in four seconds. Time to resolution: four seconds. Process is a beautiful thing.

Huh, so that's why text is called a string













