Before reading this post - note that when I say "resolving", I'm only talking about clicking the "Resolve" button for that particular comment thread. I am not talking about actually fixing the issue that the comment is describing.
TLDR; - The term "100x Development" is better because it focuses more on the nature of software development, not an individual. And the 10x is just too small of a multipler.
Last year, whilst browsing the web on my phone, I learnt something that blew my mind. I can't remember exactly what (or why) I googled about 'visualisations', but some of the results said things like "Did you know that some people can't see images in their mind's eye?!". I read that, and thought - "Wait? What! Some people can?!".
It's New Year's Eve, and I've just remembered that I haven't done a 'year in review' blog post this year - so I'm quickly knocking this out now! In fact, I'm sorry to say, I haven't blogged much at all this year - with my primary focus being on the podcast. This will only be my second blog post of the year! Hopefully, the podcast content makes up for the lack of blog content! So let's start with that...
This year has obviously been a lot different than everyone expected. I feel extremely fortunately and lucky to be in an industry that naturally makes it easy to work from home. In fact, remote work is something I've wanted to try full-time for quite some time, and this year has not only forced it to happen, but also made it more normal in our industry (hopefully now moving forwards). It's just a shame it took something so terrible as what's happening for this to become a thing.
I have some exciting news! As you may already know if you follow me on Twitter, I've recently started my very own podcast!!
As an industry, we spend far too much time sat down. A quick Google search will show plenty of research suggesting that this is very bad for you in many different ways. I've very recently invested in a standing desk, and thought I'd share what led up to me buying it, which one I chose, and also my initial experiences using it. This will be a 'part 1', with a follow up in about 6 months.
How many times have you been working in a Git feature branch, and come across something in code that you want to change, but isn't related to the feature your on? Perhaps a code tidyup, or fixing some unrelated warnings?
There are quite a few different mocking libraries in .NET. Moq and NSubstitute seem to be by far the main ones I hear that developers use. I've used both of these in different projects, and really like them both. Whilst my preference leans towards NSubstitute, I'd be happy using either. Out of interest, I posted a Twitter poll to see what other people preferred, and the results and replies were really interesting!...