Vital Tips for Learning A New Codebase Quickly For Faster Productivity
Vital Tips for Learning A New Codebase Quickly For Faster Productivity. Adam Culp of Beachcasts php programming videos shares 6 tips on how to learn a new codebase quickly, while onboarding at a new job or project. We learn how to read code, and gaining an understanding quickly is important to software engineering. By learning a new codebase faster it enables us to become productive faster.
Please * LIKE, COMMENT, AND SUBSCRIBE * - and share with others!
Key Topics:
- Onboard at a new software engineering job quickly
- Take on smaller tasks to become familiar with code faster
- Find some mentors to help you navigate a new codebase
- Get code walkthrough from someone already familiar with the application
- Read documentation and wiki to pick up on business logic of a new application
- Leverage peer code reviews to onboard faster
- Define a rule to abandon prolonged blockers
For a nice list of equipment I use in my studio, and to support the channel if you make any purchases (doesn't cost you a thing), visit my kit at kit.co: kit.co/beachcasts/beachcasts-...
Errata:
Let me know if you notice anything that should be errata
Associated Links:
beachcasts.com
Timeline:
00:00 Video Intro
00:59 Link to another of my videos on understanding code written by others
01:10 Take on small tasks to get hands-on in a new codebase
03:05 Get some mentors to help you become familiar with a codebase
04:06 Ask someone to give a walkthrough of new code functionality
05:16 Reading documentation and wiki to help learn a new codebase
05:51 Use code reviews to learn a new codebase quickly
07:20 Institute a "no progress" rule to prevent prolonged stagnation
Other Beachcasts videos you might find interesting:
How to understand code written by someone else • Secrets of how to unde...
Laravel Query Builder Usage With Example Code • Laravel Query Builder ...
How To Create And Use Github Packages For Docker Containers • How To Create And Use ...
Measure PHP Code Quality With Static Analysis Using PHPStan • Measure PHP Code Quali...
Define Technical Debt and Contributing Factors for Software Errors • Define Technical Debt ...
Getting Started using Laravel Sail for Docker on WSL 2 • Getting Started using ...
Developing on Windows with WSL2 (Subsystem for Linux) and PHP • Developing on Windows ...
WSL 2 With Docker Getting Started and Docker Desktop Installation • WSL 2 With Docker Gett...
Getting Started with WSL 2 and Ubuntu on Windows 10 • Getting Started with W...
Secrets To Get A Developer Job And Searching For Programming Jobs • Secrets To Get A Devel...
Store sensitive data in environment variables using phpdotenv • Store sensitive data i...
Ways to advance your programming skills and improve as a developer • Ways to advance your p...
Make your local DEV environment available on the internet • Make your local DEV en...
AWS Elastic Load Balancer (ELB) Tutorial How-To • AWS Elastic Load Balan...
Laravel Model Factory Tutorial using Artisan make:model • Laravel Model Factory ...
Authentication in Laravel Tutorial • Authentication in Lara...
Top 5 skills to be a better software developer • Top 5 skills to be a b...
Install Laravel in Docker container on Ubuntu for beginners • Install Laravel in Doc...
Getters and Setters accessors in object-oriented programming • Getters and Setters ac...
Critical programming issues preventing a PHP 7 upgrade • Critical programming i...
Behat for beginners functional REST API testing tutorial • Behat for beginners fu...
PHP Mess Detector static analysis to find PHP code smells • PHP Mess Detector stat...
How to get lines of code in PHP • PHPLoc Lines of code s...
Use UUID with Doctrine ORM for DB keys • UUID with Doctrine ORM...
Learn about Hypermedia and how to create it • Creating Hypermedia (H...
Configure PhpStorm for PHP development with Docker • PhpStorm setup for PHP...
Create PHP development environment with docker • PHP web development en...
Help through referrals:
I use TubeBuddy to help me manage my KZhead channel. If you're interested, click the following link to check it out. www.tubebuddy.com/beachcasts
#php #onboarding #beachcasts
For more on improvements for reading code better, see this video: kzhead.info/sun/n85vd6xusImJn6M/bejne.html
Here are some other videos on software engineering: kzhead.info/channel/PL6_nF0awZMoNvi0QLmcv4qY5kfbnHrqg_.html
amazing background!!
Learning how to read legacy/new codebases (other people's work) is very crucial. I've lost multiple jobs due to inability to understand big parts of the applications + trying to be "polite" and not sound too d*mb. In my experience, almost 90% of projects I had to participate/code, were legacy/large complex "sloppy-second" projects. It was a pure bliss to start a new project - completely different appreciation. This should be noted in every advice you could give to young developers.
I am feeling myself in the same space. How to overcome reading large complex undocumented codebase.
Thanks so much. I've used the Walkthrough method in the past and it saved me tons of hours and headaches.
This was tremendously helpful. I'm grokking a large-ish legacy codebase and these tips are great. Nice speaking style and production, keep up the good work!
Imagine working on a team which doesn't do code reviews, total nightmare. That's a good question to ask during an interview. Candidate: "you guys do code reviews right? Sr Engineer: "What's that?"
HA, great point! Glad to see code review becoming more and more common.
Good tips, but if you "find dementor" you run, unless you can cast expecto petronum
Very good point. LOL Thanks for watching.
1. Take on small task 2. Get a mentor 3. Ask someone for a walk-through 4. Read documentation 5. Code reviews 6. 'No progres' rule 7.
Thank you. But "no progress" rule, may be harmful for your career in some companies with tough working culture, like Amazon. BTW, even ask for help too much in such companies, may be bad idea)
Definitely. There can be some bravado and ego in teams which can make reaching out a bad idea. I guess a good rule is to try to solve it yourself before reaching out.
I think a good thing to do before reaching out is to anticipate the questions your teammate may ask such as- 1. What are you trying to do? What's the roadblock? 2. What have you tried to do on your own so far to solve said roadblock? 3. What led to this roadblock, issue? Or (if you're not sure yet) 3.5 What do you think led to this issue, what did you try that makes you think so 4. Which part specifically don't you understand/ you need your teammate's help with? (Figuring out an approach, asking for clarity) 4.5, If possible, when reaching out to ask for a best approach to a task, prepare your own suggestions of approaches to take as well Before reaching out, make sure to have the answers to those questions so your teammate gets the idea that you did put effort into the task before reaching out. Sometimes, as I formulate the answers to those questions- I end up figuring the answers lol (rubber ducking)
HELP