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.
Today I’m breaking from my typical routine of writing about digital marketing and strategy trends to talk a bit about a big personal milestone. It is with much excitement that I share the news of some big changes for me and my family: I have left ThoughtWorks to head for new pastures. My next career challenge: I am joining TrackMaven… Continue reading Pastures New →
As far back as the 19th century, industrial firms pursued vertical integration strategies. The thinking was that by owning the supply chain from raw materials to retail outlets, a firm had direct control over its entire cost structure, making it better able to squeeze efficiencies out of it and being less susceptible to supply shocks. This was important because, for large industrial firms, competing on price was the primary strategy for winning market share.
During the 1950's and 60's, companies also pursued conglomerate strategies: bringing seemingly unrelated businesses under one roof, sometimes seeking synergies (as Sears did owning a retail…
The future of podcasting is looking bright. I think it might be the next major wave of personal publishing. It could become the darling of advertisers who will see it as a way to reach legions of new buyers. I’m going to explain how we got here, and what you can do to ride that wave with… Continue reading The Future of Podcasting Is You →
Feature Toggles seem to beget rather messy Toggle Point code, and these Toggle Points also have a tendency to proliferate throughout a codebase. It's important to keep this tendency in check for any Feature Toggles in your codebase, and critically important if the toggle will be long-lived. In this installment, Pete covers a few implementation patterns and practices which help to reduce this issue.
Modern web development has many challenges. Of course, you need to write code that fulfills customer functional requirements. It needs to be fast. Further you are expected to write this code to be comprehensible and extensible.
Somewhere, way down at the bottom of the list of requirements, behind, fast cheap, and flexible is “secure”. That is, until something goes wrong, until the system you build is compromised, then suddenly security is, and always was, the most important thing.
Specialized techniques, such as threat analysis, are increasingly recognized as essential to any serious development. But Cade Cairns and Daniel Somerfield explore…