BEGGING

@skillfoundryio

11.9K followers · usually 1.2K views a post

Views

5.3K

Likes

217

Comments

2

Shares

1

Selling · Course / Info

Skill Foundryseen in 6 videos →https://linktr.ee/skillfoundry ↗

Why it worked

The video addresses a common pain point for aspiring developers: technical interviews and debugging. By highlighting a frequent failure point and offering a solution (using the debugger), it provides valuable, actionable advice that resonates with the target audience.

Summary

The video explains that in technical interviews, not knowing how to use a debugger can lead to failure, especially when presented with broken code. It emphasizes that mastering the debugger is crucial for navigating complex codebases and fixing issues efficiently.

Structure

1Introduction to the problem of not using a debugger
2Importance of exploring the codebase
3Common interview tasks: simple bugs and features
4Consequences of not using a debugger in enterprise environments
5Interviewers may provide broken code and expect debugging
6

Original caption

Technical interviews often test debugging skills by giving broken code and watching how you troubleshoot, not just whether you get the answer. On a mac? You have to start somewhere, start here! Link in bio. #coding #programming #learntocode #programmingbeginner

More from @skillfoundryio

Their other posts in the index, biggest breakout first.

Failure point: flailing at code instead of debugging

Product placement

Skill Foundry (appears on t-shirt, does not act, removing it would not change video)

Call to action

Link in bio.

On-screen text

BEGGING TO DEBUGGER IN THEIR MINDS when you get one one of the first things you're going to need to EXPLORE THE CODE BASE and one and one of the first tasks they're going to give are usually SIMPLER SIMPLER BUGS OR SIMPLE FEATURES BREAK FIXES THINGS LIKE THAT and if you're not USING THE you're gonna have a lot in an enterprise code base figuring figuring out where everything and what you need to touch to complete your and this will show up in the interview I know a that will give you broken code and they will ask and they will ask you to fix it during the interview AND THEY AND THEY WANT YOU TO but but what you often see with people that are with the debugger is FLILING AT THE CODE AND START CHANGING AND JUST RUN RUN IT AND NEVER USE THE DEBUGGER AND THAT AND THAT IS A COMMON failure point in technical interviews that you should avoid

Transcript

They are begging you to use the debugger in their minds when you get one. One of the first things you're going to need to do is explore the code base. And one of the first tasks they're going to give are usually simpler, simpler bugs or simple features, break fixes, things like that. And if you're not using the debugger, you're gonna have a lot in an enterprise code base figuring, figuring out where everything is and what exactly you need to touch to complete your and this will show up in the interview. I know a that will give you broken code and they will ask you to fix it during the interview. And they want you to use the debugger. But what you often see with people that are with the debugger is flailing at the code and start changing and just running it, run it and they never use the debugger. And that is a common failure point in technical interviews that you should avoid.