nirvdrum

85 ms·

871.
by nirvdrum 14y ago
IntelliJ has inspections for long class and method names. A lot of Java devs run that. Long names are frequently derided in the Ruby community as being Java-like. I can't speak to Haskell at all. But generally whenever something needs t
872.
Real-time QA: staying confident with code(guardian.co.uk)
11 points by nirvdrum 14y ago|0 comments
873.
by nirvdrum 14y ago
Oh, I get the concept. I've just been doing this for a while and see it fall part constantly. The problem is always that what is clear to you isn't clear to everyone else, including yourself somewhere down the road. And decomposing every
874.
by nirvdrum 14y ago
The author seems to like the minimalistic comments. I wonder if the team looked back what their thoughts would be. I can barely look at code I wrote a year ago and not ask what the hell I was thinking, but in my mind it was absolutely cle
875.
by nirvdrum 14y ago
This is going to sound extreme, but I did measure it. Roughly 30% of my time was spent just managing dependency updates for quite some time. That, to me, felt absurdly high. But, the problem was transitive dependencies and their changing
876.
by nirvdrum 14y ago
We've been doing the same for the past year or so at Mogotest and the results have been great. To build on the points in the articles: - Exceedingly few gems provide any semblance of a human-readable changelog and even fewer care about tar
877.
by nirvdrum 14y ago
You could always download it from their service, too. I routinely download tracks on my phone so I have something to listen to when I have poor mobile service.
878.
by nirvdrum 14y ago
Good to know. Thanks.
879.
by nirvdrum 14y ago
Well, the old gems will still work. But assuming you want to get any sort of security fixes, you need to backport all that yourself. I'm surprised you haven't run into more issues with gems targeting 1.9 now.
880.
by nirvdrum 14y ago
invokedynamic is new in JDK 7. It still has some maturing to do, but JRuby is already targeting it.
881.
by nirvdrum 14y ago
AFAIK they did keep turn-by-turn directions off iOS though. It's been a while since I've used an iPhone so I can't readily verify that.
882.
Speed Up Web Testing with a Caching Proxy(blog.mogotest.com)
4 points by nirvdrum 14y ago|0 comments
883.
by nirvdrum 14y ago
It's hard to say. Other communities do this much better. Java is obviously the poster child for backwards compatibility, but Python is much better too. Ruby makes supporting multiple versions very simple in most cases, but there's no wil
884.
by nirvdrum 14y ago
In theory, there's nothing preventing you, but in reality it's just way too difficult. I put off upgrading to Rails 3 for a long time because of the rspec 2 fiasco and because Rails 2.3 was much faster. But, the problem is the rest of the
885.
by nirvdrum 14y ago
Pardon my ignorance, but what made this a great idea? I'm not overly familiar with the company, but it seems like yet another "instead of going to place X to have service Y, X will come to you." It doesn't strike me as entirely novel. An
886.
by nirvdrum 14y ago
Likewise, what most people really care about is the delta. Absolute matches work when the initial state is 0, but it's fun watching these sorts of tests fail when that's not the case.
887.
by nirvdrum 14y ago
I've been using Sidekiq for a while now and also purchased the pro license. But using redis as a store is only nice when everything is going well. I've managed to have production blow up on me because cascading job failures caused redis t
888.
by nirvdrum 14y ago
A different issue, but one that's burned me several times is when things go wrong with resque (or sidekiq), life goes to hell pretty quickly because redis needs to fit everything in memory. E.g., if a third party resource goes down and job
889.
by nirvdrum 14y ago
Partially. I'm pretty sure if you write-off that donation you need to subtract the fair market value of that mug. A real accountant could speak better to that though.
890.
by nirvdrum 14y ago
Sure, there is, but then why do I pay for GitHub? And I was mostly alluding to pull requests, issues, pages, etc. All the non-git stuff that I rely on being available as well.
891.
by nirvdrum 14y ago
It's actually quite likely. If you have a git repo listed in a Gemfile, for example, and you need to bring up a new server or deploy, you're going to have problems. Sure, the outage isn't going to last forever. But the standard, snarky r
892.
by nirvdrum 14y ago
Sure. When GitHub is online, the argument holds fine as well. I fail to see what difference that makes. Clearly the situation being described is when the submodules aren't init'd and GitHub is down (e.g., bringing up a new server and dep
893.
by nirvdrum 14y ago
Aside from the fact this argument falls apart when you use submodules or third party repos, a lot of us use GitHub for the services they offer beyond just git.
894.
by nirvdrum 14y ago
I cannot disagree any more. I haven't used a terminal that can't wrap in probably 15 years. The point of a commit message is to convey information. If you could point me to a study or something showing people retain info or learn better
895.
by nirvdrum 14y ago
On the other hand, I'm tired of short commit messages that are almost completely devoid of anything useful because the author wanted to adhere to an arbitrary restriction. It feels like the mentality that all comments are evil and can be f
896.
by nirvdrum 14y ago
Keep in mind "it looks worse if you use long first lines on the website" is a completely arbitrarily imposed issue from GitHub. A while back they just wrapped the text and all was right in the world. Now they truncate the message and it l
897.
by nirvdrum 14y ago
Interesting take on "mobile," which is a bit of a fuzzy term. So, I take it you don't consider the wifi-only iPad or the Nexus 7 to be mobile devices? I guess the concept of "mobile Web" has really made things murky.
898.
by nirvdrum 14y ago
I'm guessing you got downvoted because it's a silly point to make. Companies have stupid names all the time. No investor is going to care about that.
899.
by nirvdrum 14y ago
One of my biggest issues with JSON is it's a lot harder to generate valid JSON as a stream. Granted this may be an esoteric use case, but the quoting rules and type representations seem to require some amount of look ahead which isn't fun
900.
by nirvdrum 14y ago
I've found in offices that a lot of the times the $4 coffee is just a nice reason to get out of the building and go for a walk.

More ›