Form Object is a very useful pattern in rails ecosystem as it can address variety of issues and antipatterns. In this article we will attempt to sort out in which situations Form Objects can prove useful and what conventions allow us to make most out of them.
Clients and Wrappers (also referred to as “Facades”) are remarkably useful tools for working with external services, libraries or APIs. While both Clients and Wrappers are primarily used to facilitate usage of before-mentioned libraries or APIs, there are some significant differences in responsibilities each of these patterns have. In some cases a Wrapper can take over a Client’s responsibilities too
At Selleo, we pride ourselves on our ability to help businesses become more efficient. Through our web and software solutions, we’ve worked with dozens of clients to create digital dashboards, SaaS platforms, and more that meet the needs of the companies we work with.
Pair programming is one of the best ways to learn programming, as collaborators can easily share their experiences and knowledge. This holds true when working with someone on similar or higher skill level, but can one really benefit from pairing with a novice developer?
Some people say that recruiting and hiring the right candidates takes time, energy and patience. In my opinion hiring process can be a great positive experience both for the candidates as well as for the company.
In part 1 we have covered antipatterns related to stubbing and problem with implementation details that are a overcomplicated just for the sake of being super easy to tests. In second part we are going to focus more on tests themselves.
When preparing our test suite we might be tempted to make some shortcuts that will render our tests less readable, comprehensible or will significantly decrease the flexibility of further implementation. Below, I try to list some of the most commonly seen techniques we should avoid to keep our test suite healthy.
It is hard to underestimate a value and importance of automated tests. Creating confidence about if the code works the right way and thus enabling safe refactoring is just one thing. Another one is that test suite can act as a way to document behavior and also, especially when approached the BDD way, can drive the code design and architecture.
Query Objects (also referred to as queries) is another pattern that helps in decomposing your fat ActiveRecord models and keeping your code both slim and readable. While this article is written with Ruby On Rails in mind, it easily applies to other frameworks, especially MVC based and applying ActiveRecord pattern.
The goal of the research project we undertook was to find a robust web-based SR tool which could – among other things – support medical vocabulary and which could be speaker independent.
