Autore: Maurizio Pozzobon
Maurizio has 5+ years developing solutions in the insurance industry. He is passionate about doing the right thing right, so he works in a tight loop with his clients to deliver the best solution possible.
Testing your sharepoint repositories
In this article we will see how to test your sharepoint repositories, as we said before writing unit test for them isn’t easy. I don’t think you can test drive them or that it would help, at the very least Read More …
Repository Pattern
If you have ever heard of software design patterns, you have heard of the Gang of Four and their book. It’s the bible on this matter and it would be a disservice not to reference it, but the pattern we Read More …
How to test in sharepoint
We have talked about how to set up your test environment, how to write tests and what to do with the freedom that the test give you (write code that is clean). Now we start to get into the nitty Read More …
Clean Errors – Clean Code
If you write feature code, you also have to write error handling code. There’s no clean code without clean error handling, if you don’t do it, your user has to deal with it in the form of your application crashing. Read More …
Clean Formatting – Clean Code
You just need to have a look at any minified JS file to realize how important proper formatting is.I don’t think any one would be able to program a whole system constantly minified, but most don’t give a concerned effort Read More …
Clean Comments
One of the most interesting things I’ve found out about people arguing on the internet is related to code comments. Every time there’s an article about how to properly comment code it is followed by a heated discussion in the Read More …
Setting up NUnit 3 in Visual Studio 2013
Setting up NUnit 3 in Visual Studio is a simple task, but if you don’t know what you need to do, there are a few ways you can easily get stuck. To help you avoid loosing time I put together all the steps you need Read More …
Clean Functions – Clean Code
Now let’s take a look at rules that give you clean functions. First off, your functions should be smaller than you think. Many people recommend functions of 20 lines, probably referring to the old times when that was how much Read More …
Stop writing legacy Code – What’s Clean Code
If you want to stop writing legacy code we have seen the importance of doing TDD, because it let’s you refactor your code and improve it. Well, actually refactoring lets you change your code, modify it. To actually improve it you Read More …
Clean Names – one of the hard things
There are only two hard things in Computer Science: cache invalidation and naming things. Phil Karlton Today we are talking about the second of the hard things, luckily this is the one you can keep on improving with ease. I’ll Read More …