jamesgolick

10 ms·

31.
by jamesgolick 16y ago
So, I think my biggest problem with this app is the UI. The layout is okay, but there are lots of places where the spacing is really far off. Especially the enormous yellow bar on the front page. The type is way too big for the box, and the
32.
Most NoSQL DBs Are Not Scalable(jamesgolick.com)
8 points by jamesgolick 17y ago|2 comments
33.
by jamesgolick 17y ago
What's painful and embarrassing is when somebody who didn't actually read the article calls it "painful and embarrassing". > Patterns are still patterns whether you acknowledge them or not, and they are not defined by the LOC or numbe
34.
by jamesgolick 17y ago
I'm totally with you. The title was tongue in cheek.
35.
by jamesgolick 17y ago
In retrospect, logging was absolutely the wrong example for this article. I intend to follow up with a better example. In the case of logging, an observer may or may not be appropriate depending on the specifics of your application. In your
36.
A New Dynamic for Early Stage Product Development(enlightsolutions.com)
3 points by jamesgolick 17y ago|0 comments
37.
by jamesgolick 17y ago
Totally fair.
38.
by jamesgolick 17y ago
My data is from a real-world application. One that gets plenty of traffic. Friendly has served almost 50 million hits since we put it in to production two weeks ago. It actually happens to be quite a write-intensive workload. We have defini
39.
by jamesgolick 17y ago
It already works with Postgres. Just set :adapter => "postgres" when you call Friendly.configure.
40.
by jamesgolick 17y ago
Awesome. You guys rock!
41.
by jamesgolick 17y ago
Actually, we do run redis in production, and it has been awesome for us. But, for this particular aspect of our application, we see about 20GB of data growth per week. So, an all-in-RAM db isn't really practical. Either way, durability wasn
42.
by jamesgolick 18y ago
I probably wouldn't tell somebody to go practice typing either, but that's not because it isn't important. I would just take it for granted that they could already type.
43.
by jamesgolick 18y ago
Yes, I do know where the parentheses belong. Like I said earlier, it isn't hard to read ruby like this once you get used to reading ruby. > While any programmer who would write this deserves to be fired... That's exactly my point. The o
44.
by jamesgolick 18y ago
> That restriction tends to improve readability and reduce bugs at the cost of making it harder to have a truly transparent DSL. I used to think this too. But, then I actually learned ruby, and it turns out to be pretty easy to discern
45.
YC is a cult(danielharan.com)
116 points by jamesgolick 18y ago|154 comments
46.
Taking Style Tips from Natural Language(jamesgolick.com)
3 points by jamesgolick 19y ago|0 comments
47.
by jamesgolick 19y ago
Still, you can write your unit tests as you write your code. All a unit test does is verify that your code behaves the way you want it to. I think a lot of people here are confused about what exactly a unit test is. When you write a unit
48.
by jamesgolick 19y ago
I think the problem that you might be facing is more related to the quality of your tests than testing itself. If your tests are written correctly, you should never have to throw them away when you refactor. In fact, that's one of the maj
49.
by jamesgolick 19y ago
I want to be clear in saying that the argument I was putting forth in this article was that you're already investing the time in testing your code, whether you test it by eye, or by code. The question for you is - Would you rather spend y