Explore >> Select a destination
|
You are here 
|
agileconversations.com | ||
| | | | |
chrisfrew.in
|
|
| | | | | Insights from startup land! | |
| | | | |
infraeng.dev
|
|
| | | | | Written interview in May, 2022. Learn more about Mahdi on his website, linkedin, and his StaffEng podcast interview. Tell us a little about your current role: where do you work, your title and generally the sort of work you and your team do. I am currently a Senior Staff Engineer at 1Password, leading the Server Architecture team. We are implicated in our systems overall design while pushing for the modernization of legacy systems. | |
| | | | |
benoitpasquier.com
|
|
| | | | | For the past few years, I had the opportunity to mentor new joiners through different roles. In some aspects, I could see myself in them the same way I started years back: eager to prove themselves, jumping on the code and hacking around. I tried to think about what I learnt the hard way since my first role in the tech industry and how could I help them learn the easy way. | |
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
