It is a fast and dynamic world we are living in these days and as some of you may have noticed, I have a new job as of recently. I decided to become a consultant, and I could not think of a better place to pursue my career forward than tretton37. It seems that we are a perfect match. I have had more than a warm welcome since I started and everyone seems so nice. I already feel at home here. I decided to devote this article to tretton37. So, if you want to find out more, read on…
We are a knowledge-based company that helps our clients achieve their goals by delivering customized & well-crafted software solutions, utilizing primarily .NET platform with help of agile and lean development methods.
Every day thousands and thousands of developers fight stress, anxiety, deadlines, pressure, guilt, hard work. They give their everything so that they make the world a better place….These are their stories…
Whatever you do in the .NET framework deals either with value or reference types, yet, there seems to be a great deal of confusion in many discussions with fellow developers and on online forums and QA sites about where the actual variables reside. It is so basic yet a cause of so many misconceptions. For example one of them is that value types reside on the stack and that the reference objects reside on the heap. We will try to break up some of those misunderstandings by carefully examining and explaining what really happens(with the current implementation of the .NET runtime, which at the time of writing is .NET 4.5.1)
Before we dig deeper into this issue I just want to say that this is by no means a comprehensive guide to how types are handled in the .NET framework. It would take a whole book on that. I’m simply trying to create a nice picture and get a few things clear as a general concept by working the foundations and trying to create a picture of what is one possibility of what happens behind the scenes down at the deepest level.
When our projects reach a certain size it is very hard to determine the complexity of our code. It gets harder and harder to see the overall picture. It also becomes very easy to introduce unnecessary complexity to parts of our system that we don’t want to. In simple words, it’s easy to get lost. Especially if there are may people working on the project.
On top of many other tools, practices and principles like unit tests, integration tests, acceptance tests, continuous integration, it is static code analysis tools like NDepend that come into play.
There are several ways to find a stored procedure in the server by name: we can query sys.procedures, syscomments, or information_scema.routines. Respective examples would be:
select * from sys.procedures where name like '%name_of_proc%'
select text from syscomments c inner join sys.procedures p on p.object_id = c.object_id where p.name like '%name_of_proc%'
select * from information_schema.routines where routine_name like '%name_of_proc%'
Software Developer, a “Programmer” even an “Engineer” or a “Craftsman“, although there are substantial differences between these according to some people, when we say any of them we mean one thing….an organism that transforms coffee into code 🙂 so I will continue with the term “Developer” and I wouldn’t like to go into that discussion right now because it can turn out to become a book.
We have come a long way from being the “basement” nerds, that nobody wants to talk to, to the modern day mixed media served image of super-rich-enterpreneur-programmer(which is sadly just a few lucky ones). So where is the truth? What are we, where are we? How do we manage to form a picture of ourselves and waht we want to accomplish in todays diversity of technologies and approaches to software development?
I know it maybe not much. But, having been there for quite a while both as amateur since I was a little kid typing random programs in Basic on my Commodore 64 back in the 90’s, then professionally since 2005, all the way until today. I will try to share my view and experiences of what I consider the most important values of a modern day developer by answering dozen of questions.
So, here we go.