Summarized years of dealing with containers into a learning path. The journey starts from the bottom (Linux basics) and goes up to the orchestration layer. 3 years of blogging and ~20 in-depth articles on containers, Docker, and Kubernetes in one place. iximiuz.com/en/posts/conta…

Eindrucksvoll.

The Feynman Technique—how to learn anything:

We just launched a new site sre.google for you to learn about how #SRE is done at @google: a balance btwn details like disk driver IO scheduling to the big picture of service capacity. Check out books, courses, experts, and how it all applies in the cloud.

Your startup's customer doesn't care if: - Your tech is built on Golang or PHP or NoCode - You use AI/ML, Web3 or execute manually - You analyze 150 data points with Big data or run on Excel It simply boils down to whether you are solving their problem.

Creating a course about starting a podcast - what would you like to know?

So sieht journalistische Arbeit bei Corona-Aufmärschen in Wien im Jahr 2022 aus.

I have been reading Ryan Singer‘s book Shape Up and see a lot of benefits in the approach. Are there people around who use this method? Interested in an exchange?

I am hiring a principal product manager for managing our Christine project involvement. You will work with a great team on OpenTelemetry, falcosecurity , Kubernetes SIG instrumentation, and others. Feel free to DM me. careers.dynatrace.com/jobs/3086bae5-…

twitter frends... anyone here a native Hebrew speaker that can help me with a quick review (<2 min)?

Turbulence ahead: Why the future favours the bold. My call-to-action blog via Global Drucker Forum druckerforum.org/blog/turbulenc… Richard Straub Bruce Rosenstein The Sweeney Agency Speakers Bureau David Lancefield #DruckerForum #leadership #thinkers50

Wow. It’s real. #Istio in Action Rinor Maloku Abstract Cloud Istio manning.com/books/istio-in…

This definition brings us down to earth by focusing on causes before effects. Yes design is about "experience." But how do we cause an experience to happen? By understanding which parts to put in, which to leave out, and how to connect them together. x.com/rjs/status/151…

Metrics from GitHub and JIRA can't tell you how productive an engineering team is.

Asked what I look for in PMs when hiring, here’s my answer: shipped multiple things (impact, examples of many sizes from tiny to big), storytelling, comms (written/verbal), stakeholder engagement, willing to do the work, cares abt getting to the right answer not being right

5 must-ask questions for evaluating new product opportunities: 1. Who is the customer? (Segment) 2. How do we know their problems? (Discovery) 3. How do we reach out to them? (Go To Market) 4. How do we iterate/ scale? (Roadmap) 5. How do we know we are succeeding? (Metrics)

Bandan (Productify) 6. What does our product actually do? (Reality) 7. What does our product CLAIM to do? (Communication) 8. What do our prospects BELIEVE our product to be? (Perception) In marketing, the gap between these 3 is so common - and they rarely overlap. Aligning them is crucial.

“I don’t understand why X was laid off, and their manager also couldn’t tell them why.” With layoffs being more frequent, a thread about how who is let go is often decided, and why it can seem random (even though there’s a system):

Hey Twitter! Are you a member of a community of practice on Product Leadership/Management/Ownership in your company? Would love to exchange thoughts and experiences on developing and nurturing one! DMs are open, thanks! #productmanagement #community

I'm a Chief Technology Officer at Deloitte. I've hired 100+ people in my career and I know in the first 9 minutes if a candidate has what it takes. Here are 10 things that will make you stand out in any interview: