I originally posted this post on my blog.
I didn't have writer's block today. Naaah! I was just scrolling down the /csharp subreddit for inspiration.
Scrolling through, I realized I had answers and reactions. And to follow the popular YouTube format, here I go reacting/roasting/responding to the front page of /csharp:
#1. I wrote a cross-platform TUI podcast player in .NET 9 (mpv / VLC / native engine fallback) Source
Great! Put it on your portfolio.
#2. Best approach for background or async tasks Source
Mmm. Probably that's Hangfire.
Hi.
In my last project, I had:
1 Api for backoffice
1 Api for app mobile
1 Worker Service for all the background tasks
...
So now I'm in new project, but I'm not sure if is necessary use Masstransit with RabbitMQ? Maybe channels? I mean, I want to keep it simple, but I don't like put consumers or jobs in the same API, I always prefer to have a worker service dedicated to all asynchronous tasks.
Hangfire?! That's definitely Hangfire. I don't need to read more. And you don't need to look for anything else.
#3. Is conciseness always preferred? (Linq vs Loops) Source
Not that I have a course about it, but LINQ is the best of all C# features. Yes, write a LINQ query first. Then, if you're working on a high-performance scenario, go with loops.
#4. Can you explain result of this code? Source
Nah! I have a post to write. Ask ChatGPT or Copilot. It's free.
But seriously, it's a good exercise. Try debugging it yourself before asking.
#5. Let's Talk About the Helper Classes: Smell or Solution? Source
Definitely a smell. Helper classes attract plenty of methods. "Where do I put this new method? Oh there's a Helper class over there! I'm putting it there..."
If you're tempted to write a Helper class, hold your horses.
#6. In general is it normal to have more than 2k lines in a file? Source
You shouldn't have one. But yes, it's normal.
Scroll...scroll...
Nah! Boring! Scroll...scroll...
#7. After seeing that LOC post, can anyone beat this? Source
Really?! Like, c'mon. We're seeing who has a larger file?!
The other day, I shared that you know you're in trouble when you try to open a file on GitHub and it says "(Sorry about that, but we can’t show files that are this big right now.)" Spoiler alert: The file has 69,923 and it's called GlobalFunctions.vb.
You see? Helpers!
#8. Is C# good for beginners? Source
Hell, yes!
#9. Why is this issue only popping up at the 30 line? Source
Dunno! See #4.
Scroll...scroll...
#10. Career Guidance: .NET Backend Developer Role and Future Tech Stack Transition Source
"Blah...blah...blah... I've accepted the offer, but I sometimes question whether choosing the .NET path was the right decision. I'd like to understand the current job market for .NET developers."
Hey, buddy! We're in a bubble that is popping (or about to pop) now. In 2020-2021, "Software Engineer" on LinkedIn meant a line of recruiters with "life-changing opportunities."
These days? Just look at the headlines. Amazon just "let go" thousands of employees in the past weeks. And that was right after an outage that took down pretty much every client. That's for every stack, unless you have "AI" anywhere in your title.
OK, let's call it a day! That's enough roasting for today. I should be writing a YouTube script, but I don't have a channel. Just a blog...and a book. Speaking of which...
This post is brought to you by... Check out my latest book, Street-Smart Coding: 30 Ways to Get Better at Coding. It's not a C# textbook. It's the roadmap I wish I had on my journey from junior/mid-level to senior. Some lessons are conventional. Others not so much. From Googling to debugging to clear communication.
Get your copy of Street-Smart Coding here
PS: In case you didn't notice, this was half-joking. And yes, I'm promoting my book.
Top comments (2)
Good tongue-in-the-cheek promotion. ;-)
I had to look at the solution of the static fields problem. One one hand, it's boring (as it results, it depends on the implementation, in this case, on the implementation of static initialization), but on the other hand, it is interesting to get the inner workings of the compiler.
😁
Yeah, that's interesting to see what happens under the hood...just for curiosity!