If you wish to see the power of docker on your Mac as a way to run all (or many) of your daily apps check this great post by Jess.
However, when you are going to the repo with all the Dockerfiles it’s clear that it was meant to be used on Linux. However, here is a short path to run all of these powerful apps on Mac as well.
Continue reading
Last week I had the pleasure to participate in a panel that talked about the future of DevOps. It was part of Transform!2019 Event that was in Munich, Germany. Fun fact, from the hotel I could see the Google office, which brought many good memories.
The main goal of the event was to let participants a way to experience what it means to change a company to become more “Intelligent”. The way to share the knowledge was by engaging in an open dialogue between industry leaders, start-ups in the DevOps world, executives and SAP experts. The event had few tracks and many options to network which was a great opportunity to learn from others.
When it comes to creating a business that can thrive in the digital age, the benefits of DevOps are clear. Faster deployment frequency and lower failure rates are proven to be some of the advantages of DevOps adoption. It brings more velocity into your (software) organization and enables you to add more value (faster) to your users.
Continue reading
Any developer knows that you must have a source code repository (e.g. Git) but from time to time I get the question “why do I need a binary repository”?
Here is the short answer:
Faster and more secure software development – Any company is a software company these days and the best companies release updates on daily/hourly bases. The ability to push updates quickly is a real competitive advantage. The minute you have few engineers on your team you wish to avoid ‘fetching the all internet’ with every ‘npm install’.
A binary repo will give you the option to cache these libraries and make sure you are working with the correct ones (vs a hacked one). From the developer perspective, it is a big boost for their productivity as it saves time during development and on each build. Even better, from the DevOps perspective, the ability to control all the packages/libraries (and scan them for vulnerabilities) is a huge advantage. It enables the internal engineering team to control the releases better as they have full transparency (e.g. quality, performance, security, licenses, etc’) on everything the ‘compose’ the release version. Check the 12-factor app manifesto for more on dependencies (declaration and isolation).
I read a few years ago the Poor Charlie’s Almanack and found it to be a really great book for many areas in life. It’s also a long and heavy book so you might wish to get it it to your Kindle. Charles Munger is a brilliant thinker and it’s no surprise that the book is full of practical wisdom.
Some of the points I took and used many times:
Incentives – He talks about the incentives and how they are in the root of many systems. One of the more powerful statements is: “If you wish to see what people will do – look at their incentives”. It holds true both to people and to teams & companies.
Bias – How the human mind is closing itself after it ‘knows’ something. That might be really hard when you want to change your thoughts on a topic. You should embrace people who think differently and aren’t agree with you on every topic. It’s not easy but rewarding and will improve your decisions. Continue reading
It’s one of the best books I read during 2018.
Hans Rosling was a great author (and a speaker) and he expressed his ideas in a very clear way. One of the great things that open this book, is the test that he gives you at the beginning. It comes to prove you, how little you know about the world we live in. It drives the point home very clearly.
Don’t believe?
Try it for yourself:
Continue readingI’ve just finished this interesting book on the biography of cancer. On one hand, it’s a depressing story, as we are still losing many battles.
On the other hand, there are many ways that progress have been made and hopefully, we are in a phase (e.g. genomics research and the cost reduction in analyzing DNA) that will bring us more victories. It is a story about the history of research with eureka moments and decades of despair.
The author, Dr Mukherjee does a great job in describing the history from its first documented appearances thousands of years ago (when the Greek historian Herodotus records the story of Atossa the queen of Persia and the daughter of Cyrus, who noticed a lump in her breast.) through the progress in the twentieth century to cure, control, and conquer it to a radical new understanding of its essence.
I found somewhere this encouraging answer he gave to the question “With all that you have learned up to this point, are you hopeful in terms of cancer research and possible cures?”
Mukherjee: “I feel pathologically hopeful!
The opposite of hopeful is hopeless.
How can you be hopeless?
Discoveries have occurred, and discoveries are occurring.
Look at history, does that mean that every move becomes the most brilliant discovery or the universal cure for cancer? No.
But history clearly shows a track record of progress. Medicine is caught in this moment of pulling out from a sea of uncertainty these little pieces that are more certain than others. I often tell fellows and residents, to me there is no discipline we practice as human beings that manage this level of complexity. Not just statistical or scientific complexity, but emotional complexity. That’s what makes it one of the most unbelievably moving professions that exist.”
What are the components that help teams to build quality into their outcomes?
The main goal is to create a baseline that developers could follow and be in a quality level that is well defined and measurable. The main parts to focus on are:
