Cagdas Yonder

@cagdasyonder

Frontend Engineer shipping products at startups. Interested in scalable architecture and design systems.

Vancouver, British Columbia

Joined July 2015

76Posts 24Followers 148Following

Cagdas Yonder

@cagdasyonder

Oct 15

When a library offers both <DatePicker /> and useDatePicker(), choose the hook. Pre-built components force you to style around someone else's markup. Hooks give you the logic and let you build the UI your way. Your markup. Your styles. Full control.

Cagdas Yonder

@cagdasyonder

Sep 21

As a new dev joining a team, your fresh perspective is valuable but hold those big suggestions for a bit. First understand how the team works, how the product functions, and why decisions were made. That "outdated" approach? There's often a reason. Listen, learn, then contribute.

Cagdas Yonder reposted

Cory House

@housecor

Aug 28

Often, the “best” technology doesn’t win. Why? Because it must be *way* better to justify the risks and switching costs. Is it buggy? Is it easy to learn? Is it well documented? Is the ecosystem sufficient? Is our team willing to switch? Is the support team responsive? Is it…

Cagdas Yonder

@cagdasyonder

Jul 18

Not sure why, but I get a strange joy from racing against the clock to enter my MFA code. It's like a mini action movie. Especially when I beat the code turning red by a second.

Cagdas Yonder

@cagdasyonder

Jul 6

Keep your media queries next to the styles they modify, not bundled at the bottom of your stylesheet. When tweaking grid layouts, you shouldn't have to scroll through 500 lines to find the tablet version. Colocated responsive styles mean less scrolling and faster edits.

Cagdas Yonder

@cagdasyonder

Mar 30

#Severance is the most original thing I’ve watched since The Matrix.

Cagdas Yonder reposted

Lex Fridman

@lexfridman

Mar 26

Most journalism seems to maximize for drama & engagement not wisdom.

Cagdas Yonder

@cagdasyonder

Mar 5

Great DX isn't just nice to have. It drives productivity. When tools provide intuitive APIs, clear docs, and consistent patterns, devs focus on solving problems, not fighting tools. Better DX often leads to better products and less frustration.

Cagdas Yonder

@cagdasyonder

Jan 27

Keep your components pure by moving spacing to the implementation layer. Adding margins inside components is like baking the plate into the cake. It limits where and how you can serve it. Let each usage context decide the spacing it needs.

Cagdas Yonder reposted

Cory House

@housecor

Sep 14, 2021

#1: Know the 8 ways to handle state, and when to consider each.

Cagdas Yonder

@cagdasyonder

Dec 25

Use dummy data during UI development instead of making network requests. It speeds up your workflow and lets you focus on styling without waiting for API responses. Save real API calls for when your components are polished and ready for integration.

Cagdas Yonder

@cagdasyonder

Nov 8

Duplicate styles, conflicting CSS rules, and unclear naming patterns create a maze of complexity that makes the codebase harder to debug and maintain. Names should reflect unique roles in context (semantic), and similar styles should be consolidated into reusable patterns.

Cagdas Yonder

@cagdasyonder

Oct 30, 2024

Your atomic components power every corner of your app. Modifying them for one-off needs is like changing traffic lights because you're in a hurry. What helps your flow breaks everyone else's.