This post is an attempt to predict what the following decades will look like. I wrote a more technical post about this 3 years ago, which still makes sense far as I’m concerned.
Somehow, my understanding about how this applies to non-software things has evolved, and after trying to make my point on twitter, I decided to elaborate in this blog post about my assumptions on the future.
I’m only slightly aware about “the how” of the technology that could drive these things. My assumptions are purely based on my observations about how people interact with devices and technology at this very moment.
I would definitely say the past decade has been all about knowledge economy, i.e. the democratization of knowledge.
Knowledge used to be something people used to consider exclusive. In the world of today, people no longer consider knowledge something exclusive, as almost everyone can search information about almost anything on the internet. One could say, that it is no longer valuable what people know, but what makes the difference is how people apply and combine that knowledge.
As knowledge is becoming a commodity, people are starting to share knowledge, others improve it and publish their conclusions. One could say that the speed by which we learn is growing exponentially, just because we can share it and get feedback in a way people from a few decades ago could not even have imagined.
As the Mrs. does not allow me to take the laptop on vacation, but we do take the tablet with us, I decided to find out whether Elixir runs on an Android tablet.
I experimented for about an hour or so, and apparently it is quite easy. Here is my proof:
With a lot of unicorns and fairydust… No, actually it is quite simple….
People following me on twitter noticed I got entangled in yet another new language for the Erlang/BEAM VM:
Elixir could be easily described as “ruby for the BEAM/Erlang VM”. In previous posts, I mentioned why people should learn Erlang, but in fact, I think most people might be better off when they skip Erlang and opt directly for Elixir. It has all the advantages of Erlang, but offers a Ruby-like syntax, macros, polymorphism and more.
As someone else made a perfect blog post on why you should learn Elixir, I will not elaborate further on it in this post. Read his post; the info is all there.
In this post, I will show you how to get started with Elixir and generate a template website using the Dynamo web framework.
Installing Elixir is simple, but because one of the Dynamo web framework dependencies requires the make tool, you need to do some extra work. If anybody finds a better/simpler way to do this, please let me know in the comments.
A little while ago I wrote a post the fallacies of the tech recruitment process. While it is nice to point out what is wrong, I never actually provided the proper way to find out if a senior developer might be experienced enough and the right fit for your company, so this time I decided to put my money where my mouth is, and tell you how to hire a senior developer.
In my opinion, a senior developer is a developer who manages to think out of the box, and who does not stop reasoning about finding a solution at technical boundaries. A senior developer is somebody who tries to provide business value for every single step he makes, while a junior is more or less focussed on implementing the whole thing, a senior thinks about what he has to do and why he has to do it…
The last two days of August there is a 2 day Erlang course in Amsterdam. One of the most incredible things, is that there is a low cost offer sponsored by Spil games that reduces the price to 55€ for both days; talk about a steal!!
People who know me in person know that I am an avid fan of Erlang, even though I have only done some very small experiments with it.
Even if you are not planning on developing something in Erlang, you should at least try to grasp the basic concepts!!
You want to know why? Here is why:
Implementing Domain-Driven Design is a book written by Vaughn Vernon, and you can consider it a practical guide to the blue book - a lot of people consider the blue book to be used as a reference, but it takes some persistence to read it -. Vaughn tried to solve exactly that problem with his book…
A little while ago, Vaughn Vernon was tweeting about how had given a free course about his book “Implementing domain driven design” while visiting Bogota, Columbia. This course was given for free to help start-ups there.
In the next few hours after this tweet, an idea emerged on twitter about a concept called the IDDDtour, where Vaughn would be teaching his book to larger classes and doing a tour through Europe, but at a fraction of the cost. As I am somebody who is more of a head first kind of guy, I decided to take ownership and figure out a way to make this a real thing…
As I was wide awake at 5am this morning, and it was the end of the month, I decided to do some invoicing (while the Mrs. & kids are still asleep ;) ).
Because I had some time left, I decided to take a look at my stats… This invoice app was built about 10 years ago in MsAccess in a few days, and has not really changed a lot since then (except for some adjustments to allow certain billing specific extents; things like non-EU or VAT-exclusive stuff, as well as some automated payment reminder letters).
Anyway, that is not the subject of this post, but as I was browsing some of my available graphs - it has been a few months since I did that - , I decided to write a small blog post about my findings.
I will start of with what most of you will probably consider quite a controversial thing; I will just post a slightly censored graph of my invoices cumul over my years as a company owner. ..
LOL, that looks odd…