PaulColomiets

@PaulColomiets

Software Engineer at . Opinions are my own.

Ukraine
Vrijeme pridruživanja: siječanj 2008.

Tweetovi

Blokirali ste korisnika/cu @PaulColomiets

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

  1. 31. sij

    There are few more, like spaces around operators. But I very much agree on that.

    Poništi
  2. proslijedio/la je Tweet
    31. sij

    Embrace discomfort, it’s a signal that something needs your attention. “Yet, got pushback. Lots of it. Boss said was bringing up uncomfortable and difficult topics. Was hired to make the firm better, but the firm’s leadership wanted to believe they were already great.”

    Poništi
  3. proslijedio/la je Tweet
    30. sij

    Водій змушує вас переглядати піратський контент в автобусі та ще й виробництва країни, яка 6 років тому анексувала одну частину вашої країни та окупувала іншу? Власник компанії каже, що не має грошей платити за ліцензований контент? 👉

    Poništi
  4. proslijedio/la je Tweet
    29. sij

    Hi everyone! Please consider myself if you’re looking for experienced / developer for your remote team. More details available at my CV: Thanks!

    Poništi
  5. proslijedio/la je Tweet
    27. sij
    Poništi
  6. proslijedio/la je Tweet
    23. sij

    One of the most effective things you can do to build better habits is to join a culture where your desired behavior is the normal behavior. New habits seem achievable when you see others doing them every day.

    Poništi
  7. 19. sij

    Nice typo! I were thinking of more free time of course :)

    Prikaži ovu nit
    Poništi
  8. 19. sij

    By "easy" I mean it's a long and boring but straightforward task (if you're familiar with HTTP in depth). Not "easy" as "write five lines of code".

    Prikaži ovu nit
    Poništi
  9. 19. sij

    If I would not be employed currently or had more free memory I were already saying "challenge accepted" I think it's extremely easy to write a client in current that passes that test (and still full enough and practical of course)

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    17. sij

    If anyone leaving Mozilla or DigitalOcean is looking for a new place to work please DM me, we'll have a few positions at EdgeDB open soon.

    Prikaži ovu nit
    Poništi
  11. 17. sij

    The context of this thread is this:

    Prikaži ovu nit
    Poništi
  12. 17. sij

    The problem with projects sunsetting too late is that a community starts to adopt new things even later (waiting maybe it will eventually shut down) which leads to less innovation in the tech as the whole.

    Prikaži ovu nit
    Poništi
  13. 17. sij

    I have to admit that this is extremely hard to do when you are that only maintainer.

    Prikaži ovu nit
    Poništi
  14. 17. sij

    I'm starting to think that it's responsible to sunset the sufficiently large open-source project if you haven't found any co-maintainers. And it should be done before the project reaches too much popularity. Not sure how to measure the size and the popularity though.

    Prikaži ovu nit
    Poništi
  15. 16. sij

    On the contrary, I've spent a whole few hours today fighting with the type system. This is rare enough so I notice such days as exceptions.

    Prikaži ovu nit
    Poništi
  16. 16. sij

    This is another thing that I have never seen handled in Python (perhaps, because everybody hides Python behind a proxy). But we want it to be handled in every Rust application which is a network server.

    Prikaži ovu nit
    Poništi
  17. 16. sij

    It could be only me. But I observe something similar from a lot of folks asking things on a github.

    Prikaži ovu nit
    Poništi
  18. 16. sij

    It might be easier to copy what Python code had, but that's not how I usually approach the problem in Rust. Because well, who will push a larger than memory data to a Python process? And people using Rust tool: It's slow handling a few gigabytes? How dare you?

    Prikaži ovu nit
    Poništi
  19. 16. sij

    Coding takes more because the code quality I do for Rust is much better than what I usually do in Python. For example, I'm rewriting pretty-printing code that buffered the whole data as opcodes in-memory to Rust code the has both: asynchronous input and buffers only bytes.

    Prikaži ovu nit
    Poništi
  20. 16. sij

    A lot of people ask me how much slower is to write in than in a scripting language. My answer: it's slower but not in a way you think. Fighting with types or the borrow checker takes only a percentage of time...

    Prikaži ovu nit
    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:

    ·