Tweetovi

Blokirali ste korisnika/cu @kimjoar

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @kimjoar

  1. proslijedio/la je Tweet
    29. svi 2019.

    Many tools people adopt force you back into thinking about the way you write the code over the way the product works. I worry many devs would rather follow a bunch of clean code rules but have a janky UI than have code inconsistency and an amazing UI. Code is a means to an end.

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    30. tra 2019.

    I am excited to finally be able to share the new completely rebuilt from the ground up with React and Relay!

    Poništi
  3. proslijedio/la je Tweet
    6. lip 2018.

    My world would be measurably less fun if Ryan Dahl hadn't made Node.js, even though he has regrets about the implementation. All shipping software has regrets built in—we can only hope that those regrets impact developers and not end users.

    Poništi
  4. 20. tra 2018.

    After a fantastic journey today's my last day at . I've had tons of fun and learned a lot — and I even got to be a digital nomad and travel the world for a year 😍 Now I've got a week to relax, then I'm off to London and

    Poništi
  5. proslijedio/la je Tweet
    31. svi 2017.

    Elastic Cloud Enterprise is here. Centrally manage all of your assets on any infrastructure with ease:

    Poništi
  6. 14. svi 2017.

    Great intro if you want to learn about how Immutable.js works under the hood.

    Poništi
  7. proslijedio/la je Tweet
    14. svi 2017.
    Odgovor korisniku/ci

    If "requirements" don't change as you write code, you're building a shitty product. Your code might be great, but at that point...who cares?

    Poništi
  8. 12. svi 2017.

    Verifying myself: I am kimjoar on Keybase.io. 3eULfO8T53QSxuuw0FLIRHaGA3lqFNvIYS5A /

    Poništi
  9. proslijedio/la je Tweet
    31. ožu 2017.
    Odgovor korisniku/ci

    Not just syntax, but repetition too. Early abstractions are almost always harmful. Explore the problem space, and then reduce code.

    Poništi
  10. proslijedio/la je Tweet

    Related to "value improvement over consistency": thoughts on creating abstractions. ⚡️ “Is your code too DRY?”

    Poništi
  11. proslijedio/la je Tweet
    25. ožu 2017.

    I think I *finally* understood 's talk on taming the metalanguage

    Poništi
  12. proslijedio/la je Tweet
    Odgovor korisniku/ci

    But "designers must code?" It's a sign that we still aren't giving UX and front-end dev the level of respect BOTH demand. You need BOTH.

    Poništi
  13. proslijedio/la je Tweet
    23. velj 2017.

    I prematurely generalized at wrong level. Took perhaps an hour or two to do. Built things on top of it. My untangling now 10h and counting.

    Poništi
  14. proslijedio/la je Tweet
    2. velj 2017.

    Regular reminder that an abstraction that doesn't add significant value or clarity is often more costly than the boilerplate it replaces.

    Poništi
  15. proslijedio/la je Tweet
    29. sij 2017.
    Poništi
  16. proslijedio/la je Tweet

    The best technical discussions focus on trade offs under a given set of constraints; not better or worse comparisons.

    Poništi
  17. proslijedio/la je Tweet

    Everything is much easier when you discount error handling. And that's why creating solid software is very hard.

    Poništi
  18. 25. pro 2016.

    Been nomading for almost four months. Working at and being able to travel the world at the same time is pretty nice!

    Poništi
  19. 14. pro 2016.

    Also, good example of some of the things we do: (by )

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·