Frontend Infra Book
  • Why I Wrote This Guide
  • Mock Interviews
  • Development Roadmap
  • Product/Nonfunctional Requirements
  • Technical/Functional Requirements
    • Performance
    • User Experience Tracking
    • Backend Integration
    • Security
    • DevOps
    • Other / Unsorted
  • Design System & Common Components
  • Examples
    • Trading System
  • Topic In Depths
    • Containerization
    • Data Stack
    • Tools and Packages List
  • Common Solutions
  • Success/Failure Stories
    • Comp At Startups
    • Scaling FE Teams - My HOVER Story
  • Other Resources
  • Environment Setup
  • About The Author(s) + Contributing
  • Interviewing for FE
    • Getting The Interview
    • Negotiation Tips
    • How RSU's Work
    • Moving Up in Your Career
    • FAQ
    • Companies
  • Culture
  • What Matters in Company Culture
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub

Culture

Unpopular Decisions

When I was starting my engineering career, I would often argue with the team on technical decisions. But as I grew, I learned that these things aren't black and white. I remember when I just turned 20 years old, and I was working in the Communications dept at the Federal Reserve. One of my coworkers printed out a gray rectangle and posted it on my monitor. It helped remind me of that fact.

And since that time I started seeing that there any many points of view. There's usually a reason why somebody made a certain decision, and often times it's not even technical. There are all sorts of factors to consider, such as legacy costs, bugs that will inevitably be caused by a large refactor, etc.

So whenever I encounter such scenarios, I really take the time to explore why the team has a certain point of view, rather than jump to explaining my technical correctness.

PreviousCompaniesNextWhat Matters in Company Culture

Last updated 3 years ago

Was this helpful?