PlantUml
Lately, I’ve started to use PlantUML.
If you are like me and prefer keyboard over mouse and want to be able to properly version-control your UML diagrams, then you should definitely check this out.
Lately, I’ve started to use PlantUML.
If you are like me and prefer keyboard over mouse and want to be able to properly version-control your UML diagrams, then you should definitely check this out.
I just stumbled across an article about a new addition to the BCL, the System.Threading.Channels
namespace.
The new API is very useful in certain situations, but I’m even more happy with the article itself - I really highly recommended it for anyone who likes to think about threading related design (or to learn about such).
There’s an update out for renameproject
. This is a bit of a bigger change in how you control its behavior. See here for details, or just update it with
When developing against REST APIs without dedicated client libraries, I very much like to use Flurl.Http, because it makes it pretty easy and intuitive to test your code, also under several error conditions.
I’ve been using the marvellous FluentAssertions library for many years, yet I still discover useful details I had not been aware of.
Recently, I found myself for the first time in my 25+ year career needing infinite iteration over a finite set of elements.
The context was generation of examples. For certain data types, there is a finite set of constant example values provided, but the actual number of values that will be
required are not known beforehand.
Today I stumbled across a strange omission in netstandard2.0: the HttpStatusCode
enum is incomplete (as opposed to, say, the netcoreapp3.1 version). For example, it does not contain a label for 422 (Unprocessable Entity).
A dev-friend was unhappy about not being able to exclude certain code passages from R#’s cleanup/formatting feature.
Actually, you can:
1 | // @formatter:off |
There’s an update out for renameproject
, just a bugfix release. See here for details, or just update it with
Another interesting article, this time something for younger folk (careerwise). With my 25+ years of experience, I can say that I agree with everything the author says.