05 April 2018
Many years ago there was a site with collection of Ruby Quizzes: http://rubyquiz.com.
What Is Ruby Quiz?
Ruby Quiz is a weekly programming challenge for Ruby programmers
Idea is superb. So, I have decided to look around and collect here similar resources:
The current list is not very impressive. But, I am going to maintain it and I hope it will be bigger.
15 March 2018
REST API is the most popular interface for communication between different component of the system. There are a lot of different common sense approaches to design RESTful API. Despite this fact it is always better to have something written as a reference to follow common principles during API design of the system.
Here I have collected some REST API guidelines and API References. It’s nice start point for your inspiration.
Microsoft - REST API Guidelines
Microsoft - Best Practices - API Design
Zalando - REST API Guidelines
Paypal - REST API Guidelines
Atlassian - REST API design guidelines version 1
Digital Ocean - API v2 Introduction
Google Cloud Platform - API Design Guide
Red Hat Lessons learnt from designing the Red Hat Enterprise Virtualization API
Australian Government Agencies - AusDTO API Design Guide
Cloud Foundry - Cloud Controller API v3 Style Guide (Proposal)
Heroku - API Design Guide
Also, Apigee provides huge list of different API providers in one place: https://apigee.com/providers
05 November 2017
I’ve been listening podcasts for many years. Mostly (99%) technical podcasts. Here is the list in my favorite order (Please note, some of them are not in English)
(RUS) DevZen: Very interesting. It covers broad range of different technical topics
(RUS) Scalaz Podcast: Podcast about Scala
(RUS) Radio-t: Tech podcast. Sometimes might be boring because it has a lot of blaming and trolling
(RUS) GolangShow: only #Golang, only hardcore
(ENG) The Ruby Rogues: broad range of topics, not only #Ruby
(ENG) Functional Geekery: A podcast on Functional Programming, covering topics across multiple languages
(ENG) LambdaCast: LambdaCast is a podcast about functional programming for working developers
(ENG) Mapping The Journey: interviews with famous people from IT
(ENG) The Chanelog: broad range of topics
(RUS) CTOcast: mostly interviews, tech podcast with different guests from different companies
(RUS) SDCast: mostly interviews, tech podcast with different guests from different companies
(RUS) Americhka.us: non-technical podcast about life
(ENG) The Chariot TechCast: “The Chariot TechCast is an interview show that covers emerging and important tends in the world of software development.”
(ENG) Software Engineering Radio: different tech topics
(RUS) Razbor poletov: Java-related talks
31 October 2017
I differentiate normal programming language and scripting programming language.
Scripting language must be used for quick prototyping, automation, has a nice integration with shell, etc. Also, it should be very quick at startup time.
So, any automation task can have the next implementations evolution, e.g.:
then any scripting language (
I have been using several languages which have such characteristics (or similar): Ruby and Groovy.
I started using Ruby (as a scripting language) in 2008. It was cool. In that time Ruby community was "bashing" Java. The community was and is Ruby on Rails centric, mainly non-Windows. Almost nothing has happen outside of Rails (Vagrant, Chef and Puppet are exceptions), and it’s sad. But this language has a "soul". I could not explain, but I feel happiness while I am writing something in Ruby :-)
Groovy is nice JVM language which has own pros & cons. But now, this language has some problems with popularity (see The state of Groovy and other JVM Languages). And for me it’s a very important point. Also, due to JVM nature, the script startup is very slow (I do not count GroovyServ).
Groovy language syntax is much better for me than Ruby. I like Groovy packages and hate Ruby Modules and Namespaces. Again, it just a matter of taste.
If we compare different scripting languages they are almost the same in terms of what can be implement using them. But, some of them have community problems, some - ecosystem problems, some - is just not well suited to your development approaches (e.g Perl, Lua, Js/Node.js).
And as always there must be some shift or motivation to look around and try something new and hopefully better. The time invested in learning new "tool" must be rewarded in future.
If we look around the decision of picking another better scripting language is very simple - it’s Python. And by "better" I don’t mean syntax.
I have never used Python because Ruby (or Groovy) had the similar language features and I have not seen any benefits in switching to another language. On the another hand, Python has huge ecosystem, it has library for almost everything, it is not a framework-centric language (see Ruby on Rails, Groovy: Grails or Gradle). And the most important it has a momentum in terms of Data Science, Machine Learning and Artificial Intelligence (where I have big interests as the other people). Unfortunately, Ruby has lost this fight.
For several month, I have been using a lot of Python-based tools (AWS CLI, ZMON, Stups) during my work day and this is another big motivation for me to look into the Python as my potential next scripting language.
There is a very interesting moment. I do not like Python syntax (I am not dogmatic). For some reason Python syntax (and language features) is very ugly for me. And I would pick Python only because of pragmatism and not because I like it. But, I am not sure whether Python will be my main scripting language since Python is not equal to "happiness" :-(
Python is very popular right now (check the numbers below) and it’s a very good time to start using it if you don’t have biases like I have.
Older posts are available in the archive.