How to Prepare for Yearly Performance Reviews as a Software Engineer

How to Prepare for Yearly Performance Reviews as a Software Engineer

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

Descope Your Software Project To Deliver Early And Often

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

Look For The Root Cause When Solving Problems

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

Why Share Your Work?

Why share your work?  Why take that risk and put yourself out there? Well, it's because there are a lot of very positive things that come out of the process of sharing.  From improved skills, to unexpected opportunities, to more effective conversations and documents at work - sharing can help us in many ways. Listen to this week's podcast episode to learn more about why you should think about sharing your work. Chapters 01:59 Improve Our Communication Skills 02:55 Learn to tell stories with your work 03:47 Better understand the needs of project stakeholders 05:00 Leads to interesting conversations 05:40 What if I'm wrong? 07:15 Unexpected opportunities 09:33 Helping Others 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

Jetpack Compose Tips From a Production Android App

This week's podcast episode explores Jetpack Compose tips that have been helping my team while using Compose in an existing production Android app. Chapters 00:43 Intro 02:12 Leverage self-documenting apis 04:07 Embrace slot-based api design 07:46 Expose composable parameters with sensible defaults 11:18 Customize your Composable previews 13:15 Modularize for faster @Preview refresh 16:02 Build a sandbox app for rapid prototyping 18:25 Pull from the MaterialTheme 19:30 Theming is contextual 21:35 Extend MaterialTheme when needed - but not for everything 24:20 Use a debug color palette Show Notes Jetpack Compose https://developer.android.com/jetpack/compose [https://developer.android.com/jetpack/compose] Slot-based layouts https://developer.android.com/jetpack/compose/layouts/basics#slot-based-layouts [https://developer.android.com/jetpack/compose/layouts/basics#slot-based-layouts] Theming in Compose https://developer.android.com/jetpack/compose/themes [https://developer.android.com/jetpack/compose/themes?hl=ru] Adopting Compose https://developer.android.com/jetpack/compose/interop [https://developer.android.com/jetpack/compose/interop?hl=ru] 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