Polina Chernenko 🇺🇦

I’m building two apps right now. The hardest part isn’t code. It’s deciding what not to build.

@Adidotdev 💯

@polya444 Exactly custdev isn't just interviews it's relentlessly chasing real traction and problem-solution fit.

Customer development is the act of gaining traction with customers, of finding a fit between what you make and what they want.

when is the last time you actually read code you merged

@tomjohndesign Tools changed Taste didn’t 🤌

I've yet to see any generative product design tool or workflow that even seems remotely close to replacing my daily work. 95% of product design is knowing what to put in and what to take out, not how it looks. Designers are decidedly not cooked

@rxhit05 Marketing 🥲

Devs, what skill are you trying to improve? -coding -sales -marketing -talking to users -distribution

@hemeon Yeah, ideas are easy. Real design lives in iteration, and Figma owns that loop.

Figma is not out. If anyone automates design with AI it will be them. Still not convinced on any of the AI design tools I've seen - they are fun to use for quick ideas and to help spur thinking. Figma could make a Google Stitcj killer and be back on top.

@ravikiran_dev7 Cache is a shortcut, not a source of truth

Interviewer: If cache is faster than database, why not store everything in cache?

@jessfraz Totally agree - real elegance shows up in reuse, not just features

I don’t give a lot of compliments but the way Codex cli & app is designed so it reuses code (that anyone else can reuse as well) is really quite elegant. Elegant in a way that it could only be the result of an experienced & thoughtful team. Which is rare at their speed & scale.

@jxnlco Loool 🥲

Someone just described me as the Gen Z social media intern for OpenAI.

@samlambert Execution matters, but so does keeping people aligned

I maintain the position that CEOs who constantly have a camera in their faces are probably not getting much real work done.

@chrisalbon Yeah, feels like the natural direction Hardware becomes optional

What if, instead of a buying a mac mini, you could rent a computer and just ssh into it.

@CodeByNZ Frontend = vibes Backend = responsibility 🤌

Do backend devs really find joy in doing this ?

@hemeon Sometimes you’re just faster than the tool 🤷‍♀️

I'm manually designing a deck this morning and it's taking me about 2 hours by hand. Spent all afternoon yesterday trying to make it with AI and wasted way more time typing than just making . Don't forget you can just design stuff with your mouse.

@buccocapital Tools should reduce friction, not replace judgment

“It organizes your files” “It prioritizes your emails” “It tells you insights about your calendar” These are not real things. They are not making you more productive. It is making you an idiot Yes, AI is great. But this is fake productivity. This is dumb. You are being dumb

@blakeaburge Being easy to work with compounds faster than raw IQ

A massive advantage in life: Being a pleasure to deal with. Kind when others aren’t. Calm when things go sideways. Reliable under pressure. Intelligence alone is overrated. Be someone who lightens the load for folks around them. People value people who make their lives easier.

@Brad08414464 People don’t need a place to publish They need a reason to be taken seriously

why isn’t there an underground research community for people to publish research outside of the system and outside of conventional channels? the world doesn’t have very good infrastructure to enable this

@caffeinefaildev 😂🤌

When management says: “we all work equally hard here”

@buildwithshyam Yes, now it’s just two of us getting lost together

@polya444 With Ai as well ?

What’s your biggest distraction while coding? - Notifications - Social media - Random ideas - Debugging loops

@garrytan This is just good orchestration in practice

Two more gstack skills in the next 24 hrs: 1/ Using Codex as your brilliant near-non-verbal code review buddy who gets called in when you need the extra brain power 2/ If /browse gets stuck, we go from headless browser to Chrome and you can take over to fix, then pass it back

I’m starting to see code less as an asset and more as a responsibility. Every line carries weight: you have to read it, test it, debug it, and explain it to someone else (or to yourself in 3 months). So when you delete code and the system still behaves the same, you didn’t just “clean up” - you reduced future problems. It’s a quiet kind of improvement, but it compounds. Less code, fewer surprises, more clarity.