HNHacker News
TopNewBestAskShowJobs

jfrisby

68 karma · joined October 19, 2010

[ my public key: https://keybase.io/mrjoy; my proof: https://keybase.io/mrjoy/sigs/oOGXJA1w21RMWUtFLk33LJ3WXi07YCdbrAOSDJbALcs ]
submissionscomments
jfrisby··on New platform for fucking with Debt Collectors
And my point is that the default behavior of both collectors -- the behavior from the very first word of their first call -- was in violation, and they continued to violate the law in numerous ways.

If an entire industry is so systematically rotten that good behavior (read: compliance with the law) is the exception rather than the norm, what is one to do?

For example, if the debt collector does not provide any written notice and refuses to provide an address to which one can mail a written notice of dispute, what is one to do?

If the debt is intrinsically fraudulent, and the "validation" of the debt consists solely of confirming its veracity with the party committing fraud, what is one to do?

If one tries to dispute a fraudulent claim when speaking to a debt collector on the phone and one is told "I don't fucking care, if you don't give me a goddamn credit card number right fucking now I'm going to garnish your wages and fucking destroy your credit!", what is one to do?

And don't tell me that I should complain to the FTC -- since there was no written communication, and I couldn't identify the parties involved, they were unable/unwilling/uninterested in helping me.

At this point I have no sympathy for debt collectors. The very best of them are preying upon people who are already in a bad position and that's being generous.

I'm almost tempted to be late on a bill or two just so I can use this service (whatever it may be -- still can't access it) in an attempt to discourage these vermin from continuing in their chosen "profession".

jfrisby··on New platform for fucking with Debt Collectors
I've faced two situations involving collectors: In one, I had forgotten to pay a bill in a timely manner. In the other, the bill was BS and the former landlord who sent it to collections was breaking a number of related laws (such as double-dipping).

In both cases, the default behavior of the debt collectors was to... break the law. The Fair Debt Collection Practices Act exists for a reason and its only peoples' ignorance of it that allows the grotesque tactics they employ to continue unabated.

(BTW: The $100 bill I forgot about? I promptly paid it once I was reminded of it. The $5,300 the landlord claimed I owed? That went away the moment I pointed out I had proof of their malfeasance.)

"Just doing their jobs" is not an excuse for bad behavior, ever.

jfrisby··on Ask HN: What is Coinbase's Personnel Security Like
An alternative to the insurance model is to implement something like SSS ("Shamir's Secret Sharing")...
jfrisby··on An Unusual Case for Cucumber
> The state exists only in your application, not in the test. > Your given sets up the environment in the way you want, the > "when" manipulates the environment and the "then" checks > that the environment exists in a particular setting.

Err, are you asserting that that is what I am doing, or what I ought to be doing?

And yes, time-dependent code is evil. I should probably add commentary to my style-guide to explicitly call that out, but thankfully we never ran into that despite testing of distributed-job-queue functionality, by virtue of having a queue so simple stubbing its main loop to work in-process in a deterministic way was trivial.

Your example should be in violation of the style guide for precisely the reason you state, among several others (blurring of concerns, etc). If my style guide isn't clear on that point -- that a When should NEVER follow a Then -- I need to clarify that. :)

I recall a Gherkin-based testing framework that handled the actual step definitions MUCH differently and much more cleanly but I never got around to fully switching us over and don't recall the name... :-S

jfrisby··on An Unusual Case for Cucumber
To use your example -- how desirable is it to generalize "I change my name" to something "reusable"?

I'm finding these days that a pairing of .feature to corresponding step definition file allows for fluid language, simple step definition code, and well-compartmentalized messes (as opposed to the big ball of mud that Cucumber step definitions often become). Code reuse can happen through test helper classes that are called from step definitions as needed. (FactoryGirl would be an example of a very generalized test helper class, in my mind -- but more system-specific ones can be handy, albeit one wants to avoid making stateful / complex test helper code!)

jfrisby··on An Unusual Case for Cucumber
So your example still requires that state exist, it's just far more global. I.E. there must be some prerequisite code that sets up the thing to which "I" refers such that it's available to any step at any time. There may be some good patterns for that -- and that approach may be an excellent way to keep step definitions clean and simple, but I think it's somewhat orthogonal to my point.

