Pinned Tweet
Truth is, when I started out, I was a terrible developer and among the worst in my coding bootcamp cohort. None of the programming concepts stuck.
The reason I made it this far, and others in my cohort didn't, was that I didn't quit π₯
James Lieu π¬π§ retweeted
neverForgetThatOneSrDev redd.it/1m7y0hn
ββ¦plans are useless, but planning is indispensableβ - Dwight D. Eisenhower
Planning is better if you want to handle uncertainty, complexity, and change.
And having a plan is still useful, and you really want both, but without continuous planning, the plan becomes obsolete fast
98
π© Flag arguments are a code smell.
If a function needs True or False to decide what it does, split it into two.
One job per function π
2
64
James Lieu π¬π§ retweeted
Never return null collections in C#.
Why? Because it forces every caller to handle the null caseβeven when they just want to iterate.
This leads to:
- Extra null checks
- More verbose code
- Potential runtime errors if checks are missed
Instead, return an empty collection:
- Enumerable.Empty<T>()
- new List<T>()
- Or [] if you're using C# 12
This keeps your code safer and easier to work with β no surprises, no crashes.
I share tips like this every Saturday with 67,000+ .NET engineers.
Join here: milanjovanovic.tech/?utm_souβ¦
Whatβs your take on returning null vs empty collections?
Tackle the real root cause, not just the symptoms.
This mindset saves time and prevents the same problems from resurfacing repeatedly. Itβs what separates quick fixes from true problem-solving.
1
45
Code is read and modified far more often than itβs written. Designing for maintainability means you help your future self and your teammates succeed.
1
2
91

























