phillmv

20 ms·

211.
by phillmv 13y ago
Well, they do have an algorithm. That's why this service works. Unless you were selected at random, no one reads the paperwork you submit until someone thinks you've done something wrong. They're just evidence that will be ex
212.
by phillmv 13y ago
Few things depress me more than climate denialists. They're the real life equivalent of http://gunshowcomic.com/648
213.
by phillmv 13y ago
From the article, the issue is that the Ruby GC is triggered on total number of objects, and not total amount of used memory. The article claims this got worse with the new generational GC algorithm, which sought to minimize the amount of w
214.
by phillmv 13y ago
Can you quantify how much memory you're saving per worker?
215.
by phillmv 13y ago
I think the problem is that we don't seem to have hypothesis' that guide our interpretation of the numbers. In the absence of a guiding framework on how to interpret your data, you're bound to min-max individual criteria; we&
216.
by phillmv 13y ago
Heroku's kind of in a sweet spot. They already charge an immense premium over your own fleet of micro to large instances, but by the time you rack up enough dynos for it to make sense to spend the necessary weeks migrating your infrast
217.
by phillmv 13y ago
I worded it unfortunately, but we're getting at the same thing. What I mean to say is the easier it becomes for everyone to get everything right all of the time the more likely it is to occur. Expecting everyone to individually know an
218.
by phillmv 13y ago
>When I make mistakes, which I often do, I don't go around thinking oh, darn, they should have known that for me. Well, you should! These are mind numbing details that are best taken care of by other people. I am too concerned with
219.
by phillmv 13y ago
The excuse is precisely that there isn't a great, all encompassing framework. Setting up a scenario where everyone has to get everything right all of the time is setting everyone up for a lot of heartbreak. Having bad password manageme
220.
by phillmv 13y ago
>The benefits Clojure brings to the table more than make up for the work in either case. No one's saying "stop using clojure". The argument here is "build a clojure framework lots of people use". >There's
221.
by phillmv 13y ago
> They simply cannot really screw over engineers. All they can do is bargain. We say this now , because the industry is growing so rapidly that it's hard to feel shafted given the sea of opportunity. But being shafted is independen
222.
by phillmv 13y ago
> Could web applications written in Go, or to a lesser extent, node.js, suffer from the same shortcomings? Yes, and they do. And there's no "lesser extent"; if I can't set up a fresh node app with the correct defaults
223.
by phillmv 13y ago
> It forced me to learn all these issues and understand them well enough to be able to customize each and align them with a products design. This is a standard developer response - I recall when Sinatra was a fresh kid on the block, and
224.
by phillmv 13y ago
Aren't you still stuck using their implementation of BigTable? I forget if that's changed. The main benefit of say Heroku is that while migrating away is not trivial, in principle you shouldn't have to rearchitect your app to
225.
by phillmv 13y ago
That's real easy - it works like any other asset. You tell it to them, voluntarily, because not doing so is tax fraud and if they audit you and find out they will punish you accordingly.
226.
by phillmv 13y ago
Separating this sort of stuff into "social issues" is I think an incorrect way to look at it. We're talking about changing normative group positions in a complex society that has delegated huge swaths of norm policing to imme
227.
by phillmv 13y ago
Because they'll be socially shunned by people who find their views to be embarrassing.
228.
by phillmv 13y ago
:%s/function/module/ and no meaning is lost :). I've yet to catch up on my lisp and fully grok the "functional paradigm" and, admittedly, passing around consts is less elegant than passing around function point
229.
by phillmv 13y ago
See, I still genuinely think we're saying the same things! We're just going about it in different ways. Rails encourages you to use the "primitives" it ships with, because they've all been more or less designed to w
230.
by phillmv 13y ago
Not to dull the shine of my own brilliance but I'm pretty sure I've seen dhh say something along those lines in his previous commentary. I've spent a lot of time thinking about this subject, and have only recently begun to fe
231.
by phillmv 13y ago
Being smart isn't good enough; you need to be able to finish what you've started. It's all about the execution and not the concept. Furthermore, he's found he prefers to select hard workers and promote them up than to pi
232.
by phillmv 13y ago
>Basically, your data-persistence objects (ActiveRecord models) become more composable because they do fewer things and rely less on associated objects being present to work properly. I agree with this entirely, and elsewhere in this thr
233.
by phillmv 13y ago
It sounds like you're letting "ease of test maintenance" drive the architecture of the rest of your app; I'm inclined to accept that incentivizing test creation will lead to more confidence in the face of changes but am
234.
by phillmv 13y ago
The solution you describe is isomorphic to the one proposed in the blog post, which I think you recognize? But both leave a lot to be desired. I personally think in both cases they are a code smell, and we ought to either introduce an objec
235.
by phillmv 13y ago
I think there's a lot of miscommunication going on - people are doing the same things but using different vocabulary to describe it - and so I'm not sure I agree with your characterization. In a nutshell, almost all DCI/servi
236.
by phillmv 13y ago
I immediately distrust all startups that don't have a team page with real human beings on it.
237.
by phillmv 13y ago
They really don't . I have almost zero control over my phone (a situation that only slightly improves with Android) and even then limited control over my workstation. You're not even allowed to use GPL'd code on Apple app st
238.
by phillmv 13y ago
Yeah but you and I don't have extremely rigid schedules that, if interrupted, can throw us off kilter for a whole week. I'm all for promoting healthier work/life balances (4 weeks vacation, anyone?), but it's not like it
239.
by phillmv 13y ago
What polarization? This is pretty much black and white. Either your business model requires the exploitation of cheap labour, or it doesn't and we're being crappy for no good reason. Now, we can talk about say the specific ways
240.
by phillmv 13y ago
Well, because right now as it stands the default is to be hostile to people with kids. And frankly, if our business culture needs to exploit childless 20 year olds then we're building a toxic, unsustainable environment.

More ›