Asaf Klibansky

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

Earlier this week, I mentioned that we shipped over 30 new endpoints for the Vanta API at the end of June. Another exciting set of improvements centered on controls: adding and removing custom controls, updating control metadata, assigning control owners, adding and removing test or document (evidence) mappings to controls, etc. These building blocks allow you to bring your program into Vanta – keep the work you've already done, gain a high-level view of your security and compliance program, and benefit from continuous control monitoring. Thanks to Bo Y. and Eric Yuan for building these new endpoints!

130

8 Comments

Saw this post about selective builds for monorepos 🚀 Key benefits: • Faster build times • Reduced resource usage • Improved developer productivity Read the article to see behind the scenes, it's a lot of work! The good news is that Coherence has this built-in and makes it turn-key for you to get going. https://lnkd.in/eWzYbtMg #DevOps #Monorepo #CICD #EfficiencyBoost"

4

Programming is Unnecessarily Hard! I’ve taught programming to business and product folks at Acko and Coverfox Insurance. The goal was to help them run queries and get data without depending on the tech teams. Here’s the reality check: Before they even get to writing code, they’re buried under syntax, editors, file organization, server deployments, version control, and so on. As a developer, I get it—it’s part of the job. But for non-tech folks, this has been a total roadblock. It’s not about their aptitude; it’s the crazy learning curve. That’s why I founded FifthTry. We believe programming should be as easy as changing a cell color with conditional formatting in MS Excel. Doesn’t that instant win make you want to keep going with Excel? Coding should be just as rewarding from the start. I am excited to share that over 1,000 non-tech folks have already started their projects with us 🚀 A big shoutout to our early supporters: Dr. Sneha Upadhyay, Swapnendu Banerjee, Rutuja Kapate, Jahanvi Raycha, Govindaraman S & others. Let’s make tech easier for everyone. #CodingForAll #FifthTry #TechMadeEasy #Fastn

98

11 Comments

Our B2B auth products make organization management (e.g. SSO, role & permissions, SCIM, per-org auth settings) & member management (password resets, 2FA, etc.) a breeze -- with our Admin Portal SDK, we're taking that a step further to offer this as a fully embeddable, whitelabeled UI customers can now offer directly to their end consumers in their app For a B2B app, this means giving direct organizational control to your admin members in just a few lines of code -- no back-and-forth required for customers to set up SSO, SCIM, or make any other organizational auth changes

24

Sup fam!! Relationships are everything!! They're the core of your engineering platform. Your team's design docs, software patterns, pull requests, and GitOps workflows all need to pass through a complex network of relationships before becoming meaningful to stakeholders. Before that, they're just bytes sitting on Jeff Bezos' disks. How are your relationships doing? Which relationships need some light touching up? Which ones need some serious investment? How about that one person on that one team? How about on _your_ team? Are you tracking these gaps with the same effectiveness you're tracking tech debt? It takes an intentional effort to build meaningful connections and to show peers you're a stakeholder in _their_ success. It's worth your time -- not to mention you'll feel great!! Want to optimize your engineering platform? Start by investing in your relationships!

38

https://lnkd.in/gdGKdeAW - New project I built using a combination of Replit Agent, Perplexity search API using llama-3.1-sonar & OpenAI API Assistant. You're not sure how to vote on that? Take a quiz about your core values then this app will research it/them and help you decide.

5

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

tl;dr: Not every ad channel is going to deliver results. Don’t be afraid to cut the cord on the underperformers before they drain your budget. Ever invested in a channel that just didn’t work out? If you’re a dev marketer, your answer’s most likely yes. At ScraperAPI, Google Ads was a total bust. We tried. We spent. We waited for results that never came. Outside of branded searches, it was a total disaster. It was a stark reminder that not every channel — no matter how popular — is always worth the spend. While I’m a big believer in the idea that growth doesn’t happen overnight, you need to know when it’s time to jump ship before you drain your whole ad budget. Our problem at ScraperAPI was that we were building a product that devs didn’t quite know to even search for yet. Hindsight's 20/20, but I wish we’d poured all that AdWords spend into channels that *actually* helped devs understand our product — like Quora, Reddit, and other dev communities — instead of holding out for a payoff that simply wasn’t coming. tl;dr: Not every ad channel is going to deliver results. Don’t be afraid to cut the cord on the underperformers before they drain your budget.

23

1 Comment

My teammate Sean O'Brien, asked me an interesting question while we were discussing how epic it is that, moving forward, very small teams (1-3 people) will build significant software products thanks to development agents like Replit. He asked, "Does all software melt to N-of-1 solutions over a decade?" Essentially, will all software be a highly personalized experience where the software adapts to the needs of a single user or entity. Cool question. My current thinking: Not all software will melt to N-of-1 solutions, but the trend will likely dominate for many categories... Likely to Melt:  Consumer-facing software, productivity tools, and AI-driven platforms (e.g., CRMs, content creation tools). Less Likely to Melt:  Regulated industries and foundational infrastructure where standardization and compliance outweigh personalization. I predict we will be looking at a hybrid landscape: general frameworks at the foundation and N-of-1 solutions flourishing in user-facing layers. Over a decade, most software will have no choice but to embrace elements of personalization and adaptability. For many investors, I think most of the ROI is to be made in the regulated industries as only a select few companies on the consumer-facing side will own almost all use-cases. Am I off the mark?

6

Saw the news today that PivotalTracker is shutting down. Although I haven't used the product in years, PivotalTracker was, to me, the perfect example of how opinionated software can supercharge a development team. All software embodies a process. The best tools are ones that not only record information but drive your process and your team forward. If you tried to use PivotalTracker but didn't follow their process, you'd find the tool would not work well - and so you'd be forced to adopt their process (which was a good process). Other tools that are more general, like Jira, let you do whatever you want, which often results in teams with poorly defined or loose processes, which results in teams that don't operate effectively. RIP PivotalTracker. For me, its legacy as an example of what opinionated software can do to make a team operate with peak efficiency will live on. https://lnkd.in/e3_jvQ9g

16

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.

6

1 Comment

Tailscale posts about fixing their pricing so that everyone can use OIDC-compliant SSO on any plan. This sentence about their mission stood out: Our mission at Tailscale is to build the new internet, and we take a strong stance that the next internet has to be secure by default. https://lnkd.in/gQF6rR9c

2

so what is your move gaes

1

Got an email "GCP's Apache Kafka service is now live" at noon. After dinner, spent half an hour confirming it works well with Timeplus. I don't think you can make the bootstrap server publicly accessible. Has to setup a bastion host or run your app within the same project/VPC. Setting up the SASL username/pwd was not easy. Follow the guide carefully https://lnkd.in/gcKEVh3g and you may need to disable the iam.disableServiceAccountKeyCreation Anyway, if your workload are in GCP already, having such Kafka service in GCP is nice way to burn your cloud credits. Yet another Kafka vendor, great.

33

2 Comments