HNHacker News
TopNewBestAskShowJobs

sturgill

893 karma · joined December 31, 2012

chris at the domain thesturgills.com
submissionscomments
sturgill··on Send money to debit cards
I was excited when I read about this when Balanced launched their beta of this same feature, and I'm equally as excited to read about it WRT Stripe. The competition in this space has provided some wonderful innovations in a very short period of time.

I had to do some integration with Authorize.net some months ago and had terrible flashbacks to the late 90's / early 00's when they were the only real player in the game for self-hosted checkouts. Reading Authorize.net documentation does not invoke happy feelings.

sturgill··on Accidental Tax Break Saves Wealthiest Americans $100 Billion
There is no inherent morality attached to paying taxes. And there is no inherent morality that dictates what amount of tax one should pay. There is a legal obligation to pay taxes, and a moral obligation to follow the law, but there is not a moral obligation to pay more in taxes than what the State requires.

Put another way: there is an intrinsic moral responsibility to not murder, but there is not an intrinsic moral responsibility to pay taxes. One could imagine a country in which there were no taxes, and such a state would not be immoral. And those who lived there and did not pay taxes would not be viewed as immoral. But if this same country did not have an explicit statute outlawing murder, we would still call people who murdered others (e.g., killed for pleasure) immoral.

Given that we are morally obligated to pay taxes strictly on the virtue that a law exists that says "You must pay this tax", how is it morally problematic to determine what you owe under the legal structure that has imposed the tax? Your moral obligation is to pay the tax as it is defined, it is not your moral obligation to pay more tax than the tax code requires.

That seems to me to be an obvious tautology: you owe in taxes what the tax code says you owe. If the tax code allows you to limit your tax responsibility by moving money through trusts, so be it. It doesn't seem any different than parts of the tax code that limit your tax responsibility for buying a home, having kids, or making under a certain threshold of money.

Whether or not the tax code, as constituted, is fair, equitable, desirable, or is having its intended effect are fair questions. But calling people immoral because they find legally sanctioned ways to reduce their tax liabilities is troubling.

I don't make enough to really worry about these structures, but I can guarantee you that if I did I would do whatever I could to reduce my legal tax responsibility.

sturgill··on TinyPNG launches API to automate PNG compression
Back when I was slicing and dicing specs that had to be compatible with IE6, I really wish I could have used TinyPNG. Preserves alpha transparency that works in really crappy browsers, without resulting to weird CSS filter shenanigans.

But even today, I really enjoy the service. Not sure what I would pay for it, but it is very convenient.

sturgill··on Friends and Family Funding and Why I'm Dreading Thanksgiving
I turned down friends who wanted to join our raise at Goalee for this exact reason. That, and I wasn't convinced that they were fully aware that you only invest in a small start-up what you can afford to lose. They guy was getting a doctorate in piano performance, and I didn't get the sense that they had a lot of extra in their lives (especially considering their three kids).

Best decision I ever made.

sturgill··on TinyPNG launches API to automate PNG compression
I'm a pretty big fan of TinyPNG. I was actually part of their beta invite for the API and wrote up a quick Ruby gem(1) to automate the process (and to auto-shrink PNGs on a Capistrano deploy). I haven't really messed around with it much since then, but it was fun to write and the team at TinyPNG was very accommodating.

Not sure what I think about their pricing structure, but I wish them the best.

1) https://rubygems.org/gems/tiny_png

sturgill··on My really successful, unfundable, piece of shit startup I hate to love
Amazon Mechanical Turk could help with this.
sturgill··on Stop Validating Email Addresses With Your Complex Regex
Forging mail headers is easy enough to do that I wouldn't consider this approach to validate an email address. Sending a validation email is much harder for spammers to bypass.
sturgill··on Did you ever take that test yourself?
First off, no need to apologize - I didn't take your criticism to mean you were affronted by my existence or anything...

Second, I don't necessarily disagree with what you call "a good testing practice." Seems pretty reasonable to assume that writing tests for what is most brittle is a good idea.

Third, you missed part of my point (and the impetus behind why I wrote that post). This might not have been a point that you even felt a desire to address, and I don't fault you for choosing to focus on other parts of the discussion. But I want to reiterate: I'm not anti-test; I'm anti-hype. I get annoyed by people who "slavishly follow test-centric practices for 'cargo cult' reasons rather without any introspection over what they are trying to accomplish." But ultimately what one group of people decides to do really doesn't matter that much to me. However, I am incredibly frustrated by the extension of the mentality that if I don't subscribe to TDD or 100% code coverage that I'm somehow a lesser human being.

sturgill··on Let people pay you. Make it easy
I'm a big proponent of SSL-everywhere, but paying Heroku $20 / month to have a custom endpoint seems absolutely obscene (especially for a small shop worried about simple once-off payments). I guess you could forward non-encrypted requests from your custom domain name to the Heroku-branded endpoint, but that is awfully ugly (and potentially scary to the end user).

Almost best to roll with a cheap $5 plan from Digital Ocean - except then you lose all of the ease of use this project is meant to solve.

At the very least he should probably highlight the possibility of MITM attacks when not serving the original page over HTTPS, but I'm not sure how to solve the SSL issue in a way that's as simple as what Heroku offers without dropping a lot of money in monthly fees.

sturgill··on There is No Right Way to Develop Software
My wife is a planner. I'm more of a "let's get in the car and see where we end up." A healthy mix of both planning and spontaneity adds a lot of variety and enjoyment to life.

