lbarrow

19 ms·

151.
Programming lessons from studying mathematics(lionelbarrow.com)
8 points by lbarrow 13y ago|0 comments
152.
by lbarrow 13y ago
Security is definitely hard, but security challenges are often proportional to your apps' surface area. If you just have a simple token-based API, your language probably has libraries that can get you started with a reasonably designed
153.
by lbarrow 13y ago
You wouldn't lose customer data if you left Braintree: https://www.braintreepayments.com/landing/data-portability-p...
154.
by lbarrow 13y ago
(I'm an engineer at Braintree.) Hey Luke, we had an internal discussion about what happened with RaceMetrics and came to several conclusions about what we could do better. The restrictions on who can use Braintree and who can't no
155.
by lbarrow 13y ago
Braintree will also negotiate with you once you hit a certain volume.
156.
by lbarrow 13y ago
(I'm an engineer at Braintree.) I can't say too much about our timelines, but we're working on it =)
157.
by lbarrow 13y ago
If you write unit tests that make assertions that would be caught by a type checker, you're writing bad tests.
158.
by lbarrow 13y ago
Jim Belk was my math professor in college -- we always knew he was a much better programmer than he let on!
159.
Comfort with tradeoffs and ambiguity(lionelbarrow.com)
2 points by lbarrow 13y ago|0 comments
160.
by lbarrow 13y ago
I'm super excited about the new GC and profiling tools. I actually feel like I can't wait to get back to work and try them out =)
161.
by lbarrow 13y ago
In Go.
162.
by lbarrow 13y ago
This reminds me of "The 1/2 News Hour". It an attempt by Fox News to replicate the success of the Daily Show by making a comedy news show from a conservative perspective. Predictably, the show was so tone-deaf and unfunny tha
163.
by lbarrow 13y ago
Great read. In the end, it seems like a classic failure to resolve the innovator's dilemma. IBM decided that the future of computing would revolve around mainframes because they liked mainframes , not because that's where the fac
164.
by lbarrow 13y ago
"Unlimited vacation time" isn't always a red flag. I work for a company with unlimited vacation time (Braintree) and I've always felt comfortable taking vacations. In fact, in June I went to Europe for over 3 weeks, and
165.
by lbarrow 13y ago
"No regulations" sounds great up until the moment when the bank gets robbed, the police don't care, and the only proof that it wasn't an inside job is a screenshot of the banker's email[1]. (Not that I think that it
166.
by lbarrow 13y ago
Mentioning that stereotypes exist isn't the same thing as reinforcing them.
167.
by lbarrow 13y ago
Good job assuming that anyone who writes an introduction to Clojure is a straight white dude. As it turns out, you're completely wrong.
168.
by lbarrow 13y ago
ValleyWag pretty much nailed it: "Beer. Dance floor. Shot bar. Food truck. Girls." Nerds. Obliviousness. Poor judgment. Skewed cultural views. Social regression. Bros. MySQL. Crushing it. A party atmosphere combined with everythin
169.
by lbarrow 13y ago
Ah, thanks for the clarification.
170.
by lbarrow 13y ago
I'm going to guess with credit cards. Credit card numbers are much safer to use online than debit cards, mostly because credit card dispute mechanisms give consumers a lot more power. If a merchant behaves in an unsavory way, with a cr
171.
by lbarrow 13y ago
I'm an engineer with Braintree. This deal will not affect our participation in the Credit Card Portability Standard.
172.
by lbarrow 13y ago
sync/atomic would indeed be the way to solve this problem.
173.
by lbarrow 13y ago
"SQL" is not a database.
174.
by lbarrow 13y ago
The article totally lost me when the author called Godel's incompleteness theorem a "cheap trick" used to "frighten mathematicians". That comment makes it clear that despite his claims to the contrary, the author is
175.
by lbarrow 13y ago
Thats... not how statistical significance works.
176.
Introducing Examples, a behavioral testing library for Go(lionelbarrow.com)
2 points by lbarrow 13y ago|0 comments
177.
by lbarrow 13y ago
Seems entirely appropriate in this case.
178.
by lbarrow 13y ago
Your code shouldn't be designed to reflect what you believe is going to happen to the program eventually; it should be designed to fit the requirements as they are right now. If a Pet class makes sense later on, add it later on.
179.
by lbarrow 13y ago
I chose that example precisely because it makes sense to have a Pet class that holds common code between Dogs, Cats and Chickens. When the code only contains Dogs, though, the Pet class is unnecessary, even if you plan to introduce Cats at
180.
by lbarrow 13y ago
(OP here.) I agree that code examples would be better than intangible statements; I included a few samples in early drafts of this post, but ultimately concluded they made it too long. I'm not saying we shouldn't try to make compo

More ›