> Markdown version of [/videos/378-but-you-re-not-facebook](https://www.wearedevelopers.com/videos/378-but-you-re-not-facebook). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# But, you're not Facebook

Stop over-engineering simple web apps. You are not Facebook. Drop the developer ego and embrace pragmatic tools to ship actual value before AI outpaces you.

- **Speakers:** Kristijan Ristovski
- **Event:** World Congress 2022
- **Published:** June 15, 2022
- **Duration:** 31:12
- **URL:** https://www.wearedevelopers.com/videos/378-but-you-re-not-facebook

## Summary

Web developers frequently fall into the trap of over-engineering simple applications by adopting the complex architectures of massive tech giants. Despite the reality that most developers do not work for hyperscale companies, the industry obsesses over solving non-existent problems, prioritizing achievements like perfect test coverage or maximum Lighthouse scores over shipping functional products. This hyper-focus on theoretical edge cases often ignores actual user analytics demonstrating that modern devices can easily handle practical codebases without obsessive micro-optimizations.

Instead of delivering maximum value, engineering teams continuously reinvent solved problems, wasting critical time debating button aesthetics or wiring up boilerplate-heavy state management frameworks for rudimentary data fetching. By stubbornly clinging to bespoke configurations, custom CSS architectures, and strict linting rules, developers prioritize the prestige of a sophisticated tech stack over the end-user experience. Adopting established solutions like CSS-in-JS, replacing rigid terminal workflows with visual tools like Sizzy, and leveraging GraphQL for simplified data handling can drastically reduce architectural overhead.

To remain relevant in an environment where artificial intelligence is rapidly learning to generate component logic, the frontend community must relinquish developer ego and embrace pragmatic innovation. Shifting away from terminal-centric stubbornness toward modern, UI-driven workflows enables teams to prioritize core product features and rapid iteration. Ultimately, abandoning the mimicry of enterprise-scale engineering allows teams to ship meaningful results faster and focus entirely on solving concrete user challenges.

**Keywords:** web development over-engineering, frontend state management, lighthouse performance scores, react application architecture, developer productivity tools, css-in-js adoption, redux boilerplate challenges, graphql data fetching, user-centric software delivery, codebase test coverage traps, terminal versus ui workflows, ai code generation threat, component design systems, sizzy browser features, tech stack selection, agile feature shipping

## Chapters

1. **Introducing dedicated browser tooling for front-end development workflows** (00:05) — Consolidating essential testing tools into a dedicated browser environment replaces disjointed and complex development setups.
1. **Recognizing and ignoring hypothetical performance bottlenecks in software** (04:46) — Anticipating imaginary memory leaks and rendering issues distracts software teams from delivering concrete value to users.
1. **Prioritizing real user outcomes over synthetic software metrics** (07:04) — Focusing on actual user analytics ensures products deliver value instead of merely achieving perfect synthetic performance metrics.
1. **Reducing technical complexity and avoiding over-engineered application architectures** (10:48) — Abandoning unnecessarily complex state management tools for basic inputs prevents delayed product shipments and over-engineered architectures.
1. **Focusing on core functional features instead of cosmetic details** (15:17) — Prioritizing complex interface animations over essential registration flows causes minimum viable product launches to fail.
1. **Leveraging existing library solutions to accelerate application development** (16:58) — Replacing complex global state architectures with modern data fetching frameworks drastically simplifies front-end application codebases.
1. **Evaluating component styling solutions against unfounded bundle size concerns** (21:26) — Rejecting modern styling solutions over negligible payload increases unnecessarily harms component maintainability and team productivity.
1. **Evolving developer environments beyond legacy terminal text command interfaces** (25:14) — Transitioning away from obscure command line configurations toward visual tooling accelerates interface development and debugging workflows.
1. **Embracing artificial intelligence and replacing traditional front-end engineering** (28:09) — Integrating automated coding assistants into modern development workflows requires letting go of traditional software engineering ego.

## Related Moments

- [Evaluating the operational trade-offs of modern javascript frameworks](https://www.wearedevelopers.com/videos/1347-wearedevelopers-live-rendering-in-the-browser-the-state-of-css-and-accessibility-and-more) (from "WeAreDevelopers LIVE - Rendering in the Browser, The State of CSS and Accessibility and more")
- [Prioritizing business logic and user value over technology choices](https://www.wearedevelopers.com/videos/118-how-to-stop-choosing-javascript-frameworks-and-start-living) (from "How to Stop Choosing JavaScript Frameworks and Start Living")
- [Navigating CSS complexity and embracing core frontend technologies](https://www.wearedevelopers.com/videos/1788-wearedevelopers-live-you-don-t-need-javascript-modern-css-and-more) (from "WeAreDevelopers LIVE – You Don’t Need JavaScript, Modern CSS and More")
- [Exploring alternative build tools and experimental web components](https://www.wearedevelopers.com/videos/118-how-to-stop-choosing-javascript-frameworks-and-start-living) (from "How to Stop Choosing JavaScript Frameworks and Start Living")
- [Overcoming challenges of scaling legacy monolithic frontend applications](https://www.wearedevelopers.com/videos/236-microfrontends-at-scale) (from "Microfrontends at Scale")
- [Exploring frontend development choices beyond standard JavaScript frameworks](https://www.wearedevelopers.com/videos/390-debugging-static-web-apps) (from "Debugging Static Web Apps")

## Related Articles

- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [Dev Digest 130 - The Diablo is in the details](https://www.wearedevelopers.com/magazine/470-dev-digest-130-the-diablo-is-in-the-details)
- [Dev Digest 133 - Back to Front](https://www.wearedevelopers.com/magazine/474-dev-digest-133-back-to-front)
- [How to Avoid Over-Engineering](https://www.wearedevelopers.com/magazine/546-how-to-avoid-over-engineering)

## Related Jobs

- [Junior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/1532351-junior-frontend-engineer) at **Almedia**
- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**
- [Software Engineer](https://www.wearedevelopers.com/jobs/ext/1304673-software-engineer) at **Bitpanda**
- [Staff Frontend Engineer (Expert+/Lead equivalent) - Hybrid working model, 100%, Ho Chi Minh City](https://www.wearedevelopers.com/jobs/48314-staff-frontend-engineer-expert-lead-equivalent-hybrid-working-model-100-ho-chi-minh-city) at **SMG Swiss Marketplace Group**
- [Senior Software Engineer, React (Websites & Martech)](https://www.wearedevelopers.com/jobs/ext/1605272-senior-software-engineer-react-websites-martech) at **Bitpanda**
- [Mid/Senior Full-Stack Engineer (Web-first)](https://www.wearedevelopers.com/jobs/ext/1210833-mid-senior-full-stack-engineer-web-first) at **SMG Swiss Marketplace Group**