Which is one reason I love the start-up scene. You start out with a plan, but the challenges come when you have to make important decisions in a moment.

sturgill··on There is No Right Way to Develop Software
Maybe not. Sometimes all you need is developers that are "good enough." I personally don't like hiring junior talent (mostly because I hate all of the hand holding it requires), but that doesn't mean it might not make business sense to go with the cheapest talent that can get the work done.

Ironically, if your company uses a lot of junior talent, the appropriate development methods might just require things like enforcing a JIRA ticket before code, always use TDD, etc.

Perhaps what I'm saying is the one true way to develop software is to choose your methodologies to maximize the effectiveness of your specific team to fulfill its specific end goal.

sturgill··on Tests Are Overhyped
We have a slightly different approach to the same problem: if people keep putting out crap code that breaks (or worse, introduces regression bugs) and I will let them go. I have no time for people who do crap work.

You use tests to weed those people out. That's fine, if it works for you.

I'm anal about knowing everything that's happening in my code. I compare git commits to ticket numbers to keep abreast of how things are changing over time. A bug comes through on Goalee and I know which handful of files it will be in. Honestly, I'm quite uptight about this stuff. I catch most shortcuts personally before they go out, and have the appropriate conversation with the responsible party.

sturgill··on Tests Are Overhyped
By "community" I'm referencing the Rails startup scene in particular, and technology startups in general. Here's a fun exercise: go find a job posting for a Rails startup that doesn't expound on the virtuosity of its TDD practices.
sturgill··on Tests Are Overhyped
To be clear: I did not say TDD was bad. I simply said it might not always be best. I took that a step further and suggested that with a start-up, and especially an early stage one, is probably not worth it. Not that it's bad or wrong. Simply that the costs might outweigh the benefits.

If you aren't market tested and/or market validated, I would suggest that getting something out the door is probably more important than test coverage. Because odds are those tests you wrote will be worthless when you pivot. There's a cost to writing tests, and the benefit from those tests are increased when they are reused. If you use a test once, then pivot and have to scrap it, you would have been better off hacking your way through the first release and getting to that first pivot faster.

Once you start to gain market traction and you actually know what the market wants you to be then your world changes and your approach to writing code should as well.

And as for junior devs, that's a tough one and a reason I avoid hiring junior talent. Not avoidable for all managers, but I didn't write my post to be the new bible. Quite the opposite: I think we're a bit too worried about making sure we're doing what everyone else says we should be doing. Rails is omasake and all...

I'm just tired of hearing everyone talk about TDD as if it were a given. Protecting against SQL-injection? That's a given. Being a TDD-based web startup? Not so much.

sturgill··on Tests Are Overhyped
OP here. My conclusion wasn't drawn from an isolated incident; I shared the incident to highlight what I imagine is a common pitfall in testing.

I used the phrase "only test what needs to be tested" intentionally. How should I know what you need to test? But if you accept that you should only test what needs to be tested, then there is an implication that some (I'd venture to say most) of what you write doesn't need to be tested. And that's a liberating concept. You aren't obligated to test everything, but you should test what really matters.

What needs to be tested is probably directly related to the size and stability of the company (assuming size and stability have a positive correlation). I would venture to surmise that young start-ups have almost no need to test anything. That comment isn't meant to be inflammatory, but I look at testing too early like optimizing too early. There's no reason to shard a database until you absolutely have to, and I don't think you need to test something until you know it's mission critical.

For example, Stripe offers a service that were components of it to fail would jeopardize their entire business. Their code base is obligated, by its nature, to have more stringent tests. But the startup in the garage next to yours who is still trying to determine MVP and will probably end up pivoting five times in the next two weeks? Save yourself a lot of grief and don't worry about the tests. Once you know what you are going to be, once you know what you can't afford to lose, well, wrap those portions up with some solid tests.

sturgill··on Tests Are Overhyped
I'm not sure that there is a sure-fire way to quantify what tests are or are not necessary. In my opinion, this is something that comes with experience and is more of an art than a science. But I'm okay with that.

If all you got out of the article was that slavishly following a process (like TDD) can be bad, I'll consider that a win for my writing. Because my general feel of the community is that testing is some sacrosanct practice that must be adhered to without question. And I question that.

I write tests. I'm not anti-test. I just imagine I write far fewer tests than most. In my opinion we should constantly question whether a certain practice (in this case, writing a specific test) is worth it. I think that's a healthier approach to development than blind red/green light.

sturgill··on Tests Are Overhyped
The key, to me, is determining what needs to be tested. That doesn't change with larger code bases. Note that I didn't say that tests were pointless or that you shouldn't write tests. That's incredibly shortsighted.

Originally I was going to title this "Tests are overrated" but that both seemed like linkbait and distorts my actual opinion.

I've been on projects where they tested to make sure that certain values were unique in the database and I couldn't help but think they: didn't understand the framework; didn't understand what tests are meant to do; didn't understand database key constraints; or all of the above.

Tests have their place. But they are a means, not an end. And I see a lot of people confusing them for the end.

But, again, I don't dislike tests. I just dislike what I perceive to be a current overemphasis.

sturgill··on Why I Code
Not at the moment, no, but I appreciate the validation!
sturgill··on Kim Dotcom puts up €10,000 bounty for first person to break Mega's security
For the record, (and as someone who is happily married) I would discourage marrying kids. It's better to wait until both of you are at least 18...
← PreviousPage 7 of 7