Software Engineering at Google
Reading Software Engineering at Google has been one of the most interesting parts of the course. It gave me a glimpse into the level of thought and discipline that goes into large-scale engineering at a company like Google. The emphasis on reducing friction, fostering collaboration, and designing systems that scale all reinforce how much of engineering is about people and process, not just code.
One thing that stuck with me was how intentional they are about keeping workflows fast and clean. It's clear that great engineering culture is built deliberately. That’s a mindset I want to adopt moving forward.
JUnit & Mockito
I’ve come to appreciate how unit testing is more than just a safety net, it’s a habit that forces you to think clearly about how your code behaves. Learning how to use mocks and stubs effectively (especially with Mockito) was a big leap. I never realized how powerful it is to isolate behavior and verify interactions.
Writing tests used to feel like a chore. Now, it feels like an essential design tool. That shift in perspective is probably one of the most important takeaways for me so far.
Selenium Testing = Wizardry
This week’s introduction to Selenium felt like unlocking a new spell in my developer toolkit. Watching a browser get spun up, navigate through a site, and click through flows with no manual input? Pure sorcery. It’s given me a new appreciation for automated testing and also how tricky front-end reliability can be.
Comments
Post a Comment