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? ...

From crappy to happy - refactoring untestable code - an introduction

I started testing my code automatically a couple of years in after starting my career. Working in a small company, there weren't really incentives for us to automate testing and we were not following any kind of best practices. Our way of working was to write the code, test it manually and then just Release It ™ , preferably on a Friday of course. I'm sure everyone can relate to this at some point in their career, because this is a lot more common than the Almighty Programming Gods of the Internet make us believe. I find that the amount of companies that actually bother writing tests for their production code is a fraction of the whole universe. I know some friends who work in pretty big companies with big names in the industry and even there the same mindset exists. Of course, at some point in time our code turned into a big pile of shit . Nobody really knew what was going on and where. We had quantum-level switcheroo that nobody really wanted to touch, and I suspect it i...

My simplest and most useful type

I have been doing some introspection on the way I write code to find ways that I need to improve. I consider this a task that one must do periodically so that we keep organized. There is a very, very simple problem that occurs in every application I know: How to return the results of an operation to the user? I've seen many implementations. Some return strings, some throw exceptions, some use out parameters, reuse the domain classes and have extra properties in there, etc. There is a myriad of ways of accomplishing this. This is the one I use. I don't like throwing exceptions. There are certainly cases where you have no choice, but I always avoid that. Throughout my architectures there is a single prevalent type that hasn't changed for years now, and I consider that a sign of stability. It is so simple, yet so useful everywhere. The name may shock you, take a look: Yes, this is it. Take a moment to compose yourself. Mind you, this is used everywhere , in every ...