1337p337

20 ms·

151.
by 1337p337 16y ago
I mentioned extensions; the first half of my previous job was spent on FF plugin development. Once in a while, one of us would get frustrated enough to try looking at how extensions are built for FF; never worth it. (Our IE guy was enviabl
152.
by 1337p337 16y ago
It's true; it's a bit of an over-simpification. I was trying not to get any more long-winded than I already was. :)
153.
by 1337p337 16y ago
I couldn't agree more if I were suddenly granted the magical ability to concur with the power of a thousand suns. As far as NaCl goes, the absolute last thing the web needs is portability/endianness issues. I'm writing this comment on a ph
154.
by 1337p337 16y ago
This is tangential to your point, but I don't think that experience is correctly measured by the size of the codebases of the projects you've worked on, but rather the number of serious mistakes you've made.
155.
by 1337p337 16y ago
For a major undertaking, sure. If you're a start-up, odds are that you have one product, and you can't afford for it to stagnate while it's scrapped and rewritten or while the developers layer hacks on hacks to fix bugs created by the last
156.
by 1337p337 16y ago
That's what my strategy is. "Get it working, then get it working right, then get it working fast." The "get it working" part is where you start to be able to tell whether or not you've solved the right problem.
157.
by 1337p337 16y ago
I think you hit what the author was talking about, which is cranking out code so that it works (for whatever goal, in the case the author describes, user experience), not necessarily so that the code is good. I learned Japanese, but when sp
158.
by 1337p337 16y ago
Can they do that? I would think you'd have to use the NetSol monad and force evaluation.
159.
by 1337p337 16y ago
Certainly, if the apparent cure (which I hope and I'm sure the rest of the world hopes it is) came from embryonic stem cells, this would deplete any political capital held by the opposition to embryonic stem cell research. As the cells came
160.
by 1337p337 16y ago
Instead of subtracting 10, since the caller method provides filenames, just before the .grep you could call .reject to filter out all the framework code, or perhaps .take_while to stop when you've hit a certain point. (Those would also wor
161.
by 1337p337 16y ago
Is there some reason the author doesn't use caller.grep(/block in/).length ? Because that is right there in the language and doesn't require any of that instance variable tracking or "_with_" method syntax.
162.
by 1337p337 16y ago
(D)s, (R)s, and other letters in parentheses next to names are the sort of things that influence how people vote, and in articles like this, they affect future votes. That said, it is somewhat sad that the informed citizen is a more rare vo
163.
by 1337p337 16y ago
I recommend against that. :) A team I was on had a demo for a client, and a shaky database schema. I had used, as a test account, the username "MOTHERFUCKINYEAH" for the same purpose. The purging of this account caused a few 500 errors, a
164.
by 1337p337 16y ago
I don't think they're useful for variable names, but I use them (very sparingly) in comments. A great way to spot what needs refactoring is to find the piece that caused the most frustration to the author. Under a tight deadline, apologie
165.
by 1337p337 16y ago
I can only hope it shocks some sense into kids that use GitHub for distribution rather than putting a tarball named $name-$version.tgz (or bz2 or xz or whatever). As much as I love GitHub, is has been the bane of my automated-build existen
166.
by 1337p337 16y ago
Definitely the important part. Linus Torvalds once joked: "Only wimps use tape backup: real men just upload their important stuff on ftp, and let the rest of the world mirror it." Distributed SCMs like git are a great way to But GitHub's
167.
by 1337p337 16y ago
I suspect that this is why people tend to understand when GitHub goes down, and this allows them to be more open. All (or nearly all) of GitHub's users are tech-savvy, so we tend to understand the problems.
168.
by 1337p337 16y ago
It kind of makes me wish NILFS2 would become production-ready faster. Give MySQL its own partition, and just roll back to a previous checkpoint if you wipe everything. Not a substitute for backups, but a pretty speedy way to recover for a
169.
by 1337p337 16y ago
It's not that I don't understand "Ruby magic" or "metaprogramming"; it's that the Rails codebase is spaghetti. > I wish the idea of "Ruby magic" would die in flames! Me, too. I think Giles Bowkett had an article on this; it was the onl
170.
by 1337p337 16y ago
> Used a total of 4 times in the 2.3.10 codebase. The number of times the string "BasicObject" or "BlankSlate" shows up in the codebase is not representative of the times an instance of a class that inherits from this class shows up in
171.
by 1337p337 16y ago
I (at the risk of getting horribly off-topic) attribute this to Rails' origins, namely a team that moved to Ruby from PHP, and brought too much PHP with them. Not to take a position on PHP itself, but it's a very different language, and wh
172.
by 1337p337 16y ago
For most of high school, I had the misfortune of living in the South. (I got the hell back to civilization as soon as I could.) The little town (population 6,000) didn't see too many people move in or out, and there were grudges festering
173.
by 1337p337 16y ago
I think it's a valid prediction, but I don't think they'd accept programmers for Apple products using non-Apple products; I don't know what they'd do. But their servers are all (I hear) XServes, and they basically eat their own dog-food, s
174.
by 1337p337 16y ago
I love this article. I understand that this mode of interaction is sort of an outlier, but I have come to personally resent being prevented from doing anything by a computer. A lot of friends of mine ridicule my choice of Linux distributio
175.
by 1337p337 16y ago
And if you decide to delve into the details of Rails' implementation, you're often greeted with 100-line string evals and incomprehensible hacks. I doubt this effect was the intention, but it made me cargo-cult a lot when I was doing Rails
176.
by 1337p337 16y ago
It reminds me of their sudden decision to drop their XServe line, with no explanation or hint of follow-up. We have a guy that has specialized in "enterprise-y" Apple deployments. We have a few XServes here and the default laptop people g
177.
by 1337p337 16y ago
What scale? How many concurrent users of your specific site break MySQL, and how many concurrent users do you have? Not answering or considering those questions is what leads to premature scaling.
178.
by 1337p337 16y ago
I totally agree. I may be totally wrong on this point, but it seems to me that over-engineering (in the forms of feature-creep, premature optimization, premature scaling, over-specification, planning for too many unlikely use cases, and al
179.
by 1337p337 16y ago
The second one is way more fun, using the real device as the plaintext and the loopback as the cyphered version. Have you tried using the -C (compression) option to ssh instead of the bzip2 pipe? I don't often have occasion to do this sort
180.
by 1337p337 16y ago
At the last startup where I worked, we built our own document store (in Scheme!), with exactly the same reasoning that causes other startups to over-engineer for scale before we had any users. Premature optimization is a kind of over-engine

More ›