copyconstruct

6 ms·

1.
by copyconstruct 7y ago
Netflix also wrote about the drawbacks on this approach https://medium.com/netflix-techblog/netflix-edge-load-balanc...
2.
API versioning and evolution with proxies(medium.com)
2 points by copyconstruct 9y ago|0 comments
3.
Technical Decision Making(medium.com)
2 points by copyconstruct 9y ago|0 comments
4.
lsof(medium.com)
18 points by copyconstruct 9y ago|0 comments
5.
The method to epoll's madness(medium.com)
1 points by copyconstruct 9y ago|0 comments
6.
by copyconstruct 9y ago
I'm the author of that post. The goal wasn't to mislead - like I mentioned, I'm learning these things myself and definitely could've gotten several things wrong. I meant file offsets are per process, not that every pro
7.
Golang Concurrency Design Considered Harmful(medium.com)
34 points by copyconstruct 9y ago|4 comments
8.
by copyconstruct 9y ago
Curious - does that mean you serve close to 1.75 billion requests per day, out of which 350M are unique requests that exercise your stack instead of being served from a CDN. It'd be interesting to know more about what's the number
9.
by copyconstruct 9y ago
I wonder what's the breakdown between unique files delivered as opposed to files delivered from the CDN cache. Also, what's the breakdown for file uploads, manipulation and delivery? The 350M API requests per day would make more s
10.
by copyconstruct 9y ago
>At my recent companies, I've even seen senior developers, people with fancy degrees and 200k+ salaries, write code that's horrendously hard to understand and maintain, because it's endlessly duplicated and squashed into a
11.
by copyconstruct 9y ago
Author of the article here. That's primarily the reason why there are no "concrete examples", because one person's concrete example is another person's definition of contrived. Splitting hairs over some toy example
12.
by copyconstruct 9y ago
Author of the article here. Nope, the article doesn't conflate DRY and small functions. But the quest for DRY can lead to an explosion of small functions, which isn't necessarily a good thing. The vice versa is true as well - many
13.
by copyconstruct 9y ago
Author of the article here. >The goal is not to make small functions for the sake of making small functions, but it's to compartmentalize some functionality into a nice, easier to reason about thing (function). This tendency is exa
14.
by copyconstruct 9y ago
Author here. > "The claims that "all abstractions leak" and that adherence to DRY makes code "hard to follow" is what gives me this impression." That's a simplistic -- and cherry-picked -- interpretatio
15.
by copyconstruct 9y ago
Author of the article here. I find it really interesting you mention this: >>"when you find yourself violating them, you're supposed to question why" This is essentially what I see a lot of programmers (including myself
16.
by copyconstruct 9y ago
Author of the article here. A few things. First, I'm not sure you actually bothered reading the article, because the conclusion very obviously states what you're suggesting here, in that: "This post’s intention was neither to
17.
Ask HN: What's the best technical book that came out in the last decase
5 points by copyconstruct 9y ago|2 comments
18.
by copyconstruct 10y ago
There was a good talk at Strangeloop about userland thread runtime scheduling in both the Go and the Erlang VM. https://www.youtube.com/watch?v=8g9fG7cApbc
19.
by copyconstruct 10y ago
Paper by 53 or Sketches or Sketchbook or any of the several sketching apps available for the IPad would be my guess.