Homo dating net
But then I left Scribd, stopped being a user of Db Charmer and the situation drastically changed.For quite some time (years) I would keep fighting to make the code work with newer and newer versions of Rails, struggling to wrap my head around more and more (sometimes useless) abstractions Rails Core team decided to throw into Active Record.That is exactly what happened to Swiftype at the beginning of 2017.While preparing for a public release of our latest product (Swiftype Enterprise Search), we understood that it was going to involve a lot of confidential information and we would need to be able to assure our customers of our capabilities to protect their data.Software development has seen great benefit come from the adoption of automated testing frameworks and methodologies, however, the culture of automated testing has neglected one key area of modern web application serving stack: web application edge routing and multiplexing rulesets.
And when it came to compliance for startups, it was nearly synonymous with PCI/DSS — mandatory certification used by the credit card industry.
Unfortunately, the application logic configured within web servers is often much harder to test than that hosted directly in application code, and thus too often software teams resort to manual testing, or worse, customers as testers, by shipping their changes to production without edge routing testing having been performed.
In this post, I would like to explain the approach Swiftype has taken to ensure that our test suites account for our use of complex edge web server logic to manage our production traffic flow, and thus that we can confidently deploy changes to our application infrastructure with little or no risk.
In addition to the marketing aspect, there was a security angle to the problem as well: we were looking for a standard framework that could be used by our small team to ensure the safety of customer data, guiding us through the process.
Based on those considerations, we decided to go through a formal SOC 2 certification.
Finally, in the last 2 years (while trying to make Db Charmer compatible with Rails 4.0) it has become more and more apparent, that I simply do not want to do this anymore.