foca

7 ms·

1.
by foca 13y ago
Yeah, it definitely depends on the use case. Some websites just "make sense" on responsive layouts. Others… not so much :)
2.
by foca 13y ago
I have no idea :P But that's the case for which I use raw + save instead of download the zip / clone :)
3.
by foca 13y ago
For JavaScript or CSS single-file projects it's actually quite simpler to wget the one file from the Raw URL (or copy-paste the contents into a new buffer in your editor), than to clone/download the archive and then move the file
4.
by foca 14y ago
Get those pull requests merged! :)
5.
by foca 14y ago
We did, and then we dropped it because a _very_ small percentage of users were on non-English locales.
6.
by foca 14y ago
Ah, my Family Game, how many hours did I invest in it while growing up? Those "999 in 1" cartridges were awesome :)
7.
by foca 14y ago
Love it :) One suggestion, show small flags next to people in the list view as well, with the name of the country in the title attribute.
8.
On Git Workflow and General Style(blog.poteland.com)
5 points by foca 14y ago|0 comments
9.
by foca 14y ago
For all the respect you can have to Yehuda, please don't compare him to Feynman :)
10.
by foca 15y ago
Heh, rails' time_ago_in_words, but right :P
11.
by foca 15y ago
Well the obvious reason is mentioned in the article: most people already do have a facebook account, while G+ is still new for most of the internet. If you are likely to be on facebook, you probably already are. I don't think it's surprisin
12.
How do you estimate your work? (Quick survey)(docs.google.com)
2 points by foca 15y ago|1 comments
13.
by foca 15y ago
Co-located teams are better off with sticky notes and whiteboards as long as the client is also in the same room :) Either way, I work from South America for clients in the US, so I like having these tools around. Specially when they innova
14.
by foca 15y ago
Chat hooks! I want hipchat (or campfire, w/e) to say "Joe commented on…" etc. Specially new items, comments and status changes. Then I could configure github to notify sprintly and sprintly to notify the chat, instead of getting all the pus
15.
by foca 15y ago
Oh man, I can't even begin to… I mean, this is written in DJANGO?! Who thought of THAT?! :D ps: congrats on finally launching ^^
16.
by foca 15y ago
Yep, it needs an API and webhooks.
17.
by foca 15y ago
The idea of asking the credit card up-front is that it makes it clear that it's a paid service. I personally dislike it, but probably stump can give a better insight on why he chose this workflow.
18.
by foca 15y ago
In this regard I love what Chile is doing with Startup Chile. You guys seriously need something like that, where you just grant visas to smart founders. I still wouldn't like to live in the US, but I totally support that you become more ope
19.
by foca 15y ago
When was it that you used it? I haven't used it lately, and when I did I felt the same as you, but for what I've seen Dojo is no longer the "kitchen sink" it used to be. It's small, VERY modular, and has a lot of utilities and interesting t
20.
by foca 15y ago
The specific point is that the evented model is not designed as a "one size fits all" solution. It's great for certain scenarios, not very good for certain others. Basically, the original blog post tries to get to this, remarking on node.j
21.
by foca 15y ago
git?
22.
by foca 15y ago
Thanks! I didn't know of that url. How did you find it? It doesn't seem to be linked anywhere in the site.
23.
What do the green user names mean?
5 points by foca 15y ago|3 comments
24.
by foca 15y ago
The guys at c2 have already figured this one out: http://c2.com/cgi/wiki?CommunityLifeCycle Also, if you're into how communities work and why how they succeed/fail/implode, you should definitely look at Meatball wiki: http://meatballwiki
25.
by foca 15y ago
Welcome to the future. Sadly, we don't have jetpacks or flying cars yet.
26.
by foca 15y ago
I really disagree with your point on the community valuing monkeypatching so much. Yes, it's a tool. Yes, it has it's place. No, it's not the favorite tool in our belt. And no, it's not something you should use always. At least, IMHO.
27.
by foca 15y ago
"We receive about 100 status updates per day". 5 years later, the average number of tweets per day is 140 MILLION. (According to http://blog.twitter.com/2011/03/numbers.html )
28.
by foca 16y ago
He didn't say libs were well documented. He said ruby libraries usually have the same or similar structure/coding style. The point is that it's oftentimes easier to grep the source for something than to track down said thing in google. SPE
29.
by foca 16y ago
I don't think this is necessary. The solution is to go to your project's mailing list, irc room, ask your twitter followers, or whatever, and ask for a new maintainer. Even messaging the users who actively report issues can be a good idea.
30.
by foca 16y ago
Yeah, but adding a whole organization for each open source repo? I have tons of small gems/libraries that solve one specific problem, and all enjoy their share of users/ I don't want to setup a bunch of organizations just because they might

More ›