Jacob Matthews

@jashmatthews

Software Engineer at views: own he/him

Berlin, Germany
Vrijeme pridruživanja: srpanj 2014.

Tweetovi

Blokirali ste korisnika/cu @jashmatthews

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

  1. proslijedio/la je Tweet
    22. sij
    Poništi
  2. proslijedio/la je Tweet
    8. sij

    I am looking for React Native/front end work in Berlin after receiving some ~interesting news~ today. I am fine, not desperate, but leads appreciated :)

    Prikaži ovu nit
    Poništi
  3. proslijedio/la je Tweet
    5. sij

    Mind blown. put 3D glasses on swimming cuttlefish to test for stereopsis and it WORKED. Cuttlefish have depth perception through image disparity!

    Prikaži ovu nit
    Poništi
  4. proslijedio/la je Tweet
    31. pro 2019.

    If you are a C or C++ programmer somehow still on the fence about whether or not you should take seriously, consider this piece from Cliff Biffle an absolute must-read:

    Poništi
  5. 28. pro 2019.

    Much Yak shaving later, I can now skip pushing and popping YARVs control frames during a trace and push the necessary VM state from the snapshot at a trace exit or before a C method call

    Poništi
  6. proslijedio/la je Tweet
    25. pro 2019.

    Beyond the hype ... breaking down Kubernetes my tongue is firmly in cheek and this isn’t meant to be taken too seriously ... ... expect maybe the bit about k8s in its current form as a set of abstractions for building a PaaS feeling super dated already in 2019. That’s true.

    Poništi
  7. 17. stu 2019.

    It took a bit longer than I expected but it's a super elegant optimization:

    Prikaži ovu nit
    Poništi
  8. 17. stu 2019.

    I have a first version of loop-peeling now.

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet

    a lot of the time, code ends up looking that way because it has to—we call it an abstraction when we like it, and indirection when we don't

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    14. stu 2019.

    So sad to read this 😢. Whenever I read about a software service I like hopping on the venture capital train to unicorn-ville, I fully expect them to go to shit. 1PW now need to beome a many billion dollar company OR DIE TRYING. That usually lead to desperate/shitty decisions.

    Prikaži ovu nit
    Poništi
  11. 12. stu 2019.

    I did this in the wrong order. Without loop-peeling, I can’t remove the existing local variable load or there’s nowhere to get the value on the first iteration

    Prikaži ovu nit
    Poništi
  12. 11. stu 2019.

    Today I added PHI nodes to carry values through trace iterations and pushed writing the local variables into snapshots

    Prikaži ovu nit
    Poništi
  13. 8. stu 2019.

    Tracing JIT now skips all the operand stack operations on trace and uses snapshots at exits.

    Poništi
  14. proslijedio/la je Tweet

    Taavi Kotka , former CIO of Estonia, on the low £100m price tag for being the most tech-savvy government in the world: “If you don’t use Accenture or McKinsey, you’d be amazed at what you can get done.”

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    Poništi
  16. proslijedio/la je Tweet
    2. stu 2019.

    they neglect to mention that it'll lead to a distrust and resentment of all authority and a budding interest in lockpicking and electrical reverse engineering.

    Prikaži ovu nit
    Poništi
  17. 3. stu 2019.

    Me trying to explain anything complicated

    Poništi
  18. proslijedio/la je Tweet

    It's bittersweet: I'm leaving , and am now retired. I've learned a lot during my time as an engineer here -- e.g. type annotations came from this experience -- and I'll miss working here.

    Poništi
  19. proslijedio/la je Tweet
    21. lis 2019.

    At ConvertKit we recently started dockerizing our production setup. One thing we missed is using jemalloc. Here's a screenshot of before/after switching to jemalloc. TLDR - if you care about memory usage with ruby, you can't not use jemalloc.

    Poništi
  20. proslijedio/la je Tweet
    Odgovor korisnicima i sljedećem broju korisnika:

    Having worked in traditional ITIL environments for over a decade, I can honestly and authoritatively say that the “regular releases reduce risk” approach here at is much safer. Majority of CABs represent organisational scar tissue from previous incidents not real risks

    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:

    ·