Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gecko
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
64 ms
·
571.
▲
by
gecko
15y ago
Fossil does not have a staging area. Instead, like Mercurial, it encourages you to stash things you do not plan to commit.
572.
▲
by
gecko
15y ago
I don't honestly know the exact pitch that our sales team is using right now, but in the case of Kiln, stories that show how powerful DVCS is compared to legacy solutions usually make one hell of an impact. You can check out http://www.fog
573.
▲
by
gecko
15y ago
Given that antimatter explodes violently when put into contact with regular matter, I kind of hope that's not how they go about achieving this. A kid who forgets to recharge his board, allowing the magnetic fields to collapse, could do a c
574.
▲
by
gecko
15y ago
You can use it either way. I usually employ it at return time, because usually there are classes (little-case C) of return types that I'm fine with being ignored. A list of objects that need to be signaled on an event, for example: it's fin
575.
▲
by
gecko
15y ago
There's a solution in Smalltalk that I'm wondering why no one's brought to Ruby. In applications where this pattern is useful, there's a class, Null, with the singleton null (in contrast to UndefinedObject and its singleton nil). nil raises
576.
▲
by
gecko
15y ago
I did that; it was called miniredis: https://github.com/bpollack/miniredis Your performance will be absolutely horrible compared to Redis. I can't see doing this for anything production-worthy. (Miniredis was made for a very specific u
577.
▲
by
gecko
16y ago
I'm not really convinced that StackExchange is the best system for that. You'd really want one StackExchange per person; otherwise, the one-answer-per-question nature of StackExchange, with voting for "correct" results, which result in biza
578.
▲
by
gecko
16y ago
There's no C in Wasabi; it's pure C#. That said, keep in mind that Wasabi's only purpose in life is as a compatibility shim so that we weren't forced to rewrite FogBugz from scratch. No products other than FogBugz will ever be written in
579.
▲
In Which I Defend the C Standard for Interviews
(thoughts.rockhymas.com)
24 points
by
gecko
16y ago
|
3 comments
580.
▲
by
gecko
16y ago
If you interviewed in Python for a dev position, then you interviewed with me or one other coworker who is also trying this experiment. The majority of Creekers still do their interviews in C, and are in fact passionate about it: http://t
581.
▲
by
gecko
16y ago
Because Khan hasn't yet redone his lectures in the original Latin.
582.
▲
by
gecko
16y ago
I use it incredibly heavily, in the same way that I use virtual desktops. I have a tab group for work, a tab group for play, a tab group for documentation. Makes it very easy to quickly jump in and out of large collections of tabs without
583.
▲
by
gecko
16y ago
Personally, I agree. I know our graphics designer whipped up one of the actual bell curve per VCS. Hopefully, we'll post it later.
584.
▲
by
gecko
16y ago
For each VCS, you had to pick between love, like, meh, bleh, and ptooey (I don't remember the exact word options). The infographic attempts to just merge those into degree-of-like, which I believe was done by assigning weights to passion a
585.
▲
by
gecko
16y ago
We have more than staging servers: we have staging accounts. I documented our full release process at http://news.ycombinator.com/item?id=2301680 .
586.
▲
by
gecko
16y ago
The releases are both automated (except for one component, as noted, which we are now automating), and are fully vetted. Here is the old release process: 1. Monday morning, the version to be used for the next release is automatically built
587.
▲
by
gecko
16y ago
EDIT : I posted a rundown of our deployment process, including where and how tests happen, and why they failed to catch this bug, at http://news.ycombinator.com/item?id=2301680 . While I'm sure there's a lot of stuff we could improve,
588.
▲
by
gecko
16y ago
Perforce.
589.
▲
by
gecko
16y ago
Probably? I'm welcome to be schooled here. 90% of the time, we can roll back instantly, because there were no database changes. 5% of the time, we can roll back with slightly more pain, because the database migrations were reversible. I
590.
▲
by
gecko
16y ago
This is probably skewed. We did our best to make sure we were getting a wide swath of respondents by also running the survey on StackOverflow, but even there, our choice of which tags to advertise the survey with probably biased the resu
591.
▲
by
gecko
16y ago
That's because it was conspicuously missing as an answer from our respondents.
592.
▲
The State of Version Control: an Infographic
(fogcreek.com)
244 points
by
gecko
16y ago
|
191 comments
593.
▲
by
gecko
16y ago
That was a fork. While they'll hopefully get merged in, they're not currently in the official queue.
594.
▲
by
gecko
16y ago
I doubt very much. They're basically using Redis as a much more powerful memcached. SQL Server still is the ultimate owner of all StackOverflow data, last time I talked to the team.
595.
▲
by
gecko
16y ago
I don't know that anyone engaged us here, but someone from VMware did engage me over at the blog: http://blog.bitquabit.com/2011/02/22/buying-vmware-fusion/#c...
596.
▲
by
gecko
16y ago
I know the first 6/last 4 rule, but Digital River requested the last five . I actually thought that was pretty explicitly in violation of PCI. Am I wrong, or maybe misunderstanding the rules?
597.
▲
StackExchange reaches 16 million users, 131% growth
(blog.stackoverflow.com)
59 points
by
gecko
16y ago
|
11 comments
598.
▲
by
gecko
16y ago
I doubt they're banning open source per se (though that's certainly possible), but rather that the GPL ought to be incompatible with the Wii's licensing for exactly the same reason it's incompatible with Apple's App Store licensing. (Even i
599.
▲
by
gecko
16y ago
I symlink all the music I care about into Dropbox, which gives me access to the music I listen to most at my office and on the road, but doesn't mean Dropbox hsa to have sufficient space to store ALL of my music. This hybrid works well for
600.
▲
by
gecko
16y ago
Having taught people both systems, I will assert, based on my personal experience, that while some developers can certainly pick up Git relatively painlessly, picking up Mercurial objectively requires less time, and leaves users less likely
More ›