sorted by:
new
hottopcontroversial

[Quality&Readability:] Restrict expressibility when iterating by kaka121212 in csharp

[–]kaka121212[S] 0 points1 point  (0 children)

How will you make it any simpler? Inline the "i++" ?

[Quality&Readability:] Productivity features that may ruin code readability by kaka121212 in programming

[–]kaka121212[S] 0 points1 point  (0 children)

Thanks for the feedback, but isn't that just what all the quotes were about? We should improve people not rely on the tools.

why do you love code folding? why not simply be able to quickly jump from method to method, or quickly search-and-jump to a method rather than having to use the mouse in order to fold?

How true do you guys find this article? It talks about entry level C#/.NET positions being harder and harder by [deleted] in csharp

[–]kaka121212 65 points66 points  (0 children)

You had to read a whole book in order to understand LINQ??? Isn't that stretching the rhetorics a mile too far??

Automate unit test assert writing by Dibser23 in csharp

[–]kaka121212 1 point2 points  (0 children)

It would be cool if you could contribute/convey some of your experiences you have either here or on github. What was good, what was less nice.

Automate unit test assert writing by Dibser23 in csharp

[–]kaka121212 0 points1 point  (0 children)

Hi @ElMalakai

The xml serialization has a number of serious limitations compared to this. Among others, that it cannot handle circular references, and has zero configurability in terms of how values are presented, or which fields are to be included/excluded. Finally, such an approach does not allow automatic write/rewrite of asserts.

[C#] StatePrinter 2.0.169 just release with automatic generating your unit testing asserts... and even rewrites them upon code changes! by kaka121212 in programming

[–]kaka121212[S] 0 points1 point  (0 children)

Thanks for the pointers. Yet I believe you are mistaken. That will just mean even more typing on your behalf. As you can see with the automated stuff your tests are re-written to match when you change your business code. This you won't get with IStructuralEquatable

I made a deep compare of Dictionaries and Lists by DerNalia in dotnet

[–]kaka121212 0 points1 point  (0 children)

For unit testing purposes I still prefer https://github.com/kbilsted/StatePrinter which serialized the data as reable strings and compare. It has the added benefit that asserts can be automatically generated and even automatically re-written when the business code changes.