Boris Litvinsky @borislit

Appreciator of great music and code | Engineer @Figma | ex-@WixEng, @Microsoft, @MelioPayments linkedin.com/in/borislit/ Joined April 2009

Tweets

3K
Followers

561
Following

912
Likes

5K

Boris Litvinsky @borislit

24 hours ago

@Arbel2025 אני בעד לתת את הפידבק.לא כולם גם יודעים לקבל את הפידבק, גם אם חושבים שהם כן. קרה לי ששיח הפכה למעין ויכוח על זה ש"אתם לא מודדים את הדברים הנכונים. אני לא מסכים. אסביר לך,ידידי" ונגמרה ב"לצערי זה מה שאנחנו מחפשים". לדעתי אם מתאמים מה השיחה הזאת כן, ומה היא לא - זה יכול לעבוד

0 0 3 173 0

View Details

Boris Litvinsky @borislit

3 days ago

@oriSomething Do share

1 0 0 49 0

View Details

Boris Litvinsky @borislit

3 days ago

אני ככ אוהב grilling וזה טוויסט מגניב ביותר

WILL NESS @WillNessAI

3 days ago

I built a variant of @mattpocockuk's grilling skill dedicated to frontend and it has improved how I build new apps and components. The general idea: 1. Use /grilling and /prototype as a base 2. Tell Claude to build 5 WILDLY different prototypes 3. Tell Claude to include a picker

30 64 1K 208K 2K

0 0 0 177 1

View Details

Boris Litvinsky @borislit

a week ago

@Arbel2025 Motorhead - Thunder and Lighting Down - Learn from my mistakes

0 0 1 130 1

View Details

Kenton Varda @KentonVarda

2 weeks ago

I just declared a moratorium against AI-written change descriptions (e.g. PR and commit messages, also issues/tickets) from my team. AI was writing change descriptions that were worse than useless to me as I tried to review PRs: outlining details of the code that could easily be seen by looking at the code, but omitting the higher-level framing needed to understand broadly what the code is doing. I think people like having AI write these things because the output looks structured and thorough, which makes it feel professional in a way. But this isn't actually valuable. Concise, high-level descriptions are better for everyone. If I need to use my own AI to interpret what your AI wrote then something is wrong. Let AI write code, sure, but for the description, I'd rather see your prompt than your output. We could maybe have extended agents.md with guidelines on writing descriptions, but this seemed a bit pointless since a good, concise change description only takes a few minutes to write -- not a significant time savings to delegate to AI. At least, it doesn't take long if you understand the code -- and if you don't understand the code, then I'm definitely not merging it.

147 121 2K 443K 617

View Details

Boris Litvinsky @borislit

2 weeks ago

@cherkaskyb לא יודע אם זה דל"פ. אני חושב שמי שלא מבין את זה עדיין אולי מפספס את האירוע

1 0 1 181 0

View Details

Boris Litvinsky @borislit

2 weeks ago

@DorShinar איך כלכליסט מדמיינים את הקוראים שלהם

1 0 1 108 0

View Details

Boris Litvinsky @borislit

2 weeks ago

@Marik_Sh @jxnlco Coz I like the extras codex desktop has 🤷‍♂️

0 0 1 18 0

View Details

Boris Litvinsky @borislit

3 weeks ago

Hey @jxnlco ! Any plans for a Codex Desktop side-by-side layout for threads/sessions? 🙏

1 0 1 71 0

View Details

Boris Litvinsky @borislit

2 weeks ago

@mattpocockuk Totally in favor of the change. The naming bothered me since my discussions, some technical details are also made and "prd" wasn't just cutting it. I actually call it "handoff"

0 0 1 137 0

View Details

Chris Cook @zirkelc_

3 weeks ago

How is @trpcio `httpBatchLink` able to fold multiple procedure calls into ONE batched call? Like how does `Promise.all([a.query(), b.query()])` end up in only a single HTTP request It's a pure timing trick built with a simple dataloader: Every call you make in the same tick gets pushed into one shared buffer. Only the very first call schedules a `setTimeout(dispatch)` Because `setTimeout` is a macrotask, it only runs after your synchronous code finishes. So by the time `dispatch` fires, all the calls from that tick are sitting in the buffer together `dispatch` then joins them into one request (`a,b,c`), sends it, and resolves each call's individual promise from the response array The neat part: `Promise.all` isn't special. Anything called in the same tick batches. The only thing that breaks it is an `await` in between, which yields to the event loop and flushes early I think this is a really elegant design: using the language's semantics for batching instead of exposing an explicit API

2 2 37 4K 25

View Details

Boris Litvinsky @borislit

3 weeks ago

@FinancialEduX en.wikipedia.org/wiki/Gartner_h…

0 0 1 142 0

View Details

Boris Litvinsky @borislit

3 weeks ago

@Arbel2025 @CiItay Legends in the game

0 0 1 109 0

View Details

Boris Litvinsky @borislit

3 weeks ago

@mattshumer_ How did you replicate the broiler crust? That's a hard one to crack

0 0 0 122 0

View Details

Boris Litvinsky @borislit

3 weeks ago

@DanShappir Because you are there to pass judgement on its work. It's either that or ignorance

0 0 1 125 0

View Details

Boris Litvinsky @borislit

3 weeks ago

@Eli_Barbel להשתמש בmarta כתחליף לfinder

0 0 0 50 0

View Details

Boris Litvinsky @borislit

3 weeks ago

@dillon_mulroy Can you share the prompt? 👏

0 0 0 23 0

View Details

Boris Litvinsky @borislit

3 weeks ago

Weave been cooking!

Figma @figma

4 weeks ago

Bringing Weave tools to the canvas

8 36 399 29K 94

0 0 0 44 0

View Details

Figma @figma

4 weeks ago

Bringing Weave tools to the canvas

8 36 399 29K 94

View Details

Figma Weave @figmaweave

4 weeks ago

20+ Figma Weave tools are now in your Figma Design canvas. Run pre-built AI tools for specific creative tasks — style transfers, product shoots, material extraction, art direction, and much more. Pick one, drop in your inputs, and get production-quality output. x.com/figma/status/2…