FrontendCheck (@FrontendCheck) header
FrontendCheck (@FrontendCheck) profile picture

Stop building todo apps. Start building unique SaaS with enterprise architecture. Your patterns. Your portfolio. Your thing. Built by @claudianadalin

Joined July 2025
Photo by FrontendCheck (@FrontendCheck)Photo by FrontendCheck (@FrontendCheck)Photo by FrontendCheck (@FrontendCheck)
FrontendCheck retweeted
Footgun #11 <Button primary>, <Button secondary>, <Button danger> Then you need primary + small + loading + disabled. Boolean props don't compose. Variant systems do.
1
1
3
110
FrontendCheck retweeted
Footgun #10 z-index: 9999 Then someone adds z-index: 99999 Then tooltips appear under modals. Dropdowns fight headers. Z-index needs a system!
1
1
4
96
FrontendCheck retweeted
Footgun #9 "Just use fetch" Then you need auth headers, token refresh, request/response interceptors, error handling... Use a HTTP client layer from day 1!
1
1
2
64
FrontendCheck retweeted
Footgun #8 "Just put the modal in the component" Then you need to trigger it from a dropdown, keyboard shortcut, bulk actions. Centralise your modal state! Tip: Use a state management library over context to avoid re-renders.
1
1
3
69
FrontendCheck retweeted
Footgun #7 "Just use localStorage" Then you need: - Cross-tab sync - Storage quotas - JSON parsing everywhere Abstract your storage from day 1.
1
1
3
84
FrontendCheck retweeted
Footgun #6 const API_URL = 'api.prod.com' Then you need staging. Then local. Then pre production. Environment-aware config from day 1.
1
1
2
95
FrontendCheck retweeted
Footgun #5 "We're English-only for now" Famous last words before a 3-week refactor. Wrap strings, even if you have one language.
1
1
1
4
106
FrontendCheck retweeted
Footgun #4 "Just call gtag() directly" Then you switch to Mixpanel. Then you add Amplitude. Then GDPR consent matters. Abstract analytics from the start. Swipe -> for the approach that scales If you need to switch vendors, you change one file. If you need to add consent, it’s all in once place.
1
1
5
245
FrontendCheck retweeted
Footgun #3 PM: "Can we show this to 10% of users?" You: "Sure, I'll add a boolean" 6 months later: 47 booleans, no way to track what's on. Feature flags need a system. Swipe -> for the approach that scales Audit your flags. Know what's live. Clean up what's dead.
1
1
6
107
FrontendCheck retweeted
Footgun #2 "Just use a string for status" Then someone asks "what statuses can come AFTER pending?" Don't sleep on state machines. Swipe -> for the approach that scales Now when product asks, "can shipped go back to processing?", you check one object. Not 47 files.
1
1
13
1,088
FrontendCheck retweeted
Footgun #1 Checking permissions with role comparisons. if (user.role === 'admin') { ... } Works with 3 roles. Breaks with: - Granular permissions - Role hierarchies - Custom access levels The fix: Centralized permission system Swipe → for the approach that scales
1
1
6
232
FrontendCheck retweeted
Replying to @alexgilev
Exactly what we're building at @FrontendCheck! Not "here's how to build a button", but "here's how to structure your frontend so it doesn't collapse when requirements change or the team scales." frontendcheck.com/
1
2
94