andrzejkrzywda

11 ms·

61.
Implementing worker threads in Rails(blog.arkency.com)
2 points by andrzejkrzywda 13y ago|0 comments
62.
Typical Rails bugs(andrzejonsoftware.blogspot.com)
3 points by andrzejkrzywda 13y ago|0 comments
63.
by andrzejkrzywda 13y ago
"Those private topic bugs are not the result of ActiveRecord. We added a group layer on top of existing code and missed some places where queries did not respect it." I've seen so many of such bugs in other apps, that I treat
64.
by andrzejkrzywda 13y ago
Choosing a heavier framework may put you in risk of 'typical', framework-related bugs that often appear. The bugs are not part of the framework, but they are part of the patterns around it. Discourse 'private topics' lea
65.
How to track ActiveRecord model statistics(blog.arkency.com)
2 points by andrzejkrzywda 13y ago|0 comments
66.
Post- Mortem of a Website Project(bluefishdesignstudio.com)
2 points by andrzejkrzywda 13y ago|0 comments
67.
Ruby: #new vs #initialize(blog.arkency.com)
2 points by andrzejkrzywda 13y ago|0 comments
68.
Single Page Applications fight - video and a transcript(andrzejonsoftware.blogspot.com)
4 points by andrzejkrzywda 13y ago|0 comments
69.
Case Study: How to sell a complex product without building a prototype(pietruszynski.blogspot.com)
2 points by andrzejkrzywda 13y ago|0 comments
70.
What HN and Reddit think about startups(blog.123ship.it)
3 points by andrzejkrzywda 14y ago|0 comments
71.
Potential security problem with the HipChat Mac app(twitter.com)
1 points by andrzejkrzywda 14y ago|0 comments
72.
by andrzejkrzywda 14y ago
Think of the router as the "main" method of your application. It's passing you the initial arguments. You just parse it and run the correct logic and/or display the view that is required.
73.
by andrzejkrzywda 14y ago
We all expect to find a Rails/Django equivalent for JavaScript apps. There's nothing like that. All of the JavaScript frameworks are in their infancy. It doesn't mean we can't use them yet. It's just that they are not mature enough to be ea
74.
What customers say the want is not what they really want(blog.123ship.it)
4 points by andrzejkrzywda 14y ago|0 comments
75.
by andrzejkrzywda 14y ago
Sounds interesting. I'd be interested to see some screenshots of how you approached the problem.
76.
by andrzejkrzywda 14y ago
All the code review tools focus on commits, which is probably the most common use case. Is anyone aware of tools that let me do the code reviews of the whole code base in a simple way? I don't want to focus on the commits/pull-requests in t
77.
How to improve your product?(blog.123ship.it)
17 points by andrzejkrzywda 14y ago|2 comments
78.
by andrzejkrzywda 14y ago
This presentation reminded me of this: Sometimes it's better to hire a younger, less experienced developer, who's not aware yet, that "specialisation is good". Thanks to that you can have one dev who's able to finish the whole project. Obvi
79.
Developers, learn to design(slideshare.net)
15 points by andrzejkrzywda 14y ago|29 comments
80.
Why do projects take so long?(andrzejonsoftware.blogspot.com)
4 points by andrzejkrzywda 14y ago|0 comments
81.
Angular or Ember? Congratulations, you've already won.(andrzejonsoftware.blogspot.com)
6 points by andrzejkrzywda 14y ago|0 comments
82.
by andrzejkrzywda 14y ago
You are right that there is a danger in the fact that the object being passed into the AOP advices can be changed. Usually, I'm avoiding this kind of situations. It can be terrible to debug. In our teams, we have a rule that the calls to Be
83.
by andrzejkrzywda 14y ago
In runtime, this is exactly the result. As code modules, those two things are separated. The usecase doesn't need to know about the gui and vice versa. In theory, they can even be reusable. We combine those two things in the glue code. Than
84.
by andrzejkrzywda 14y ago
We were struggling with this problem for months. What would you suggest to bundle into this library?
85.
by andrzejkrzywda 14y ago
We're going to include pure JavaScript examples. I understand the confusion that comes with the fact that most examples are CoffeeScript. There's nothing that makes this approach impossible to use with JS. The code samples are Coffee, becau
86.
by andrzejkrzywda 14y ago
Thanks for the link. I wasn't aware of this discussion. Yes, it seems that hexagonal.js uses the third approach - a metadata file.
87.
Non-framework approach to JavaScript apps - hexagonal.js(andrzejonsoftware.blogspot.com)
30 points by andrzejkrzywda 14y ago|21 comments
88.
by andrzejkrzywda 14y ago
This. I'm one of the people behind hexagonal.js. Raganwald's work enabled us to implement one of the main components - the glue code.
89.
Frontend first(andrzejonsoftware.blogspot.com)
3 points by andrzejkrzywda 14y ago|0 comments
90.
by andrzejkrzywda 14y ago
> 3. Yes we render a lightweight version of the pages in a <noscript> tag for google indexing. Can you explain it in more detail? Are you returning different results to Google bots?

More ›