not proud of it, man enough to say it software engineer POV

@youraveragetechbro

196.4K followers · usually 4.2K views a post

Views

165.6K

Likes

9.8K

Comments

483

Shares

470

SoundTikTok sound · original sound - youraveragetechbro

Promoted product

Yorbyyorby.ai

Yorby helps brands and creators go viral with a curated viral content database, AI-powered content remixing, competitor tracking, and an AI content coach.

3 videos

Why it worked

The video taps into a highly relatable and controversial topic for software engineers, using a vulnerable, conversational tone that encourages engagement and debate in the comments.

Summary

A software engineer discusses the existential crisis of using AI to write code instead of writing it himself. He compares this shift to the transition from low-level languages like C to higher-level languages like Java or Python.

Structure

1Admitting to relying on AI for coding
2Expressing professional insecurity about the shift
3Rationalizing the change through historical context
4

Original caption

not proud of it but man enough to say it software engineer edition#softwareengineer #startup #ai

More from @youraveragetechbro

Product placement

The video is a personal commentary on AI in software engineering, which aligns with the creator's product, Yorby, an AI-driven tool for social media growth.

On-screen text

not proud of it, man enough to say it software engineer POV not proud of it, but man I am a professionally trained developer. I wrote code pre-AI. I've worked in the big tech companies out there, But now with AI writing so much code, I don't always review the code that the AI writes. Sometimes I don't even test the code that AI writes, and I just look at it. It looks overall kinda good, and I just ship it out knowing that AI probably got it right. Do I like it? Not really, because it kind of does make me feel like, woah, do I even have a job anymore? I'm literally just reading and reviewing this code that I didn't even write. It does make me feel like everything that I studied in college to become a software engineer and all the work that I put into it is kind of a waste. But at the same time, I like to rationalize it by thinking that, hey, I'm pretty sure that the people that would write all their software in C, had to actually allocate all the memory themselves, They probably felt kinda similar when a really modern language like Java or Python came out, where they no longer had to handle all their memory allocation, and they're like, "Bro, this isn't real programming. What is it?" And I like to think that maybe this is just the next progression of programming, just letting LLMs rip it and just kinda reviewing the code from a really high-level architecture standpoint. Yeah, I don't know. Maybe that's just copium. Who knows?

Transcript

not proud of it, man enough to say it, but I am a professionally trained developer. I wrote code pre-AI. I've worked in the big tech companies out there, But now with AI writing so much code, I don't always review the code that the AI writes. Sometimes I don't even test the code that AI writes, and I just look at it. It looks overall kinda good, and I just ship it out knowing that AI probably got it right. Do I like it? Not really, because it kind of does make me feel like, woah, do I even have a job anymore? I'm literally just reading and reviewing this code that I didn't even write. It does make me feel like everything that I studied in college to become a software engineer and all the work that I put into it is kind of a waste. But at the same time, I like to rationalize it by thinking that, hey, I'm pretty sure that the people that would write all their software in C, had to actually allocate all the memory themselves, they probably felt kinda similar when a really modern language like Java or Python came out, where they no longer had to handle all their memory allocation, and they're like, "Bro, this isn't real programming. What is it?" And I like to think that maybe this is just the next progression of programming, just letting LLMs rip it and just kinda reviewing the code from a really high-level architecture standpoint. Yeah, I don't know. Maybe that's just copium. Who knows?