Two or more ...

A quick review of the book Practical Microservices by Ethan Garofolo

A bit exploration of why learning is important and why you should take care of it yourself

Why and how I have added functionality to insert lines

How do I approach work at home?

Does selecting at what point you access the train have anything to do with programming?

How do we handle separate SSH key

When and How should you do katas?

Why Emacs?, why Evil? and some code

Where do QA should fit within your process?

Which one should we use?

Which one should we use?

Do we need more tests on a dynamic language?

I have been using NeoTree for a while. Time to look at alternatives

Or why did I put myself into doing this.

Or how I can't longer use the mouse on my Emacs

Finally I have decided to stop messing around with nth languages.

On which setting up Emacs for Rust lead to some nice discoveries

Some notes about the BusConf 2018 in Germany

A parable about design through my use of e-readers

Adaptation of some usual katas so they have requirements that need to be considered for the functional calisthenics

There are calisthenics rules for OOP to improve your coding. This is an attempt to do the same for functional

Are all languages equal? The answer is no. So, which one should we use? Maybe the one that requires less coding

My first working Liberator mini-project, with a minimal amount of work being done, A Get and a Post

Emacs provides one of the best help systems that I have seen on a text editor/IDE. Here are a few things that you can do.

A quick recount of my current state trying to get a rest API working using Liberator.

Small changes on the css

There are a few things that are possible on Git that are not allowed by TFVC. Here I will show some of those behaviours.

A couple of behaviours that seems strange (erlang and java).

Stop the presses!! Change the way you structure your application. No more horizontal layers. Rather vertical slices are the future.

I love pair programming. Haven't used as much as I would like to, though. Some history here (pair programming and mine) that lead me into it.

In the mind of Uncle Bob FP means immutability. Here we will see what are the benefits and drawbacks of immutability.

There is nothing like a good discussion to revise and try to understand the process that is being used on your company/team. Dailies was the subject of the latest one, and here are some thoughts about it.

Fluent Interface or Fluent Style has been defined for some time. It is something specific to OOP due to the way that method calls are being made (you are calling the method on an object). A subset, or standard way of doing Fluent style is through the use of method chaining.

A small introduction to binding and assignment, a couple of operations that are usually conflated on OOP languages. On FP languages you need to understand the difference between them.

Once you get into Functional Programming languages you are going to find a few new concepts and ideas that you have to take into account. This is the hub from which you can access to posts related to these new concepts.

I do have a dislike of the factory and factory method patterns. Mostly because I have abused them. Thanks to lambdas in C# you can skip them on simple casses.

A brief description of the shaving tools that I use, and how they relate to programming.

This site, the why, the what, the how