just-boris

@boriscoder

Making frontend of . Opinions in this account are my own.

Berlin, Germany
catatron.com
Joined June 2012
266 Photos and videos Photos and videos

Tweets

You blocked @boriscoder

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @boriscoder

  1. Retweeted
    Nov 21

    Want to contribute to ? Think twice! They may ignore your PR and after some time just implement your idea by itself. Yeah, that's fine for the project, but isn't fair for you.

    2 replies 15 retweets 38 likes
    Undo
  2. Retweeted
    Nov 24

    This article (originally saw it by tip from ) is one big reason to avoid magic APIs like this: they tend to fail or obscure the “grep test“. You can never know what’s a safe and complete way to find all occurrences.

    2 replies 28 retweets 118 likes
    Show this thread
    Show this thread
    Undo
  3. Nov 15

    I just published "Peeking under the hood of redesigned Gmail"

    7 replies 103 retweets 288 likes
    Undo
  4. Retweeted
    Nov 14

    # Keeping up with two git identities While everything may seem to be working fine with your simple global git name and email. You might want to use different git identities for different set of projects.

    2 replies 5 retweets 6 likes
    Undo
  5. Retweeted
    Nov 12

    🔥 JavaScript performance advice: 1. prefer `async`/`await` over hand-written promise code
 2. prefer native promises over userland implementations

    🚀 Faster and easier-to-debug async functions and promises are coming to V8 v7.2 & Chrome 72!   and shed some light on the recent improvements:
    18 replies 575 retweets 1,503 likes
    Undo
  6. Nov 9

    Today I found next level of monkey-patching. Override Node modules loader to modify the source code on the fly

    1 reply 1 retweet 6 likes
    Undo
  7. Retweeted
    Nov 1

    When you discover a bug, ask yourself if it's an Oopsie or a Modeling Problem. An Oopsie is nbd. Write a test, fix it, and move on. A Modeling Problem is a bug that reveals a fundamental flaw in your program. These are harder to "fix" — but they also lead to the biggest wins.

    9 replies 299 retweets 933 likes
    Show this thread
    Show this thread
    Undo
  8. Retweeted
    Nov 1
    Replying to and

    Perf recommendations tend to outlive the problem they’re addressing. I regularly run into folks who still avoid Array#forEach “because I heard that’s slow”?

    2 replies 1 retweet 17 likes
    Undo
  9. Retweeted
    Oct 29

    🎉 Announcing 🚫💩 lint-staged with support for partially staged files:

    11 replies 91 retweets 224 likes
    Undo
  10. Oct 27

    All images there are very real! Modern technologies are awesome!

    I am doing a small study to learn about people's ability to distinguish between photos and photo-realistic computer graphics. To participate visit . Also please retweet to reach a wider audience.
    1 like
    Undo
  11. Retweeted
    Sep 11

    Wait um what. via at

    18 replies 144 retweets 340 likes
    Undo
  12. Oct 23

    Wow, there is new layout of the Github's navbar. It aligns with content pretty nicely on my 27" screen.

    1 reply 1 like
    Undo
  13. Retweeted
    Oct 17

    The current state of the class fields proposal is that these classes are NOT equivalent. If you see your coworker doing helpful refactors from X to Y, stop them, because they might be breaking something.

    9 replies 11 retweets 15 likes
    Show this thread
    Show this thread
    Undo
  14. Retweeted
    Oct 15

    Long, emotional and very good story of ex googler In a compiled thread over here

    Now that Google+ has been shuttered, I should air my dirty laundry on how awful the project and exec team was. I'm still pissed about the bait and switch they pulled by telling me I'd be working on Chrome, then putting me on this god forsaken piece of shit on day one.
    Show this thread
    2 retweets 6 likes
    Undo
  15. Retweeted
    Oct 11

    Web components are a complete waste of time and effort at this point. The champions of web components are too invested to admit it, but there are so many problems with the current spec. They haven't learned anything from the current state of the art of building UI for the web.

    52 replies 196 retweets 722 likes
    Show this thread
    Show this thread
    Undo
  16. Retweeted
    Oct 12

    I love how easy it is to get started with Next.js from

    24 replies 133 retweets 915 likes
    Show this thread
    Show this thread
    Undo
  17. Oct 1

    Recently I learned, that require.context in Webpack accepts forth argument, mode, where you can switch context to load chunks asynchronously. You don't have to learn it hard way, as I did, because I contributed a documentation change for it. Enjoy!

    2 retweets 2 likes
    Undo
  18. Sep 28

    Very wonderful TypeScript guide: When you the official documentation is not enough, you might look in there

    4 likes
    Undo
  19. Sep 20

    Using native array sort is hard. lodash.sortBy function rocks!

    Replying to @mathias @kaelig and 2 others
    A good comparison function always handles all possible cases (-1, 0, +1). E.g. [{ a: 'Foo' }, { a: 'Bar' }].sort(({a}, {b}) => { if (a === 'Bar' && a === b) return 0; if (a === 'Bar') return -1; if (b === 'Bar') return 1; return 0; });
    Undo
  20. Retweeted
    Sep 13

    `git checkout -` is such a convenient trick. Jumps to the last branch you were on. Works great for toggling quickly between master and a feature branch.

    18 replies 92 retweets 354 likes
    Show this thread
    Show this thread
    Undo

@boriscoder hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·