kyptin's comments

This was the transformation that hooked me:

  (transform (subselect ALL :a even?)
    reverse
    [{:a 1} {:a 2 :b 1} {:a 4} {:a 5} {:a 6} {:a 8}])
  ;; => [{:a 1} {:a 8 :b 1} {:a 6} {:a 5} {:a 4} {:a 2}]]

I'm solid with Clojure, and I am not even sure how to begin expressing this transformation without Specter.

Granted, it's not clear why you would want to do this in a real program. But I'm convinced about the generic power of such transformations and have little doubt I'd find use cases (albeit probably not this use case) in real code bases.

Author here. Apologies if this came across as clickbait. Would you point to said documentation? I haven't been able to find the parts that illuminate this issue, including on the official architecture page [1]. Thanks!

https://docs.docker.com/engine/understanding-docker/

Author here. Thanks for your comment. I figured this would be obvious to some.

Question: do you know of a good resource that describes docker in these terms, such that what I wrote about isn't surprising?

The official architecture page [1] doesn't illuminate this issue. To be fair, it isn't super relevant—so long as you run Linux, OS X, or Windows. When you run alternative OS's, though, it becomes pretty important.

[1] https://docs.docker.com/engine/understanding-docker/

Well-written and well-reasoned. Thank you.

I'd like to propose a sixth rule: don't move the goal posts. In other words, don't load additional content dynamically. This violates the user's expectation of when they will be finished scrolling. I find this frustrating, and I doubt I'm the only one.

Thoughts?

a) Fair, although I think the author's justification for describing it as such is reasonable. b) Sure, but I don't think maturity is the point. I think the point is to establish a way of thinking about emotions—which I suppose might be more useful the less mature a person you're dealing with.

Hey, that's good to know about, thanks!

Oculus looks pretty nifty.

I bet Skyline does a good job helping them keep track of all the system metrics. But, I think one thing our tool does better is periodic timeseries. That's the sweet spot of our tool, and it looks like Skyline doesn't have any special considerations for periodic timeseries (although it looks like their ensemble of algorithms is extensible).

Anyway, thanks for the link! And I hope you liked our tool!

You can try the online demo here: http://altometrics.com/dynthresh/

Interesting idea! You remind me that I have seen such pricing calculators before, e.g. on Heroku's website. Yeah, I could see a more complex approach working well to let me cover all the bases. Thanks!

Ah, very good point, to consider what is easier for the customer to predict. I had not considered that. Thank you!

Nice guide! That is very useful, to consider the perceived value rather than the absolute value. And I found many other nuggets of wisdom. I look forward to reading the rest. Thank you!

Thanks for your reply. You're right, of course. But rather than try to explain my market, target user, competitors, etc., I think I can translate discussions of Github vs. Bitbucket fairly well into my situation.

So, can you elaborate? Why is Bitbucket better for closed-source and Github better for open-source projects?

Nice! I see your guide here: http://taprun.com/pricing/ . I'll check it out, thanks!

I think the Github vs. Bitbucket question is a proxy that I can easily translate into my scenario. So in that case, what are the relevant factors?

My team threw this together this week. It's a simple aid to intuition for which World Cup teams are strongest, based on goals scored and goals allowed so far during this world cup.