Explore Across Campuses

i teach second-year engineering. i have watched the placement conversation change in three years. it used to be 'which company'. now it's 'is there a company'. the students are not less capable. the question they are being asked changed. that is the whole difference and nobody has told them it isn't their fault

we shipped a feature in march that i could not have written in the time we had. i reviewed every line. it passed review. four months later the bug in it cost us two days and a customer call. that is the real shape of this: not 'AI replaced me', but 'i am responsible for code i did not write, at a speed i cannot reason about'

i am 34, i have 11 years in, and the band i was hired into no longer exists as a role. not gone — reshaped. i do the same work with a tool and a third of the team. i am not worried about my job this year. i am worried about what the 22-year-old joining me does for their first two years

the thing nobody will say: most of the people reading about this are employed, and the employed part is temporary, and they know that, and they cannot say it at work. that's the entire emotional content of this thread. a room full of people who are fine and not fine, describing the same quarter

my company announced AI-led efficiency. no name, no number, no team. 8 weeks later the attrition report shows two departures from my team that i did not connect to the announcement at the time. i connected them afterwards. i have not said this out loud to anyone inside and i am saying it here

i have been in the industry 6 years and i am now worried about being too senior for the entry jobs and too junior for the AI ones. 3-5 years experience is the sweet spot band for demand. i am one year past it. i notice this every time i read a hiring report

i keep a list of things i can no longer do on my own. not because i forgot. because the tool is faster and i have stopped practising. i found that list last month and i have not decided yet whether that's efficiency or a slow handover of a capability i will not get back

i am reskilling from manual QA into automation testing at 38, in a market where the entry band is 26. i have the domain knowledge, i have the salary to manage, i do not have the enthusiasm everyone else has for the tools. i am doing it anyway. that is not a story, it is just what it is

i have been quietly learning AI tooling for 8 months because i could see this coming and i did not want to be the person who found out in a meeting. i still want to be the person who found out in a meeting. that contradiction is the actual state of most of the industry right now and nobody admits it

a CTO said if you take copilot away from his young engineers, 90% of them will struggle to code. the seniors look at the output with a critical eye. that is the entire pyramid in one quote: we built a generation that cannot start from nothing and trained the people above them to distrust what it produces

i earn well. i am not going to pretend i don't. what i want to say on an anonymous page is that well-paid and secure are different things and this year taught me the difference. i have the same job i had in march. i have less certainty about 2027 than i did in march. both statements are true

everyone says 'kal se pakka padhai' and then it becomes 1:40am. four of us, one laptop between three of us, the fourth watching. we are 2 hours into a syllabus we will not finish. this is the third week. it is not working and we are not stopping.