|
For my team, complexity comes from operating at varying degrees within our IdP. Pre-auth, during-auth, and post-auth are all things we build features around. We have tons of data points that we fetch in a request flow based on network info, a policy configuration, the IP address, user's behavior, tons of things. Thus the complexity comes in a few pieces: how do we feed these points into a system and decision on them, where do we allow varying degrees of configuration based on what clients what, and at what point/in what factors, contexts, etc do we support enforcement? quote:
|
# ¿ Apr 22, 2024 16:39 |
|
|
# ¿ May 6, 2024 12:58 |
|
Yep. Part of why for a team like mine the knowledge solo "system architect" is untouchable here but also a glaring issue for upwards of 15 people and oodles of money.
|
# ¿ Apr 23, 2024 18:26 |
|
What's a solid number of engineers to have under you as a TL whose focus is primarily writing tech designs, reviewing product docs, planning rollouts, and doing code reviews? At 5 I'm feeling a little bit spread thin as there's a near constant barrage of incoming support tickets and questions as well.
|
# ¿ Apr 26, 2024 22:34 |
|
Definitely something I've called out to my boss. We're aware of this, but also I'm getting a new boss soon (as in new to the company). Part of the reason isn't comfort or desire but the fact that I'm a knowledge silo in 2-3 areas that my team owns. We're working on transitioning but it's going to take time. Ideally I'd like to hand off some of the program/product management and do primarily tech designs, code reviews, and broader PoCs for new features and functionality. I'd love to not be a regular Monolith committer.
|
# ¿ Apr 27, 2024 23:05 |