Tag: c#

Whenever someone posts anything related to the Go programming language on Hacker News, it never takes long before someone complains about error handling. I find it interesting because it is exactly one of things I like the most about Go. I don’t want to specifically talk about error handling though. I want to talk about…

I’m back from a trip to a customer. How was it? Okay. I got more snow that I expected on the way there, so the drive wasn’t much fun. Then again, a part of the trip goes through a beautiful forest that was worth everything else. Cool! Also, while showing the customer a new feature,…

Mads Torgersen wrote a blog post highlighting what’s new in C# 7.0: C# 7.0 adds a number of new features and brings a focus on data consumption, code simplification and performance. The changes all seem to be in line with the recent trends of borrowing syntax sugar from other languages to C#. Nothing wrong with…

I wrote about how the Go and C# compilers implement interfaces and mentioned how C# deals with clashing method names but I didn’t talk about how Go does it, so here it is. Two interfaces with the same method name that need to behave differently is very likely a sign of bad API design and…

I make no secret of the fact that I love Go. I think it’s a wonderfully designed language and it gave me nothing but pleasure in the years I’ve been working with it full time. Now however I am working on a project that requires the use of C#, which prompted me to realize something….

The recently approved C++11 standard brings a lot of welcome changes to C++ that modernize the language a little bit. Among the many changes, we find that containers have received some special love. Initialization C++ was long behind modern languages when it came to initializing containers. While you could do [cpp]int a[] = {1, 2,…

So I recently wrote an ugly solution to Project Euler’s problem #9. It was written in Python and even though every other Project Euler solution I wrote ran in less than one second, this one took over 18 seconds to get to the answer. Obviously it’s my fault for using a purely brute force algorithm….