Jeremy Katz

Polls can be a cheat code for earned media, and a great way to build authority. But there are levels to this. Here's how one of the best I've seen - Capital One - does it. (And what I'd do differently to increase earned coverage). Led by Shena Ashley, PhD, Capital One's Insights Center is a masterclass in leveraging polls to create unique insights that would do incredibly well via earned syndication. Here’s what they do great: ✅ Content that sticks: Crucial issues > fleeting trends. Focusing on topics like financial stability, mobility, and entrepreneurship, it's easier to rationalize investment on topics with a longer shelf life. Their insights + stories can drive coverage for months to come. ✅ Visual storytelling: Data doesn’t have to be dry, and Capital One presents original insights through clear and eye-pleasing visuals that are easy to understand. Publishers like charts, they love colorful charts, and they LOVE colorful charts that are easy to understand. Check, check, check. ✅ Strong methodologies and extensive polling numbers: Capital One frequently involves 7k+ participants in their studies - they are not half a**ing it. Well explained methodologies are table stakes to get your polls covered, and Capital One does a great job outlining their data collection process, sample size, and research methodologies.   ✅ Easy to steal: Each report has multiple easy to take stories/soundbites, and are also written as full pieces of content, which can be taken as whole. Finally --- if I could change one thing... Add a byline. Brand publishing NEEDS a byline - no news outlet wants to cover a story that can't be credited back to a human. All in all, polls can be incredibly valuable for driving earned syndication - check out Capital One's Insights Center in comments for killer examples.

18

2 Comments

Technical founders can sometimes get so enamored with the product they are building that they really don’t understand why customers actually buy their product. I’ll take it one step further… Sometimes your product might be only 25% of why a customer buys, the other 75% is stuff you might not even realize until you take a closer look at each specific buyer. - Some buyers value the quality and responsiveess of your support above product feature maturity or feature parity with competitors. - Others use your product and also desire a partner they can work with, for example to teach others and conduct educational workshops. - Still others have specific KPIs and they are buying your product as a means to an end. They see the customer success team as partners who can work with them weekly to help meet and exceed their objectives (cloud cost optimization, increasing the satisfaction of the end users they support). Advice to the founders in my network, take the time to try understand why your customers buy. - It might have less to do with your feature roadmap and more to do with how you show up when they need you and how you help them win. - Your product offering also gets better faster when you understand all the manual things your sales, support, and customer success team do to get the sale and make customers happy. - Talk to more customers to understand why they first bought and why they continue to be paying customers. Understanding why customers really buy makes it so much easier to prioritize the product roadmap and find ways to improve the sales cycle and customer retention. What do you think? Have you experienced the disconnect that can sometimes occur between founders and customer facing leaders? Would love to hear your experiences and advice for others in the comments.

5

1 Comment

Who are notable companies who run on-prem? I know some of the recent, popular companies, but I'm looking for companies (or divisions of companies) that never went to the cloud too. I'm going to be PRing references for Chick-fil-a (edge), Target, and GitHub to this repo to track some of them. Looking for more references. https://lnkd.in/d7QkaVp8

34

24 Comments

Some straight talk about why #platformengineering initiatives fail and how to make sure that doesn’t happen on your watch. Check out the latest from The New Stack and Jennifer Riggins. #DevEx #DevOps

2

If you are working with Docker... I highly recommend looking at the Slim toolkit. https://lnkd.in/gX_Gb9Kf Why? Slim allows developers to inspect, optimize, and debug their containers using its xray, lint, build, debug, run, images, merge, registry, vulnerability (and other) commands. It simplifies and improves your developer experience building, customizing and using containers. It makes your containers better, smaller and more secure while providing advanced visibility and improved usability working with the original and minified containers. Don't change anything in your container image; minify it by up to 30x to make it secure, too! Optimizing images isn't the only thing it can do, though. It can also help you understand and author better container images. Keep doing what you are doing. No need to change anything. Use the base image you want. Use the package manager you want. Don't worry about hand-optimizing your Dockerfile. You shouldn't have to throw away your tools and your workflow to have small container images. Node.js application images: from ubuntu:14.04 - 432MB => 14MB (minified by 30.85X) from debian:jessie - 406MB => 25.1MB (minified by 16.21X) from node:alpine - 66.7MB => 34.7MB (minified by 1.92X) from node:distroless - 72.7MB => 39.7MB (minified by 1.83X) Go application images: from golang:latest - 700MB => 1.56MB (minified by 448.76X) from ubuntu:14.04 - 531MB => 1.87MB (minified by 284.10X) from golang:alpine - 258MB => 1.56MB (minified by 165.61X) from centos:7 - 615MB => 1.87MB (minified by 329.14X) Rust application images: from rust:1.31 - 2GB => 14MB (minified by 147.16X) Java application images: from ubuntu:14.04 - 743.6 MB => 100.3 MB

4

Latest q2 software engineering comp report (accepted offers) is out and it's a doozy. Please DM or email me [email protected] for the data. Overall trends: - compensation is up big in q2 - companies hiring more for seniority - in-office requirements continue to rise ... and much more

18

1 Comment

I'm having enlightening convos with folks who deliver infra for others to run. It sounds like "runbooks/wiki docs" are a real problem from a handoff/support perspective. We have an elegant solution, when you deliver runbooks as "click to play/pre-configured" Notebooks, and a command fails, the user gets an `escalation button` that shares a link to the output/metadata into the shared Slack room. It's ideal for bridging the gap when there's a support relationship. 🤓 This sounds like a case study in the making.. anyone else struggling with this?

14

Great SRE Interview Questions 

4

Just a few weeks after the GA release of Arm64 runners, we’re already seeing our clients achieve noticeable reductions in build times and lower runtime costs. If you're looking to scale your CI/CD operations and accelerate feedback loops, now is the time to explore the benefits of Arm64! Key takeaways: - ⚡ Faster build times to streamline development. - 💰 Cost savings through optimized runtimes. Ready to take your CI/CD to the next level? #CI/CD #Arm64 #DevOps #BuildOptimization #CostEfficiency #ContinuousIntegration target: https://lnkd.in/gY-_n6JJ

76