I'm still not with you on the timing thing. By the time that step is reached, either the state has changed, or it hasn't. We address the need for it to be able to see "back in time" by storing a history of the state of the object in a way that is accessible to the steps. I.E. For steps like this:

  Given a credential for a supported vendor
  When I change the nickname
  Then the edit version should not be changed
The step definitions might look like:

  Given /a credential for a supported vendor/ do
    @thing = FactoryGirl.create(:'credential/amazon', :valid)
    @thing_history = [@thing.attributes.dup]
  end

  When /I change the nickname/ do
    @thing.nickname += " meh"
    @thing.save!
    @thing_history << @thing.attributes.dup
  end

  Then /the edit version should not be changed/ do
    @thing_history[-1][:edit_version].should == @thing_history[0][:edit_version]
  end
(The use of "@thing" is a way to encourage myself to only be talking about one object at a time...)

Perhaps that's a somewhat obtuse way of handling things -- and there's likely ways of DRYing up that pattern, if it's worth preserving, but it's proven to be fairly effective for me in the past.

And yeah, Cucumber might make a good vehicle for that sort of testing. Quickcheck sounds like a brilliant idea -- although a bit terrifying in the context of a slow language like Ruby. Would love to get my hands on / build a tool like that...

jfrisby··on An Unusual Case for Cucumber
I don't quite get how any when/then could NOT be dependent upon previous givens.

Also, despite the job-centric nature of the .feature, it wasn't timing-dependent because we mocked Resque to keep an in-process queue that we could dispatch in whatever order we want. So out-of-order arrival was deterministically achievable, etc.

And yes, that test is testing a simple property -- it's effectively a unit test, with greater clarity of intent.

Not familiar with quickcheck, but I will look into it, thanks!

jfrisby··on 68% of the Fortune 100 are Clueless
That's precisely how we look at it internally -- IaaS, PaaS, and SaaS. We speak in terms of "the cloud", as coarse and imprecise a term as it is, because that's what a lot of the people we're trying to reach are thinking in terms of and looking for. Plus, it just flows more smoothly than "IaaS/PaaS/SaaS" in a headline. :)
jfrisby··on 68% of the Fortune 100 are Clueless
One Tool to Rule them All would be nice, but at the moment we're focusing on a fairly specific niche to address real problems we've personally encountered at companies. We're not the only ones who've had these sorts of problems either:

http://gigaom.com/cloud/cloud-computing-fiascos-lessons-from...

The key thing here is really to address two things that seem to come up a lot:

1) Cost items that can vary considerably and where a mistake -- code bug, forgetfulness, sloppiness, whatever -- can leave you with serious sticker shock. (At one company we were at, an engineer spun up a couple hundred EC2 instances for a map/reduce job and forgot about them, racking up an extra $100,000 that month.)

2) Cost items that don't vary much but which have such a low friction to signing up that you wind up with bunches of accounts across an organization without realizing it.

Finance departments already tend to have the software purchase cycle fairly well managed, but SaaS/PaaS/IaaS doesn't fit nicely into those procedures. Because of that, we're building our tools to play nice with others, so whether your finance group is managing things in Excel or you have a fancy SAP based system we're working to make it easier to get this data where it needs to be.

jfrisby··on 68% of the Fortune 100 are Clueless
It depends on who you're circumventing. If you're making an end-run around an obstinate IT department -- a situation we've seen a lot of -- then this is precisely the sort of tool that finance would want to help bring things back into the corporate-governance fold.

If you're circumventing finance, then we may not be a particularly helpful tool for you.

jfrisby··on All your cloud costs in one place like Mint.com for Clouds
It's amazing how quickly cloud costs can get out of hand with ephemeral dev servers, sloppy application code, and the like. At one job, I found a bad query that was costing us ~$112k/yr in excess EC2 costs and nobody had noticed the impact because nobody outside of finance was really paying attention to the costs.
← PreviousPage 3 of 3