Profile cover photo
Profile photo
Lars Albertsson
168 followers
168 followers
About
Posts

Bad news: Train broke down.

Good news: It happened at a station. Evacuation with snowmobile not necessary.

Back to Oslo. Two girls give a Christmas gift to a beggar on the street.

Life is good.
Add a comment...

Post has attachment
I seem to have hit a top position in a list sorted by "Hot". I am confident that it has never happened before.

Link to slides with embedded presentation: https://www.slideshare.net/lallea/top-10-data-engineering-mistakes
Photo
Add a comment...

Post has attachment
Career day at my son's school. Teaching recommendations with collaborative filtering to a classroom full of 10 year old children is challenging, unpredictable, and fun.
Photo
Add a comment...

Another interesting comparison of managed #Kubernetes offerings https://blog.hasura.io/gke-vs-aks-vs-eks-411f080640dc.
Add a comment...

I look forward to my first conference hat trick - I'll be speaking at Data Innovation Summit for the third year in a row. The topic this time is #DataOps in practice. See you in March! #DIS2019
Add a comment...

"Central source control tools were not capable of delivering agile development."

It is peculiar how contemporary trends are mistaken as aligned trends. Distributed version control discourages agile development, not the other way around.

The technical manifestation of agile development is CI/CD - limited WIP, low latency from idea to production, and frequent opportunities for feedback.

CI/CD requires a centralised workflow. Consider a hypothetical VCS that does not support forks, and limits branches to commits from a single user. Since master would be the only place for integration, continuous integration is the only option. Bugfixes on releases are impractical, so continuous delivery is essentially enforced.

In a VCS with feature branch and fork capabilities, you have the option to postpone integration and postpone work required for delivery. A workflow that can be expressed in a distributed VCS, but not in a centralised VCS cannot be CI/CD. Centralisation encourages CI/CD and agile development.
Add a comment...

OH:
- Wat? Are you wearing a suit? What has happened?
- It is my Halloween costume. It's the most scary thing I could think of.
Add a comment...

Post has attachment
So, 83% think that we have issues with racism in the Swedish society. 17% voted for the fascists in the elections. What a harmonic coincidence.

https://www.aftonbladet.se/nyheter/a/QlbWxR/manga-fler-upplever-rasism-i-samhallet
Add a comment...

Post has attachment
Interesting comparison of managed #Kubernetes offerings. 3 minutes vs 20 minutes cluster creation makes a huge difference for workflows and testing practices.

https://kubedex.com/google-gke-vs-microsoft-aks-vs-amazon-eks/
Add a comment...

Post has shared content
NotPetya caused some ten billions of collateral damage in the West, as well as nuking a lot of Ukraine's systems (as intended by Russia) - some overview and background here, and an indepth story of the effect on major global shipping company Maersk, who took some 10 days to get their IT back together and months to get their software back up. Meantime needing to process tens of thousands of shipping containers.
"Snabe, however, didn’t say much about the company’s security posture pre-NotPetya. Maersk security staffers tell WIRED that some of the corporation’s servers were, up until the attack, still running Windows 2000—an operating system so old Microsoft no longer supported it. In 2016, one group of IT executives had pushed for a preemptive security redesign of Maersk’s entire global network. They called attention to Maersk’s less-than-perfect software patching, outdated operating systems, and above all insufficient network segmentation. That last vulnerability in particular, they warned, could allow malware with access to one part of the network to spread wildly beyond its initial foothold, exactly as NotPetya would the next year."
Add a comment...
Wait while more posts are being loaded