Programming

17364 readers

152 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

What are your programming hot takes? (lemmy.ml)

submitted 1 year ago by 257m@lemmy.ml to c/programming@programming.dev

96 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Vince@feddit.de 5 points 1 year ago* (last edited 1 year ago) (1 children)

Not sure if these are hot takes:

Difficult to test == poorly designed
Code review is overrated and often poorly executed, most things should be checked automatically (review should still be done though)
Which programming language doesn't matter (within reason), while amount of programming languages matters a lot

[–] Xylight@lemmy.xylight.dev 1 points 1 year ago

I've been wanting to make my applications easier to test. The issue is, I don't know what to test. Often my issues are so trivial I notice them immediately.

What are some examples of common things in, let's say a web server, that could be unit tested?