pairing
Joined 14 years ago
Joined 14 years ago
B) Living Clojure
Any way to woo the customer back? Show up at their office tomorrow morning and convince them to stay or at least keep some of the account with you? Maybe convince them to give you a bit of a window? They might have no idea that leaving your company will cause your company to fold.
The path to mastery is mostly self learning in my limited experience in software so far, so the earlier you learn that and build the skills to learn on your own the better off you will be. Learning on your own without a teacher, grades, mentor, or internship will prepare you more for the real world than most college students.
I'm glad to see they've received more funding. In the south bay at least, doordash far exceeds the competition for the variety of restaurants they offer.
The startup class talk by one of the founders was also quite good.
Based on your post, I think going to a bootcamp would be a mistake. I think you're buying into the hype a bit too much. The career changing job comes months after the bootcamp finishes from the people I've talked too. The bootcamper job market is oversaturated and much more competitive for an applicant which results in a long job search.
If your bored at your current job, start looking for a new job where you can learn something that interest you instead of a bootcamp. You'll be earning money instead of giving time and money to learn entry level skills.
Frameworks: Rails / AngularJS / Cordova
DB: Postgres / Redis / Elasticsearch / Memcached / DynamoDB
Messaging: SQS
Plan on learning in the next few months:
More Clojure
Machine Learning
ReactJS (Hopefully a replacement for AngularJS / Cordova from above)
I've been picking things to learn based on reading programming books and observing trends. 7 concurrency models in 7 weeks, 7 languages in 7 weeks, and 7 databases in 7 weeks are all good places to start for finding something new to learn. As you can tell, I'm a big fan of the series as an introduction to a topic that can then be explored in more depth after reading.
Back End: Ruby, learning Clojure
Databases: Postgres, Redis, Memcached, ElasticSearch
You can do token authentication, basic authentication, OAuth, OAuth2, or even roll your own. For a rails api <-> angular combo, I usually stick to token or OAuth 1/2 authentication.
I have open sourced an angular application (technically ionic but it uses angular under the hood) and the rails api that it uses as a backend which uses token authentication. https://github.com/johnkelly/mojave https://github.com/johnkelly/kalahari
So if you are an AWS user for example and want to be in multiple availability zones the Elixir distribution model will not scale and you'll have to use the same techniques and tools other languages use for distribution.
With that in mind, I think the whole distribution buzzword is way over hyped since the majority of companies will be leveraging cloud platforms like Azure, AWS, Google Cloud, etc.
I write Elixir code daily because it's an awesome language to write in and not for the distribution features.