kadir

This article hit hard. Let’s talk about performance reviews. Performance reviews suck, simply, because they reward people who optimize for performance reviews and punish people who quietly do the hard work. Ok, but what else can you do? Especially at a larger organization. 3 easy steps: 1) Hire great managers you trust. 2) Be extremely unforgiving at firing bad managers and force your managers to do the same. Sorry I lied when I said it was easy, but this is step is mandatory. If you’re not willing to stomach it, just become an IC. 3) Trust your managers at knowing who the best performers in their teams are. Thank you for reading my book on effective leadership.

my top 4 tech twitter tweets of all time

Hit a big milestone today: the 𝟭𝟬𝟬𝟬𝘁𝗵 𝗣𝗥 is now merged! Proud of the team and the progress we’ve made on this journey.

At @polymetai, we’ve worked with so many different YC founders from different batches. Here’s what I’ve learned from working with them: The first time I worked with them as provider, I realized their workflows aren't just about speed, they're eliminating anything that doesn't move the product forward. 1 - They collapse steps. If a workflow takes five steps, they’ll make it three. If a decision can be made today, it’s made today. The fewer transitions, the faster the output. 2 - They trade polish for momentum super early. They don’t obsess over perfect in v1. They obsess over getting something live, learning from it, and compounding improvements. 3 - They integrate partners deeply. If you’re a provider, you’re not just “delivering.” You’re in the loop, inside the workflow, moving with the same urgency as the core team. And if you want to work with a YC team (or sell them something) you need to match that pace. Because as far as i can see in their world, every extra day is a lost opportunity. If you’re slower than they are, you’re not just behind schedule, you’re creating friction. and friction is expensive. They’ll choose the partner, tool, or service that can move as quickly as their own team. That means answering questions on the spot. Delivering in hours, not weeks. Adapting without a “we’ll get back to you” delay. Working with them isn’t about meeting a deadline. It’s about living inside their momentum. Once you do, you stop being a vendor, you become part of their team.

Every business team (even SALES and SUPPORT) should have access to the codebase. Most assume only product and dev teams need it. Salespeople are frequently talking with the customers & potential customers, and they're forwarding all technical questions to tech sales persons or product teams. It works, but it’s super slow. And over time, it builds a wall. Cursor, windsurf can change that. Not because they teach salespeople how to code, but because they let them ask the product questions directly. In B2B SaaS, as teams scale, sales drifts away from product. Most of enterprises try to fix this with weekly syncs and enablement decks between sales & product teams. But none of that is as effective as giving people the ability to explore the product for themselves. That’s why those AI IDEs should be part of every sales and growth team’s stack, not just engineering’s. at Polymet We’re helping teams move fast on design, turning ideas into interfaces visually. Not everyone can build a product. But everyone should be able to shape how it feels. Design is where too many product teams hit bottlenecks frequently - we’re removing that bottleneck, by making high quality design fast and iterative.

Every startup wants this. A community where users help each other. Where questions get answered before team even sees them. We didn’t ask for it. They just did it. Our customers design their own products and still make time to help others design too. "Polymet Network" is becoming something we never could have planned. And it’s all because of the people we get to build for. We honestly couldn’t be prouder.

Smoothest way to get something live fast. Export the design from Polymet, test it locally, and deploy it with @back4app Here's how: youtube.com/watch?v=rTk_ZE…

Best designs rarely happen on the first prompt. But what if you could actually discuss your project with @polymetai?

Imagine bringing GSAP level animations straight into your Polymet flows. It’s not here yet, but just thinking about it feels like a game-changer, wouldn't it?

A few days ago, we kicked off "Polymet Network" which is a focused space for power users who live inside the product. Sharp feedback, fast fixes, good ideas. The energy was instant. this is worth building. If you’ve been using @polymetai for 3+ months and think you’d add & get value, dm please.

Building a product used to be like carving the Parthenon by hand, you had to lay every stone yourself. Now you're more like a Roman emperor. You set the vision and system builds itself. For growth minds, it’s no longer construction its indeed a command

