For what it is worth, I noticed this too and think quite a few people, like myself, had read your initial post and jumped to the gun. It would have been nice if you had elaborated a bit more to boot.
But fine I hear what you have to say but then it leaves me to guess. Leading up to the time that you started this job, where you were gaining experience with various technologies. What did you do in this time, what have you developed that you could show to a potential employer? Anything in active use today? Many something that people are making use of?
See the thing that I noticed is the lack of the word scalability in the blurps that you have given. It seems that you may be a little more book smart than street smart as the other guy might say.
As I see it, there is a grey area here and from this point onwards you have had mediocre experience with a company that you have said yourself does not seem to be doing things in a very progressive way.
I am just saying but by that point in their career, many of the web developers that I know who are around 6 years in experience have a whole lot to show (many things online and in use by various companies or running companies off of their ideas, etc) for the time that they have spent over the years that they have been gaining experience. This is their working experience so... Logically thinking, how did you get them skillz bro?
First the lack of the word "Scalability". I read through some of my posts and don't think I see where I could use the word. The closest I could get is:
...have a project I completed 2 years ago that makes use of elasticsearch and memcached. I did not use Redis because I was not using any of its feature and at the Redis cluster was not ready yet.
But even here, it's all about avoiding getting these from Postgres. It's more about a faster response with memcached than scaling. I think learning Elixir now is how I am approaching the scalability problem. Of course there are other ways vertically and horizontally but now is my chance to learn Elixir by building something with it. My personal experience is a very long story but from my high school days I wanted to make website that everybody would use like.... "Facebook". It's deviated from that but from I have a system I build on my own time and have done so for close to 6 years now.
That system has changed so many times:
- it started as as spaghetti PHP
- then after about 15 rebuilds and growing each I started to use my own custom built MVC
- then I realised that's a bad idea and tried codeigniter followed by symfony2
- then in 2014 decided on Laravel but used Rails to learn MVC better since it had more books
- Ditched Laravel by sticking with Rails, in the same year I clicked the "angularjs" tag for the first time on stackoverflow
- while learning angular I was introduced to grunt and live-reload later replaced by gulp and browser-sync
The thing started out as a simple blog that people can post on and has become a Learning Management System. I noticed it was to bundled together with all the features so now the idea is to break it up. The early version were influenced by stackexchange. I took it offline in February 2015 when it cost be over 1k to put it online. I am still working on it today and hope that I will finish it. Of course it's going to be rewritten in Elixir now with a React frontend.
I also watch a lot of conferences and talks on youtube. I watch a lot of talks on a technology before I take time to test it and some of the things I have liked.
I like this project I am working because I get to learn things with it and it has done plenty to my programming ability. I could go in more detail but this will just get too long. I am more concerned about quality and writing something that will scale than writing a lot of websites.