I recently skimmed / read this article. It is written by someone who has 25 years of experience in the field and 18 of those at Microsoft and currently operates as a Software Architect. It is not always relevant, but in this case I found it to be so.
I recently ran into the unsolvable issue that if you ran an npm audit on a React or Angular framework project, it would give back an error because of this CVE. Now the solution was to go to a lower dependency for one of the scripts, but that lower dependency had other high vulnerabilities and so you were in an endless cycle and could not fix it.
Recently I got the experience of using Docker on Windows Server to actually deploy a production running service. It was a fun experience for sure. I ran into three things that made it worthwhile to write down for posterity.
I have gotten some experience using the Flow constructs in a real scenario and learned some lessons. Therefore I wanted to make some code changes to my original design.
So I recently started using Spring WebFlux and Project Reactor as stated in this post. One more thing I came across as I was debugging why a certain job was not running was that if you do not catch all exceptions and do not have a doOnError statement it will just keep that thought hidden from you and all to itself.
I started a project recently using Spring WebFlux which is based upon Project Reactor. I chose this one because it was new and I thought for the client it would suit the best as a lot of data was involved.
So I was watching something the other day, a fantastic speedrun of Yoshi's Island, and someone used a pronoun that I never heard of. I only saw it written and it was xe/ve. I tried to get the pronunciation of that, but I could not find it easily.