.@polymetai + Your Design System Just integrated @airtable public design system and started designing. Here’s how you can do the same: 1 - Install the "Polymet Figma" plugin, and run it on your Design System file. 2- Firstly, select the design tokens - colors, typography, spacing, font, etc. For now I recommend transferring these frames one by one instead of importing the entire file at once. 3 - Use "Enhanced Prompt" while transferring those designs into Polymet. Include something like: "This is our design system colors, detect them correctly. We'll use those colors later - create a component file and move all the color tokens into it" 4 - AI will then start generating those frames. Once it's done, you can import your remaining token and component files - but this time, add them to the existing project instead of creating a new one. 5 - Review and tweak the components as AI might miss a few things. Use visual editing or prompts to fix any components or block issues you spot. 6 - Duplicate the project and start building your screens with your new design system! Bonus - we’re also working on features like cross-project components, custom themes, and smarter design system handling, etc. coming very soon. With this, teams can finally bring their own design systems into Polymet and generate production-grade UIs with their own visual language. Want early access or feel like sharing this with your circle? Drop a “polymet” in the comments.

@gregisenberg hey @gregisenberg definitely resonates. had shared a similar take recently while thinking through how we evaluate AX at @polymetai, especially around things like instruction following and handling ambiguity etc. linkedin.com/posts/kdrnp_iv…

there's a quiet shift happening in how we design software. we're moving from UX to AX (agentic experience). traditional UX is screen-centric. you tap a button, product reacts, job done. every session starts from zero. designers pre-plan every path with hard-coded flows. users fill out forms and dropdowns because the product remembers nothing about you. success = fewer clicks and faster flows. trust = "interface looks clean so it must work." agentic experience is relationship-centric. the agent keeps track of ongoing goals, nudges next steps, improves over time. you're never starting over. the system plans its own path - it senses, infers, chooses actions the designer didn't script. context is learned, not asked. preferences, patterns, even team norms are remembered. success = earned trust and compounding value. metrics shift to retention, satisfaction with decisions, how much autonomy you hand over. trust = the agent shows its work early, then tapers as confidence grows, like a human teammate. most apps will eventually work this way. your email client will learn your writing style and priorities. your design tool will remember your brand guidelines and suggest layouts. your CRM will track relationship patterns and recommend next moves. the best products will anticipate needs, remember context, and get better with every interaction. shoutout to @meetLCA for this visual and hit them up if you need help designing these AX experiences (they lead the charge) we're moving from tools you use to partners you work with. the companies building ax instead of ux will own the next decade. users will stop tolerating dumb software that makes them repeat themselves. once you experience true AX, traditional UX feels broken. there's no going back.

@george_nqu @polymetai hey @george_nqu, thanks for the feedback. just checked your projects are you referring to the new pipeline we released? as this is the first negative feedback we’ve seen since then 😅 if the issue's still persist, happy to hop on a quick call. let me know please

Still haven’t tried our last release? You’re seriously missing out.

@daniel_nguyenx hey daniel, have you tried polymet.ai before? lmk if you'd like to try it i can give extra credits. read your replies, def agree. we're designing products from the same perspective by ai. i'd love to get your feedback.

My new favorite use case for Claude Code: build the landing page for a new side project. - I purchased an astro template that I like - Brainstorm with claude about the copy and flow, potential objections, pricing plans… - Save the plan to a md file - Tell claude code to rewrite the entire website following that plan - Generate other required pages like Privacy Policy, FAQs etc… Then I’ll need to fill in the screenshots, images and other marketing materials. AI is a gift to solo founders.

Our teammate @kdrnp wrote a poem: We launched the new structure, then fixed all the bugs, Now chilling outside, no meetings, no mugs. If you’d like to build where the vibes are plus We’re hiring at Polymet. Just reach out to us 👨‍💻

Try our new generation pipeline!

introducing mitte 1.0. AI creative suite, built for precision. photorealistic scenes. perfect product placement. video and sound. check us out on @ProductHunt today.

We superpowered the Polymet! Mark the date - July 17!