Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
solnic
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
solnic
11y ago
dry-validation supports typical validation behavior known from rails where errors are gathered and represented in a string representation. In fact it's much "smarter" than AR validations as it only executes validation functio
32.
▲
by
solnic
11y ago
You are right with everything you wrote except one thing: ship fast and the refactor is not only often extremely difficult and risky, there are cases where it becomes almost impossible. That's one of the reasons why I've been work
33.
▲
by
solnic
11y ago
Of course it is and I would never question that. The problem we're dealing with here is that you're using same type of objects for optimization purposes.
34.
▲
by
solnic
11y ago
It is silly when you look at it from the AR perspective, but if you look at it from a more general pov, it pretty much means that you have a single object that can be in many different states and what a given object really is, becomes amb
35.
▲
by
solnic
11y ago
That's gonna happen, as I mentioned they are both young libs. A shared dependency will be introduced very soon. I should've mentioned that in the post.
36.
▲
The Ruby Community: The Next Version
(hawkins.io)
10 points
by
solnic
11y ago
|
0 comments
37.
▲
My 2015 Programming Languages Tool Belt
(ku1ik.com)
5 points
by
solnic
12y ago
|
0 comments
38.
▲
Ruby Object Mapper 0.6.0 Released
(rom-rb.org)
3 points
by
solnic
12y ago
|
0 comments
39.
▲
Common Pitfalls Of Code Metrics
(solnic.eu)
2 points
by
solnic
13y ago
|
0 comments
40.
▲
Announcing Gitorious 3.0
(blog.gitorious.org)
5 points
by
solnic
13y ago
|
0 comments
41.
▲
by
solnic
14y ago
I think people miss the fact that I wrote about a code smell, which means a potential problem in your code. I don't say you shouldn't be using primitives. I say that there are cases where you should use rich, custom objects, that will simpl
42.
▲
by
solnic
14y ago
We needed a set-like data structure with enumerable interface that would also know how to handle attributes from parent classes. That's why a custom object worked better. oh and since it's an enumerable it's easy to work with it just like w
43.
▲
Using DataMapper and Rails with Legacy Schemas
(engineyard.com)
1 points
by
solnic
15y ago
|
0 comments