Dawid Ciezarkiewicz

@dpc_pw

OSS Geek and Software Engineer (at ). ~napter-matnep All opinions are my own.

Vrijeme pridruživanja: listopad 2018.

Tweetovi

Blokirali ste korisnika/cu @dpc_pw

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

  1. Prikvačeni tweet
    25. kol 2019.

    Just 11 users, narrows down potentially untrusted dependencies by 74%. Imagine where would we be if there was 1000 of us.

    Poništi
  2. 2. velj

    In case you ever need a cryptographic digest of directory content.

    Poništi
  3. 30. sij

    Because of bech32 addresses using a different address prefix on regtest vs testnet, you can't just take a piece of code and run it against a regtest-simulated test cases, without explicitly taking care of regtest prefix, which isn't even mentioned on

    Prikaži ovu nit
    Poništi
  4. 30. sij

    Giving regtest, simnet and any other test-"net" a distinct IDs of any sort is a bad idea. It just increases work for developer integrating Bitcoin. And the end user doesn't care - test money is test money, no matter on which fake network.

    Prikaži ovu nit
    Poništi
  5. 30. sij

    The answer to "Why isn't there more jobs?" is "You don't look for Rust jobs, you rewrite your current job in Rust."

    Poništi
  6. 28. sij
    Poništi
  7. proslijedio/la je Tweet
    20. sij
    Prikaži ovu nit
    Poništi
  8. 18. sij

    Users' expectations are always high, no matter if they paid $10000, $5 or $0. I'd say: especially if they paid $0, for some reason. And it's never a shame for unpaid work given away for free to be imperfect.

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

    Important thing to remember for Open Source devs (and any creators). Constant stream of negative feedback *is the best case scenario*. That means project is popular and people use it. Happy users are often contently silent.

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

    There might be great cars, there might be a great thing for the planet, yada, yada. Irrelevant. As an investment... it seems ridiculous to me. The numbers are all wrong. And a lot of stuff around Tesla is just... fishy. Looking forward into the future to see if I was wrong.

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

    For the record: I was and am pessimistic about Tesla as a business (making money). Now that the stock have done 2x, I think it's a good time to say it. I would not dare to short it, but I would never invest. If I am wrong, I'm wrong. But right now I am convinced that I'm not.

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

    Important serde trap: duplicated keys in collections are not errors. Can lead to security implications (you thought you validated all values, but something sneaked through a dup key).

    Poništi
  13. 15. sij

    Shoe size 8 can refer to: newborn, toddler, little kid, big kid or an adult, which leads to great frustration every time I'm ordering online. Aparently any practical metric system would be un-American.

    Poništi
  14. 13. sij
    Poništi
  15. 9. sij

    Watch Bao, a general purpose cryptographic tree hash, and perhaps the fastest hash function in the world: , from the time this was just a prototype.

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

    blake3: The fastest hash function in the world. Obviously implemented in , because that's what you use to implement the fastest things in the world.

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

    There's no one map that you can use to explore every unknown territory. You have to explorer individually every time, though you can help yourself with previously gained experiences.

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

    because of the fractal nature of complexity, where important details can be discovered at any level. Because of that the act of creation is an exploration and mapping process, and can't be simplified to following a generic procedure. (...)

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

    to satisfy sub-optimal higher-level design. That's why I believe that software planing and design should be done concurrently with implementation, and never (too much) ahead of it. Software engineering is very much like composing music, or painting, (...)

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

    majority of lower-level problems trivial. That's why it is important to keep the higher levels flexible and iterate on them as the feedback from implementing its lower level details is gathered, instead of just mindlessly grinding in the lower level (...)

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

    Right solutions are simple and elegant. When it is difficult to come up with a simple and elegant enough solution to a problem, it often means that the whole higher-level approach should be reconsidered. Very often right higher-level decisions make (...)

    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:

    ·