All languages, or at least most, have some way of passing a value by reference. When we wish to return more than one values from a method or simply if we want to use the classic value swap paradigm then we need to pass values by reference to our method. C has pointers (which in fact you are still passing the pointer to your method by value, but in fact that pointer has a reference to the variable you want to change) Visual basic has the ByRef argument and many other languages have their own way of doing this.
Continue reading Out vs Ref in C#
A huge pain in the arse for most developers is the need to null check everything before starting to use it. Microsoft has introduced null operators in previous versions of C# and upgraded them in C# 6.0 but still, we can and we should avoid them.
How? Well by avoiding nulls altogether.
Can we do that? Of course we can.
Let’s see how
Continue reading Checking for nulls? Not anymore
For some time now developers wanted to catch multiple exceptions in a single Catch statement in order to not repeat their code in multiple catch statements. This was not available in previous releases of C# and developers used different workarounds to achieve it.
Continue reading Capturing Multiple Exceptions in a single Catch statement in C# 6
We all know what spaghetti code is. For those of you that do not here is a small description by Wikipedia.
Spaghetti code is a pejorative phrase for source code that has a complex and tangled control structure, especially one using many GOTO statements, exceptions, threads, or other “unstructured” branching constructs. It is named such because program flow is conceptually like a bowl of spaghetti, i.e. twisted and tangled. Spaghetti code can be caused by several factors, such as continuous modifications by several people over a long life cycle. Structured programming greatly decreases the incidence of spaghetti code.
That’s cool and all but what the hell is Lasagna code? Continue reading Pitfalls of Lasagna Code
In programming jargon, Yoda conditions (also called Yoda notation) is a programming style where the two parts of an expression are reversed from the typical order in a conditional statement. A yoda condition places the constant portion of the expression on the left side of the conditional statement. The name for this programming style is derived from the Star Wars character named Yoda, who spoke English in a non-standard syntax.
Continue reading Usefulness of Yoda expressions in programming
First of all you must understand something. As a Software Developer you will never know enough, you will never be ready for what is coming. Something will always pop up and someone will always know stuff you do not know. This is the life of a Software Developer and this is how it will always be.
Continue reading Surviving the world of Software Development
Java is a general-purpose computer programming language that is concurrent, class-based, object-oriented, and specifically designed to have as few implementation dependencies as possible. It is intended to let application developers “write once, run anywhere” (WORA), meaning that compiled Java code can run on all platforms that support Java without the need for recompilation. Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of computer architecture. As of 2015, Java is one of the most popular programming languages in use, particularly for client-server web applications, with a reported 9 million developers. Java was originally developed by James Gosling at Sun Microsystems (which has since been acquired by Oracle Corporation) and released in 1995 as a core component of Sun Microsystems’ Java platform.
Continue reading Java Sucks, and here’s why