Software developers (and not just them) quite often believe that remote work is one of the best things that can happen during their career. Sitting at home or even better, laying on the beach with a laptop on your knees, while drinking some fancy beverage and of course coding from time to time (you’re not at the office anymore, therefore your boss ain’t gonna observe what are you actually doing) pictures like a some kind of dream. But is it really like this?
Many of us, and I’m not speaking just about folks within the IT industry, sometimes have this feeling about the missed opportunity. It might be related to the job, some project or anything else that somehow we didn’t manage to accomplish due to some specific reasons (maybe just a bad luck or even the laziness). However, sometimes missing a particular opportunity doesn’t mean that the world has come to an end, actually, it might turn into something even better and unexpected.
In case you’re not familiar with the Warden project that I’ve been working for the last few months, I strongly recommend you to take a look, as you may find this tool especially useful for monitoring your infrastructure and resources. So what is the Warden Spawn?
It’s a brand new repository within the Warden Stack that will let you configure the instance of the Warden monitoring application using the human readable configuration files – and that’s just the beginning!
There are many ways to perform a validation of our models living within the system.
Whether there’s an incoming request from the user who would like to create an account or there’s a need to ensure about the correct amount of money in a bank transaction, the validation process should always (I really mean that) take place. In today’s post, I’d like to present one of the possible solutions that might help you validate your entities.
Although I’m not a big fan of the Autumn (usually a cold weather, rain, not too enjoyable environment to ride a motorcycle and so on), there’s at least one nice thing about this part of the year – a lot of great IT conferences. And one of such is the .NET Developer Days – probably the biggest conference related to the .NET technologies in the whole eastern part of the Europe.
Last time I wrote a post about the commands. Events are quite similar to the commands – the main difference between these 2 patterns is that the events are related to the things that have actually happened to our entity e.g. by invoking the command. They’re also a core part of the DDD (Domain Driven Design) and can be easily implemented within our software solution.