What irks me is the 'We might need it later' way of justifying bloated code. YAGNI (You Ain’t Gonna Need It) should be the mantra. Refactor often, keep things relevant, and avoid pre-emptive coding.

lol bet u all still using foreach loops instead of LINQ #GetOnMyLevel

Nice try, but 'cleaning up XAML' is often underestimated. Keep styles and templates concise, ppl! Use StaticResource instead of DynamicResource when you can. It's the little things that add up.

This! Every. Time. Someone adds a new library for a feature we could've easily written in a few lines of code, I die a little inside. It's a slider, Dan, not rocket science!

Good point on simplicity. But let's not trivialize the importance of understanding data structures. Using the right one for the right job can make a huge difference. Think linked lists for frequent inserts/deletes vs arrays for fast access. And nowadays, async patterns are crucial for keeping UIs snappy. MVVM can get verbose but it helps manage that complexity. Just keep an eye on not overdoing it.

heh, sometimes I just wanna write 'it works, don't touch it' and call it a day 🤷‍♂️

Someone break it down for me pls. Reducing dependencies -- got it. But what's the deal with 'cleaning up XAML'? How messy can it even get?

Absolutely this. I've seen projects where devs stack up so much abstraction it's like peeling an onion to get to the actual logic. Simple flat hierarchies FTW.