So using the .source_location you will be able to figure which file it has been declared.
Lots of our people have lots of opinions. Here are just a few of them
ThoughtWorks embraces the individuality of the people in the organization and hence the opinions expressed in the blogs may contradict each other and also may not represent the opinions of ThoughtWorks.
I’m trying to model the world of centralized, decentralized, and an in-between place that I think (among other solutions), Git as a store and GitHub (as a platform, but imperfectly) fit as a solution.
I have a diagram of that model, that shows Bitcoin and a property ownership database are on a centralized/decentralized spectrum:
Full decentralized. You don’t need anyone’s permission to buy or sell Bitcoin (even though your nation-state may try to legislate it). You also don’t need anyone’s permission to mount something like an exchange, though you’ll need to gain the trust of a community to get…
Cross-Site Forgery Protection (also known as CSRF Protection) is a built-in feature in Rails.
I previously wrote something on juggling scope, schedule, resources and quality: The iron triangle is actually a square and not particularly iron. I learned in ThoughtWorks that you ask the client to find some other vendor when they suggest that quality is the thing that should be limited (in order to meet dates+scope+cost). And that faced with any other permutation the only win-win scenario is to constrain all but scope.
If you attempt to constrain all four, you get salespeople running interference on messaging, and stand to lose in multiple other ways. Invariably change requests…
It is possible to do database migrations without incurring any downtime as long as we follow certain patterns. For example, instead of renaming a column (which is not backwards-compatible with currently running web servers) in one step, you would so in 3 steps:
A very useful tool in this context is the Strong Migrations gem. This gem will detect potentially unsafe migrations and prevent…