Skip to main content

Introduction

Introduction

My name is Mário Constantino, i'm Portuguese and i love what i do.

I work as a junior developer at a small company for 2 years-ish now. This is where i started my career, so i'm still young and have the enthusiasm that comes with the age :) Our primary area is the development of ERP software in .NET technologies interacting with SQL. This gives me a little experience, but i'm far from an expert in the area, although i'm learning a lot each day.

Blogging is a new experience for me, so you'll excuse me if i make some rookie mistakes. I've been on the internet since i can remember, but only on the consumer side, never on the producer. Well, for what it's worth, now i'm going to start to produce blog posts!

But first, English is not my primary language, and some typos are in order. If you catch one, please tell me in a comment. I'm Portuguese, but i thought that by making the posts in English i would get a broader audience. Also, the kind of stuff that i plan to talk about is best understood when spoken in the Common Tongue (Game of thrones anyone?)

The context

One of my main concerns at work is "how can i solve this problem in a faster, better and more maintainable way?". I'm sure every one has had the same concern in his/her head, and if you're like me, you wont rest until you get an answer. Sometimes you see a pattern of code repeating itself and wonder if you can produce a reusable solution, right? Or maybe you're just looking for cool hidden features of the language?

Well, to be honest, i'm hardly going to teach anyone anything new that you can't find on Stack Overflow, but i like to learn new things, i like to write, and i like to teach! So, from here on, i'm going to post here some useful stuff that i myself find in the internet or discover during work. I'm going to talk about tools that help me on work, features of the VS IDE, the .NET Framework, but mainly about C#. For now, C# is the only language i know, that and T-SQL. But i can post some things about OO design concepts, Design Patterns, WPF, Entity Framework, Moq, Ninject, NBuilder, Unit Testing, Dependency Injection and other subjects that i may wish to write about.

Please don't expect too much because, as i said, i'm not an expert like Eric Lippert, Martin Fowler, etc. I certainly am not an above average programmer, not yet at least! I wont write about super advanced techniques or algorithms, nor about great mathematics concepts, no...  I can always take suggestions on subjects for posts, or about the content of an existing post on comments!

Apart from that, occasionally i can post some random stuff that i find in the internet and want to share with others, like a funny video or whatever.

The objective

I'm not really expecting to have any viewers, or even followers. For all it's worth, i'm just doing this for the kicks. All i want is to have some fun and help others solve problems or make their problems easier to solve. We learn when we teach, so, let's see what happens from here on.

Thanks!

Comments

Popular posts from this blog

The repository's repository

Ever since I started delving into architecture,  and specifically service oriented architecture, there has been one matter where opinions get divided. Let me state the problem first, and then take a look at both sides of the barricade. Given that your service layer needs to access persistent storage, how do you model that layer? It is almost common knowledge what to do here: use the Repository design pattern. So we look at the pattern and decide that it seems simple enough! Let's implement the shit out of it! Now, let's say that you will use an ORM - here comes trouble. Specifically we're using EF, but we could be talking about NHibernate or really any other. The real divisive theme is this question: should you be using the repository pattern at all when you use an ORM? I'll flat out say it: I don't think you should... except with good reason. So, sharpen your swords, pray to your gods and come with me to fight this war... or maybe stay in the couch? ...

Follow up: improving the Result type from feedback

This post is a follow up on the previous post. It presents an approach on how to return values from a method. I got some great feedback both good and bad from other people, and with that I will present now the updated code taking that feedback into account. Here is the original: And the modified version: Following is some of the most important feedback which led to this. Make it an immutable struct This was a useful one. I can't say that I have ever found a problem with having the Result type as a class, but that is just a matter of scale. The point of this is that now we avoid allocating memory in high usage scenarios. This was a problem of scale, easily solvable. Return a tuple instead of using a dedicated Result type The initial implementation comes from a long time ago, when C# did not have (good) support for tuples and deconstruction wasn't heard of. You would have to deal with the Tuple type, which was a bit of a hassle. I feel it would complicate the ...

C# 2.0 - Partial Types

For those of you interested, i found a very interesting list of features that were introduced in C# in  here . This is a very complete list that contains all the features, and i'm explaining them one by one in this post series. We've talked about  Generics  and  Iterators . Now it's time for some partial types . A partial type  is a type which definition is spread across one or more files. It doesn't have to be in multiple separated files, but can be. This is a very simple concept that can give us many benefits, let's see: If a type is partial, multiple developers can work on every part of it. This allows a more organized way of working and can lead to production improvement.  Winforms , for example, generates a partial class for the form so that the client can separately edit other parts it. This way, a part contains information about the design and the other contains the logic of the form. In fact, this is a very spread pattern across .Net. Ent...