Using generic/common libs/frameworks - in my experience I'd say depends on the scale. I've seen a case when company wide swiss army lib was created and enforced to be used (logging, security, base controllers etc) & it failed just like you described. In another case... - ThreadSky

About ThreadSky

gmanvel.bsky.social • 156 days ago

Using generic/common libs/frameworks - in my experience I'd say depends on the scale. I've seen a case when company wide swiss army lib was created and enforced to be used (logging, security, base controllers etc) & it failed just like you described. In another case...

Comments

gmanvel.bsky.social•156 days ago

I could see small teams (2-3 teams) using common libs, which implement cross cutting concerns (security, documentation, observability), with great success. Wouldn't you want unified approach across (small) teams in implementing these? I understand once you scale (Amazon) the game is different.

oskardudycz.bsky.social•156 days ago

I wasn't ever working in an Amazon scale, but I already seen a lot of issues in my projects around creating a single core/shared/platform code. It might not be quickly visible, but it starts to be an issue after a year or two if it's only to centralise the random code in the single place.

/1

oskardudycz.bsky.social•156 days ago

Still, of course I agree that it can work, and more likely with smaller teams, where there's a shared understanding of what we're doing. It's also a matter of the knowledge in our team, and how we deal with learning ladder. That's what I wrote here 👇: https://bsky.app/profile/oskardudycz.bsky.social/post/3ldvxztwkr223

2/

oskardudycz.bsky.social•156 days ago

I think that even a single-placed monolithic approach can be fine, as long as we focus on providing the certain capabilities instead of treating our team as overprotective parents treats their children 😅

It's more about the attitude and strategy, than a release scheme. 🙂

3/3

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply