Marc Brooker

@MarcJBrooker

Trying to make computers easier. Working at AWS on Serverless, mostly Lambda. I like distributed systems, formal methods and remote sensing. Views are my own.

Vrijeme pridruživanja: listopad 2013.

Tweetovi

Blokirali ste korisnika/cu @MarcJBrooker

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

  1. proslijedio/la je Tweet
    prije 15 sati

    “Judgments of effort for magical violations of intuitive physics” or “how much harder is it to conjure a frog?” This is my new favorite Tomer paper

    Poništi
  2. proslijedio/la je Tweet
    3. velj

    Our industry continues to hurt from the fact that one year is single worst length of time for certificate expirations. Too short to be rare and ignorable, and too long to build an operational muscle around renewing them.

    Poništi
  3. proslijedio/la je Tweet
    1. velj

    It's not every day that a read-after-write makes a server spend 4% of its CPU cycles in one instruction. Wrote that one up here:

    Poništi
  4. proslijedio/la je Tweet
    7. kol 2018.

    The intensity of seasons depend on where you live. About 2/3 of humans live in N. Hemisphere areas that are significantly warmer in July than January. About 1/4 experience little or no seasonal temperature change, and only ~4% are far enough South to have seasons in reverse.

    Prikaži ovu nit
    Poništi
  5. 1. velj

    The devil, they say, is in the comments.

    Prikaži ovu nit
    Poništi
  6. 1. velj
    Prikaži ovu nit
    Poništi
  7. proslijedio/la je Tweet
    31. sij

    New blog post 👇 On Parallel Programming () (Thanks to and for the feedback while I was writing this.)

    Poništi
  8. 31. sij
    Prikaži ovu nit
    Poništi
  9. 31. sij

    "..single-blind reviewers are significantly more likely than their double-blind counterparts to recommend for acceptance papers from famous authors, top universities, and top companies. The estimated odds multipliers are tangible, at 1.63, 1.58, and 2.10, respectively."

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

    Interesting to see so many top conferences aren't blind-to-accept. I also hadn't read the Tomkins et al paper before. It's a real eye opener.

    Prikaži ovu nit
    Poništi
  11. proslijedio/la je Tweet
    31. sij

    My experience teaching software engineering. (Context: I said my proudest teaching moment was getting my students to appreciate the Waterfall Model of software development.)

    Poništi
  12. 30. sij

    The intersection of hardware clocks that suck and massive software complexity trying to hide it is brutal. Also a great reminder of how hard-won operational knowledge gets baked into software over time. A big, often hidden, risk of rewrites.

    Poništi
  13. 28. sij

    I don't have alternative terminology to propose, but I think it would simplify a lot of conversations if people were more clear about which of these (or other things) they are talking about.

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

    The design philosophy is as applicable to instances, and mostly to functions, as it is to containers.

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

    I think people under appreciate how independent these are. We could replace containers-as-isolation with MicroVMs with no real change in operational properties. Containers-as-packaging could be replaced with static linking with no real change (except less convenience).

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

    Four: containers as an ecosystem. This is where all the Proper Nouns come in. These things are useful, but are one embodiment of a set of ideas, rather than an end to themselves.

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

    Three: containers as a design philosophy. This stems from the idea that if we can package and isolate software it becomes easy to run. The emphasis here is on software, rather than services, and standardized tooling trying to simplify operations.

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

    Two: containers as a packaging mechanism. Mostly popularized by Docker, this is about taking some code and a closure of its dependencies, and packaging them all up together along with some metadata.

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

    One: containers as an isolation mechanism. On Linux this is the set of cgroups, seccomp and friends that can be used to isolate processes or groups of processes.

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

    "Containers" has come to be a deeply overloaded term, and I see it causing confusion nearly every day. There are at least four things here.

    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:

    ·