L8 Explains The Leap From Junior To Senior Software Engineer
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
L8 Principal's Agentic Engineering Workflow
Kun Chen
50.6k views
AI Tech Layoffs Explained by ex-Meta Principal Engineer
Kun Chen
81.8k views
Ken Burns Explains the Revolution’s WARNING for America
Legal AF
43.0k views
The Plan To Assassinate Charlie Kirk EXPLAINED!
The Jimmy Dore Show
354.8k views
Software engineering is dead now
Theo - t3․gg
165.4k views
Tom Lee Explains Why Gold & Silver Just Sold Off
Fundstrat
109.4k views
Anthropic confirms software engineering is NOT dead
ThePrimeTime
341.6k views
My honest advice to aspiring software engineers
Tech With Tim
34.9k views
How to Prepare for a Nuclear Apocalypse, Explained by a Chemical Engineer
Tucker Carlson
596.1k views
Tucker Carlson Explains How To Solve The Israel-Palestine Issue
Kim Iversen
76.3k views
Top Comments (10)
Great video again! Two things to add: 1. Prioritization. It is a relatively subjective activity. The goal is to maximize the outcome (e.g. quantifiable progress) within the pre-defined time period. The same priority on the same sets of projects may be considered good or bad depends on the culture of the company/organization, e.g. moving fast vs. laking the long view. Typically, projects are prioritized on a quarterly or 6-month basis, to align with the cadence of the earning report. Infra or new initiative may have longer horizon. 2. Probably the step of defining the measurement is before the prioritization, as the priority of a project is largely proportion to its anticipated quantifiable impact.
Awesome video and glad to see audio improve! A few other interesting topics: 1) Real/perceived culture differences across FAANG 2) Typical workday at different levels 3) Pros/cons of Seattle vs. Bay Area for big tech 4) Perception of coding bootcamps (as an L8) 5) Pros/cons of big tech vs. startups
This video is actually golden. I think a lot of people incorrectly assume that senior developers just know how to code more effectively. Instead it has way more to do with being able to lead other developers towards a solution. As you said, as the senior, you're typically the one to both come up with solutions to ambigious problems and prioritize those solutions so the dev team knows what to work on.
Straight to the point and no fluffy sugar coating. Great video pal!
The cat cleaning herself at @2:27 lol
the cat behind is cute haha
Started my SDE career a year ago. Will be following you for a bit of great advice.
Thanks for sharing all these information, it opens up a new perspective on how I can manage expectations from my current level and moving on to the next level.
I really love this video. It is been a year since i started working as full stack engineer at booz allen hamilton . I recently took a leap to help new onboarding devs to setup their environment. It wasnt easy but i have learnt a lot how hard it is for senior devs to help others. Thanks for sharing
this was amazing, i definitely needed this
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)
Great video again! Two things to add: 1. Prioritization. It is a relatively subjective activity. The goal is to maximize the outcome (e.g. quantifiable progress) within the pre-defined time period. The same priority on the same sets of projects may be considered good or bad depends on the culture of the company/organization, e.g. moving fast vs. laking the long view. Typically, projects are prioritized on a quarterly or 6-month basis, to align with the cadence of the earning report. Infra or new initiative may have longer horizon. 2. Probably the step of defining the measurement is before the prioritization, as the priority of a project is largely proportion to its anticipated quantifiable impact.
Awesome video and glad to see audio improve! A few other interesting topics: 1) Real/perceived culture differences across FAANG 2) Typical workday at different levels 3) Pros/cons of Seattle vs. Bay Area for big tech 4) Perception of coding bootcamps (as an L8) 5) Pros/cons of big tech vs. startups
This video is actually golden. I think a lot of people incorrectly assume that senior developers just know how to code more effectively. Instead it has way more to do with being able to lead other developers towards a solution. As you said, as the senior, you're typically the one to both come up with solutions to ambigious problems and prioritize those solutions so the dev team knows what to work on.
Straight to the point and no fluffy sugar coating. Great video pal!
The cat cleaning herself at @2:27 lol
the cat behind is cute haha
Started my SDE career a year ago. Will be following you for a bit of great advice.
Thanks for sharing all these information, it opens up a new perspective on how I can manage expectations from my current level and moving on to the next level.
I really love this video. It is been a year since i started working as full stack engineer at booz allen hamilton . I recently took a leap to help new onboarding devs to setup their environment. It wasnt easy but i have learnt a lot how hard it is for senior devs to help others. Thanks for sharing
this was amazing, i definitely needed this