Yearly performance reviews for software engineers can be a stressful and/or exciting time. If we can prepare for review season by having a clear idea of our impact, data to support it and a clear vision for where we want to go in our career, we can set ourselves up for a successful yearly performance review.

Chapters
New Year - New End-of-Year Review Cycle 00:25
End of Year Reviews Focus on Two Things 02:05
How to Review Your Previous Year? 02:20
Write Down Your Accomplishments 02:55
Managers Love Concrete Numbers 03:31
Build Your "Brag" Document 04:27
Concisely Capture Impact 05:33
How Do You Want To Grow In The Next Year? 06:49
Are You Trying To Get Promoted? 07:47
Are You Trying To Learn A New Or Role? 08:39
Be Prepared 09:49
Stay Open To Feedback 11:11
Summarize The End Of Year Review Framework 13:18

Thanks for listening devs! 👋

Let's Connect
--
🔔 Find More Developer Content On YouTube
https://www.youtube.com/c/goobario?sub_confirmation=1

🙂 Find Me Online
website ➡ https://goobar.dev
links ➡ https://goobar.dev/links

Descoping a project or feature simply means making it smaller. This might mean cutting out a few bells and whistles, or it could mean making large changes to the overall requirements.

By evaluating project requirements and deadlines early on, and looking for ways to deliver smaller portions of that project earlier in the process, we can deliver value earlier and more often.

This process can help us reduce risk and help increase the overall quality of the project by getting feedback earlier on in the software development process.

Thanks for listening devs! 👋

Let's Connect
--
🔔 Find More Developer Content On YouTube
https://www.youtube.com/c/goobario?sub_confirmation=1

🙂 Find Me Online
website ➡ https://goobar.dev
links ➡ https://goobar.dev/links

When debugging an error in our code or looking for a solution to a given problem, it's easy to fall into the trap of going with the quick, obvious solution. However, this often sets us up for future problems because many times the obvious solution does not solve the root cause of the error or solve the fundamental problem of the task in front of us.

By asking questions like "how?" or "why" we can dig deeper into the potential solutions and try to identify a fix or solution that addresses the immediate need while also avoiding future problems.

Thanks for listening devs! 👋

Let's Connect
--
🔔 Find More Developer Content On YouTube
https://www.youtube.com/c/goobario?sub_confirmation=1

🙂 Find Me Online
website ➡ https://goobar.dev
links ➡ https://goobar.dev/links