Ruby has so much inspiration from the Smalltalk!

Here are my findings:

• Inspect method actually opens an inspector for the object in Smalltalk, Ruby just tries to show object’s guts
• collect, select are methods for collections from the Smalltalk
• do for collection in Smalltalk is the same what’s in Ruby each
• block parameter in «pipes» in Ruby is very similar to Smalltalk
• super is calling the superclass parent method
• initialize is a constructor name for the class in Smalltalk
• keywords concept has slightly different syntax, but the meaning is the same
• « method
• Ruby object.send method = Smaltalk object perform: method
• the self keyword means the same in Smalltalk and Ruby

It’s quite simple to increase PVC size since K8s 1.11

kubectl describe pvc and find your storage class.

Name: jenkins
Namespace: jenkins
StorageClass: jenkins-gp2
Status: Bound
Volume: pvc-473e3dbf-b759-11e9-9cbc-02a7fb0b6cca
Labels: app.kubernetes.io/component=jenkins-master
app.kubernetes.io/instance=jenkins
app.kubernetes.io/managed-by=Tiller
app.kubernetes.io/name=jenkins
helm.sh/chart=jenkins-1.3.6
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 16Gi
Access Modes: RWO
VolumeMode: Filesystem
Mounted By: jenkins-6b5c9bcbbb-gr2l5
Events:

kubectl edit storageclass jenkins-gp2 add the following to your storage class

allowVolumeExpansion: true

kubectl edit pvc jenkins

In the age of Kubernetes and all this fancy stuff, I decided to make something really simple and as static as possible. The modern, cutting-edge tech stack.

This is a story about https://it-premium.com.ua reincarnation featured with responsiveness and saving all the functionality it had before. Though it wasn’t a simple, but very interesting journey.

Here are the specs I wanted to preserve:

• Multilanguage support, due to Ukrainian language law enforcement we had to introduce one more supported language among English and Russian
• PDF dynamic generation based on what user was chosen
• Dynamic tariff calculations with dependencies on the services of user’s choice
• Easy data management. It shouldn’t be hard to fix some figures by someone else.
• Easy localization management.

The old stack

At first, it was a Ruby on Rails 4.2 application and it used the following gems:

• Create a Jenkins job for mobile application internal share to the Google Play Store
• Create a Jenkins job for mobile application automated release to the Google Play Store
• Restore Jenkins jobs for the COBOL build with Oracle 11.2 and Sybase 15.5 on the Solaris Sparc, AIX and HP-UX machines
• Debug a performance issue in the distributed power management software.
• Create helm script for the product deployment to the Central K8S cluster into staging and prod namespaces and talk to DynamoDB and put assets to the S3
• Setup Prometheus + Grafana for the performance monitoring
• Setup gradle builds for Java Spring and NodeJS
• Extend XenServer with two new HDDs for a capacity and much more.

This is really my little timesaver because you know, a lot of meetings happen when you work remotely.
Works best with Alfred 4 using mapped hotkey.

tell application "Calendar"
	tell calendar "[email protected]"
		set itemLocation to location of first event where its start date ≤ (current date) + 10 * minutes and end date ≥ (current date)
		if itemLocation contains "zoom.us" then tell application "Finder" to open location itemLocation
	end tell
end tell

This is really my little timesaver because you know, a lot of meetings happen when you work remotely.

The bad thing about Rails is that by default it suggests using own messy design patterns like fat models. I mean all these callbacks in AR, observers and everything that is good for a simple blog but fails for a big application.

You have to use a very little part of Rails to apply DDD concepts.

Почему нужно проинвестировать время в изучение двух древних языков Lisp и SmallTalk?

Я уверен, что это сделает вас на шаг ближе к стадиям развития специалист и эксперт.

Nikita Prokopov сделал отличный talk о стадиях компетентности программиста. Идея в том, что каждый программист на своем пути развития проходит пять стадий развития:

• Новичек
• Продвинутый
• Компетентный
• Специалист
• Эксперт

Почему нужно проинвестировать время в изучение двух древних языков Lisp и SmallTalk?

Я уверен, что это сделает вас на шаг ближе к стадиям развития специалист и эксперт.

Nikita Prokopov сделал отличный talk о стадиях компетентности программиста. Идея в том, что каждый программист на своем пути развития проходит пять стадий развития:

• Новичек
• Продвинутый
• Компетентный
• Специалист
• Эксперт

Никита ближе к концу доклада на примере собственного опыта сравнивает два языка: Java и Clojure и выдвигает предположение о том, что Java хорош для новичков, а Clojure это глоток свежего воздуха для уставших опытных программистов.

Here is a piece of my old code, but it’s definitely could be improved.

def to_params
  h = ticket_params
    h[:activity] = extract_activity if extract_activity
    h[:event] = extract_event if extract_event
    h.delete(:state_event)
    h.delete(:activities_attributes)
  h
end

As you can see here, ‘h’ variable name is quite uncommunicative. Could it be refactored?

Let’s see, h=ticket_params. We call this because we don’t want to modify ticket_params. Is there any method which creates a copy?

It turns out we have dup method which creates a copy of an object, this is exactly what we wanted. Then, we have tap method, which allows us to dive in object internals and return then itself. Here is whole new piece of code after refactoring.