In hindsight, I've created somewhat of a unique way of coding Starting new is hard. Few people have the entire ecosystem of code loaded in their mind. Progress is excruciatingly slow at the beginning * connect the database * build repos * setup DI * database migrations *

Had a shit post locked-and-loaded but then dug into exception filters and I gotta say this is pretty slick. try/catch wrapper using generics to filter for exceptions How are you using exception filters in your projects?

Jira > Azure DevOps I don't quite get the Jira hate. I think it works reasonably well — isn't perfect by any stretch. Azure DevOps hasn't changed in 10 years. Maybe that's a good thing? But Work Items feels down right archaic.

Learning a language for the sake of learning a language feels like a fools errand to me. It's really hard to answer the question "what language should I learn"? Whoever answers has no choice but to heavily include their bias. I think it's a better question to ask "what do I

being a coder, i'm pedantic on the difference between the number zero and the letter O at the end of the support call, the person recited the ticket number to me four, one, eight, T, A, two, "OH" Knowing this is a common normie mistake, I asked for clarification on the final

what does thread safety mean to you? If you're surprised that l1.count is less than 1000 then time for some study

weekend project: snake in C# the code kinda sucks. there's probably a 1000 better ways to implement this game. i just tried to figure it out. throw back to my old Nokia phones

https://t.co/EZBxkLUENd

C# switch expressions Moaaaarrrrrrrr LINQ please

`dotnet build -c Release` This command underpins nearly all of your build pipelines whether it's Azure DevOps, GitHub Actions or GitLab Pipelines OR a shell script running on an old desktop in the office closet. Build pipelines are just a somewhat complex way to a) document

update: in the past 5 minutes I've been hit with 2 out of the blue null reference exceptions. I don't like the karma that I've triggered.

simple recipe for null exceptions 1) create bloated class 2) ignore constructors 3) act surprised when things break The ENTIRE PURPOSE of the constructor is to create VALID INSTANCES of a type. You, as the coder, should create classes such that any instance is ALWAYS a valid

DataTable: the original Entity Framework never forget!

C# Sieve of Eratosthenes (prime number generator) LINQ let's gooooooo

I do nice things for my team like add style rules that force leading commas then auto-format the repo so they just can just pickup my changes on their next pull.

Users just have to wait longer if I ignore the cancellation token

Null is not a crime!

@RyanRodemoyer2 @hibakod

Option A is soooooo much better LINQ is a gateway drug

TIL that we can get internet points for posting LINQ snippets

a) S-Q-L Server b) Sequel Server c) MyS-Q-L d) MySequel Choose 2