brandur

41 ms·

331.
Legacy Projects and the Maintainer(brandur.org)
2 points by brandur 11y ago|0 comments
332.
by brandur 11y ago
Interesting approach! I'd be curious to hear about the mechanic that you came up with for division of labor among workers — since every client is essentially reading the same stream, I guess you'd have to distribute jobs based on
333.
by brandur 11y ago
> I'll also note that since the beginning Que has gone out of its way to use session-level locks, not transaction-level ones, to ensure that you can execute long-running jobs without the need to hold open a transaction while they wo
334.
by brandur 11y ago
Ah, nice, thank-you! > Fortunately our job throughput is small enough to not hit any scaling issues with Postgres, so I stuck with that because of my confidence and experience w/Postgres over the years. I think we're in a prett
335.
by brandur 11y ago
> Thanks for the article, very interesting. Thanks! > What we have implemented was a Python decorator to have the tasks actually fired after the function completion (thus after the transaction commit). In Go we achieve the same result
336.
by brandur 11y ago
I'd be curious to hear what the general community thinks of putting a job queue in a database and if there are a lot of other QC/Que users out there. FWIW, the transactional properties of a Postgres-backed queue were so convenient
337.
A Month of Amazon Kinesis in Production(brandur.org)
2 points by brandur 11y ago|0 comments
338.
by brandur 12y ago
You may want to also consider this alternative: http://www.amazon.com/World-History-Timeline-Schofield-Sims/... It has the advantage of being a little more modern/complete than the original Histomap, even if it&#x
339.
Command Exit Statuses: An exercise extending the shell's API(brandur.org)
1 points by brandur 12y ago|0 comments
340.
Elegant APIs with JSON Schema(brandur.org)
1 points by brandur 12y ago|0 comments
341.
by brandur 12y ago
The Internet Archive has some alternate formats available like PDF and ePub: https://archive.org/details/ost-computer-science-the_art_of_...
342.
by brandur 12y ago
Known as an "EPIRB" [1]. That was a great episode on the Kaufmans [2]; definitely worth the listen. [1] http://en.wikipedia.org/wiki/Distress_radiobeacon [2] http://www.thisamericanlife.org/ra
343.
by brandur 12y ago
At some point they switched to a slightly different model where you would see the normal obfuscated answers with a request to log in at the top of the page, but if you scrolled down far enough, the answers would be there in clear text. They
344.
Mozilla and Free Speech(me.veekun.com)
2 points by brandur 13y ago|1 comments
345.
Microservices (comments on 200-500 LOC services)(brandur.org)
1 points by brandur 13y ago|0 comments
346.
The Mediator Pattern in Ruby (or Interactors by a different name)(brandur.org)
1 points by brandur 13y ago|0 comments
347.
Healthy Anti-patterns(brandur.org)
2 points by brandur 13y ago|0 comments
348.
by brandur 13y ago
Fair point! I'll admit that my original title was somewhat linkbait-y and fully respect the moderator's decision to amend it. That said, while the title was designed to incite discussion (and there is disagreement in a good discus
349.
by brandur 13y ago
Right. It's certainly possible, and it's awesome that many services like your own provide good clients that empower developers this way. My experience though is that some don't, and figuring out whether they do support these
350.
by brandur 13y ago
Yeah, I included this last as I think it's by far the weakest argument. I've found in the past, especially when looking being introduced to new codebases that I'll see URLs around in the logs but that the logging is weak enou
351.
by brandur 13y ago
Nice idea! I naturally worry a bit that the reader's eye will have a hard time tracking which segment it should be looking at next (say they accidentally jump from 1 --> 3 for example). But like you said, if you used the horizontal
352.
by brandur 13y ago
Z, > As with everything, the issue is twofold. In the case of Heroku and your user-base it is reasonable to expect your users are closer-to-wire than an iOS guy hacking in Cocoa Touch. Certainly! Regarding the overall question of "S
353.
by brandur 13y ago
> SDKs do have their value. I agree! And a well designed API can certainly help workaround many of these problems. I would say that fully evaluating an SDK is a non-trivial undertaking though, especially when it comes to features like co
354.
by brandur 13y ago
Great idea! I can definitely see this as a workable solution. The only thought I have is that once in a while behavior like retry/idempotency support might have to be tweaked on a per-endpoint basis rather than from the general `call`
355.
by brandur 13y ago
Hah! Call it a design experiment, and either way it's good to gather a data point that someone hates it. The multi-column layout will only trigger at large screen sizes. The idea here was to fill some of that extraneous white space you
356.
by brandur 13y ago
I agree! We've been building a CLI that uses an SDK [1] against our new API and so far it's been tremendously helpful in identifying bugs and other problems -- if we hadn't gone through that exercise then we would have inadve
357.
by brandur 13y ago
I concede this point. The article was written from the perspective of a user who's running a high volume app and wants maximum control over how they communicate with foreign services (i.e. my perspective). I certainly don't want t
358.
Why I avoid SDKs in production(brandur.org)
73 points by brandur 13y ago|43 comments
359.
Tim Harford: How can we outwit our lazier selves?(timharford.com)
1 points by brandur 13y ago|0 comments
360.
Forward security for journalists(imperialviolet.org)
1 points by brandur 13y ago|0 comments

More ›