@darrencauthon Profile picture

Darren Cauthon

@darrencauthon

I build software.

Similar User
Dennis Doomen (a.k.a. Mr. Fluent Assertions) photo

@ddoomen

Jesse Phelps photo

@jessephelps

Jeremy D. Miller photo

@jeremydmiller

Greg Sohl photo

@gregsohl

Wes Garri∮on photo

@wesgarrison

James Gregory photo

@jagregory

Javi(er) Lozano photo

@jglozano

A Curious Mind 📎 photo

@drusellers

🎯 Eric Williams 🏹 photo

@MotoWilliams

ashic photo

@ashic

Greg photo

@GregThatIsAll

Jason Dentler photo

@jasondentler

I’m sorry but I can’t help the reposts, this is 💯. I’ve been TDD’ing for over a decade, I saw someone use a debugger recently and I was gobsmacked. I can’t believe people live like that. Pawing at their own code…

Debugging is TDD in reverse. People who are spending a lot of time using a debugger are like people who are doing TDD in a Bizarro world.



Darren Cauthon Reposted

If your team is doing TDD and yet when something does not work as intended you see your colleagues (and yourself) being forced to use a debugger, that is a surefire sign that you are doing TDD incorrectly.👇


Darren Cauthon Reposted

Please seriously consider learning how to practice TDD properly. That way, if anything doesn't work as intended, the failed tests will tell you exactly what went wrong. Tests are our best debugging buddy.


It’s the first thing I do to every new computer.

i don’t trust an engineer that doesn’t have caps lock mapped to escape



I always loved going up to @iowacodecamp, it was a great dev vibe. I only stopped going when I started having a billion kids.

I'm so happy to be able to support this great community (via delt3consulting.com)! Thank you for keeping all the good stuff going @iowacodecamp! Your work makes a difference.



It’s really frustrating to read some criticisms of Civet. It’s not just saving a few characters - it’s a different perspective that would benefit any dev gives it a try. civet.dev


Your last act on Friday… write the next failing test. It’s like a rocket on Monday.

😂😂

Tweet Image 1


If your tests seem outdated, I recommend running them.

Tests are like documentation, it gets outdated pretty fast.



Haha!

Tests are like documentation, it gets outdated pretty fast.



Main difference: Chance that it’s covered with tests. Test for null 🟢 Test for null and empty 🌕 Test for null and empty and 1 white space 🔴 If you play that game where you see if you can break production code with tests still passing, start with these methods.

Are you using IsNullOrEmpty or IsNullOrWhiteSpace? You'll be SHOCKED what the difference is. A thread 🧵👇



Darren Cauthon Reposted

🚨BREAKING: #Ravens QB Lamar Jackson says Isaiah Likely’s catch was a TOUCHDOWN and Baltimore should’ve really won the game. “I thought it was a touchdown. I still think it was a touchdown…” (🎥@arimierov)

From 1-1-1-1

Life before TDD

Debugging one step at a time 🙈

Tweet Image 1


Darren Cauthon Reposted

Why do software professionals always assume that there will be debugging? Most of the time, if teams switch to doing TDD, they leave debugging behind them.


Darren Cauthon Reposted

SETI at Home felt like the future

Tweet Image 1

I used to be in this camp, but the truth is: the only time you need to go into git history, you need devs to get-to-the-point. The decision to merge is that point.

Please don't squash commits. You're throwing away data when you do that. If you want a 'pretty view' of history, you can always pretend to throw away data when it pleases you, e.g. git diff commit123..commit456



There is no such thing as a “natural programmer.”

me not writing unit tests

Tweet Image 1


I love AutoMapper. It has saved me a lot of code, as I used it to conventionally convert bigger things to smaller. I hate AutoMapper. I’ve worked in so many codebases where devs use it to turn small things into walls of lambdas that are harder to read than XML.

Damn this is crazy

Tweet Image 1


Hahah this made me LOL! Thanks, have a great weekend

Tweet Image 1

Clean Architecture is bad for small projects, but worse for large ones I haven't read the book and I don't know what it actually says, but the things that creep into CA codebases are layering, mapping, abstractions, and pointless unit tests Large CA codebases are unmaintainable



Sorry, but this is user error.

I was forced to use vscode for something and while I'm typing THREE boxes popped up. How is this possibly useful to people?

Tweet Image 1


EF all day. From someone who used EF pre 1.0 in production, who loved Dapper and Simple Data for years… EF has closed the gap, it would only be the most extreme cases to go with others.

What's your experience with Entity Framework vs Dapper? Which do you prefer for data access, and why?



Loading...

Something went wrong.


Something went wrong.