For some reason, I expected the installation was going to be a bit more complicated on MacOS. It is actually quite easy.
I downloaded the latest MacOS binaries from https://jdk.java.net/11/
I clicked the .tar.gz that I got to decompress it in the jdk-11.0.1.jdk directory.
I moved it to the directory for MacOS to pickup the new version:
sudo mv jdk-11.0.1.jdk /Library/Java/JavaVirtualMachines/
I was done with these steps.
You can test by running:
to confirm that you see the new version:
openjdk version "11.0.1" 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.1+13, mixed mode)
I have heard of serverless from so many vendors by now that it feels more about marketing than anything else. I have a bad gut reaction when I feel that there is more marketing than substance about any technology.
I decided to look at Now from Zeit just out of curiosity and I think that I should look at it a bit more since it looks quite easy.
On the Zeit site, you can see the free offering that they have and it allows you to get your feet wet and be more curious about what you can do.
The Now CLI also looks like a very simple way to perform everything you need.
I also like the immutability approach that they have that allows you to move quickly from one deployed version to another.
It is definitely worth more time to see what I could do with this platform.
Nice article about some framework that we should all learn and as much as I know a few this list of classics certainly has a few that I should learn before the end of the year.
Which one are you learning?
It is always a good reminder when you read this type of article. Producing good code that can be easily maintained is very important.
- S: Single Responsibility Principle
- O: Open-Closed Principle
- L: Liskov Substitution Principle
- I: Interface Segregation Principle
- D: Dependency Inversion Principle
This presentation has a series of coding habits that can cause problems if applied blindly:
I have seen many of these bad habits and I have quite often used them because they are my habits as well. I am unsure how we can lose these habits easily because some are embedded in the team and getting the entire team to change is not easy.
I like that he explains the fact that some of these start small and grow to be a problem. You have to be very attentive and make sure you don’t start on the wrong path.
This presentation from Google Next 2018 is very good to understand how to use Vault in Kubernetes:
The details of the demos are available on GitHub:
The details shown on how to run Vault in Kubernetes and how to get application in Kubernetes to use Vault are very good and help understand how we can deploy our own.
I have been getting an error every time I try to install a new homebrew package and I found a quick and easy solution to it.
The problem looks like this:
user1$ brew install kubernetes-helm
Warning: git 2.15.1 is already installed
Error: Git must be installed and in your PATH!
Error: The following formula:
cannot be installed as a binary package and must be built from source.
Install the Command Line Tools:
Git is available on my system without issues so I was puzzled about this “invalid” error.
I found that if you set this variable:
It would allow brew to update and then install new packages without an issue.
Very simple workaround.