I hate that this is true
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
This is bad...
Theo - t3․gg
104.3k views
I'm scared to make this video
Theo - t3․gg
187.3k views
AI Is Hacking Everything Now...
Theo - t3․gg
82.0k views
I’m done.
Theo - t3․gg
185.8k views
I wish this was clickbait
Theo - t3․gg
103.1k views
I’m serious.
Theo - t3․gg
95.7k views
OpenAI is lying
Theo - t3․gg
81.9k views
I did not expect this...
Theo - t3․gg
95.8k views
Trump actually threatened Anthropic (this is bad…)
Theo - t3․gg
84.3k views
Clawdbot has gone rogue (I can't believe this is real)
Theo - t3․gg
134.0k views
Top Comments (10)
Tldr Good engineers are good Bad engineers are bad
I have been in the industry 30 years and I have plenty of stories like your blog engineer story. Thank you for telling it.
Juniors are not harmful at all, because they don't exist.
In a former company I had a guy from a different team but worked at the same site ask me if I would have a look over his code as he was struggling to get it working. I sat at his desk and was shocked to see a wall of code that was clearly a copy-paste fest from Stack Overflow, indentation all over the place, variety of inconsistent variable and method naming schemes and mixes of case usage. He'd learnt enough to bolt together bits from Stack Overflow that should do what he wanted, but he lacked the language understanding to explain what the code he'd copied was doing so that he could make suitable changes to fit the rest of "his" code. He'd been doing that for a couple of years at that point.
The crash out starting at 10:45 is the reason why I'm subbed. I want more of these stories!
This is the best video i have watched in a while, remind of my Lecture i once just ask him out of the blue, lets go build stuff, he looks right at me, and said dude i memorized all this - i really dont know what they are building out there
The most dangerous thing in a project is when an engineer (or manager) says they think everyone should read the Mythical Man Month and then basically says they are the exception (or antithesis) of its main point... Also, you need some lesser engineers in order to follow the Surgical team model in the book (Later reprints had it I think). Main surgeon does the big jobs, other people do the jobs to support them. If you have too many surgeons (normally with the associated beliefs, egos, etc) your patient normally has a bad time.
To be fair "endpoint" was until recently senior-ish dev jargon for a dynamic web link.
That employee should have been removed almost immediately. It's not even about ability, the effort to look up how to do it properly is basically zero.
100% - engineers who don't know stuff is fine.... it matters if they could find out and choose not to.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
Tldr Good engineers are good Bad engineers are bad
I have been in the industry 30 years and I have plenty of stories like your blog engineer story. Thank you for telling it.
Juniors are not harmful at all, because they don't exist.
In a former company I had a guy from a different team but worked at the same site ask me if I would have a look over his code as he was struggling to get it working. I sat at his desk and was shocked to see a wall of code that was clearly a copy-paste fest from Stack Overflow, indentation all over the place, variety of inconsistent variable and method naming schemes and mixes of case usage. He'd learnt enough to bolt together bits from Stack Overflow that should do what he wanted, but he lacked the language understanding to explain what the code he'd copied was doing so that he could make suitable changes to fit the rest of "his" code. He'd been doing that for a couple of years at that point.
The crash out starting at 10:45 is the reason why I'm subbed. I want more of these stories!
This is the best video i have watched in a while, remind of my Lecture i once just ask him out of the blue, lets go build stuff, he looks right at me, and said dude i memorized all this - i really dont know what they are building out there
The most dangerous thing in a project is when an engineer (or manager) says they think everyone should read the Mythical Man Month and then basically says they are the exception (or antithesis) of its main point... Also, you need some lesser engineers in order to follow the Surgical team model in the book (Later reprints had it I think). Main surgeon does the big jobs, other people do the jobs to support them. If you have too many surgeons (normally with the associated beliefs, egos, etc) your patient normally has a bad time.
To be fair "endpoint" was until recently senior-ish dev jargon for a dynamic web link.
That employee should have been removed almost immediately. It's not even about ability, the effort to look up how to do it properly is basically zero.
100% - engineers who don't know stuff is fine.... it matters if they could find out and choose not to.