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.
Blog post by Bonna Choi
23 May 2013
The idea of “Failure Demand” comes from systems thinker, John Seddon, who describes it as “unnecessary burden on the system.” By looking at removing failure demand on a system, you free up more capacity to focus on value added work. Much of failure demand also maps to the lead concept of “waste” although not all “waste” is the same as failure demand.
Some classic examples (and tell-tale signs) I see with companies include:
Blog post by Patrick Kua
23 May 2013
We were trying to template google analytics and make it part of our requirejs setup. When we did what we thought was obvious to wrap it in a module and declare a dependency on it, it seemed to fail quite miserably.
The trick was that we missed that you needed to export a global variable. This means in the javascript file initialising google analytics we had to add the following code block
var registerGoogleAnalytics = function(accountId) {
var _gaq = _gaq || [];
if (window) {
window._gaq = _gaq; // export as global
}
_gaq.push(['_setAccount', accountId]);
_gaq.push(['_trackPageview']);
…Blog post by Patrick Kua
23 May 2013
Out of many roles on an Agile team - developer, tester, project manager or product manager, the role of the business analyst is probably the one whose “existence” on the team is most frequently challenged. The role of a BA is often questioned, not the quality of work, but the “perceived” value delivered for the team - by clients. Frankly I’ve had a few identity crisis since I started working as an analyst on agile teams in 2006.
Blog post by ThoughtWorks Studios
23 May 2013
You can read the title as “How to make your recently created android app’s file visible”.
I am recetly playing around with Android Platform and around goods and bads this is just annoying. Android has an complex user mode mecanism to segregate application namespace. It is based on linux user mode and each application has its own, well, user. It is OK and brings up a good security policy but has some trade offs as well.
Going specific to what I want to say about files: You do have many ways to write a file with…
Blog post by Filipe Gomes Esperandio
22 May 2013
So, in the context of this retrospective, please share with us what you consider: positive (Plus), negative (Minus), or Interesting. Please write each note on a post-it, and place them on the respective canvas area.
Blog post by Paulo Caroli- Agileretroactivities
22 May 2013
The ThoughtWorks Technology Advisory Board (TAB) has released the latest edition of our technology radar. This is where we highlight some of the technologies that are currently attracting our attention and that we feel are worth you taking a look at. In this edition our themes include my long term interest in breaking down boundaries between people and groups, lightweight option for analytics, infrastructure as code, and applying the practices that have worked well for us in development to places that are missing them.
Blog post by Martin Fowler
22 May 2013
Blog post by Lindsay Ratcliffe
22 May 2013
Blog post by Sriram Narayan - Go
22 May 2013
One our frustrations using jade and icanhaz (a javascript front end mustache implementation) was that when we were trying things that were obvious to us, jade would simply fail to template and we weren’t sure what was causing it.
Fortunately small TDD cycles and experimentation made us realise that it was the combination of new line characters and mustache code made jade work/break.
We would try something like this:
script(type="text/html", id="my_checkbox", class="partial")
li
label(for="{{code}}")
{{name}}
input(id="{{code}}", checked="checked", name="{{code}}", type="checkbox")
The set of statements above would be valid mustache (once converted to HTML) but jade…
Blog post by Patrick Kua
22 May 2013
We are a software company and a community of passionate, purpose-led individuals. We think disruptively to deliver technology to address our clients' toughest challenges, all while seeking to revolutionize the IT industry and create positive social change.
Sign up for our perspectives newsletter