blog.sriramnarayan.com
XPloring around: Open Source authors' struggle for compensation
http://blog.sriramnarayan.com/2010/01/open-source-authors-struggle-for.html
Sriram Narayan's blog on IT. Open Source authors' struggle for compensation. It is the freemium business model - Give away the basic software and charge for enhanced functionality or support. It is not enforceable - Users will simply build the software from the source code and there is no way you can get them to pay. Monday, January 25, 2010. On your comment about the category where an open source project will be adopted by Eclipse, Apache or Mozilla still falls into two categories:. 1 Its a big. The var...
blog.sriramnarayan.com
XPloring around: Fail fast
http://blog.sriramnarayan.com/2010/02/fail-fast.html
Sriram Narayan's blog on IT. When failure is a possibility, design to fail fast rather than slowly. Doing so reduces the cost/impact of failure. What is equally important, failing fast makes further attempts feasible. Learning from previous failures makes future attempts more likely to succeed. This principle is widely applicable in software development:. Methodologies that have fail fast mechanisms baked in are more likely to generate greater ROI. More on this later. Verification: When and How? Okay, so...
blog.sriramnarayan.com
XPloring around: The economics of aesthetics
http://blog.sriramnarayan.com/2012/07/the-economics-of-aesthetics.html
Sriram Narayan's blog on IT. The economics of aesthetics. Many will argue that it is just plain wrong to subject aesthetics to cost and benefit, at least until a certain threshold. Someone said, “An economist is someone who knows the price of everything and the value of nothing.”. What about the people who write code? They also have a sense of aesthetics. Their bosses don’t grudge them the inexpensive effects – standard tools that can ensure uniform indentation, nice fonts and syntax high...To this claim...
blog.sriramnarayan.com
XPloring around: How email shapes us... and how to get back into shape
http://blog.sriramnarayan.com/2012/04/how-email-shapes-us.html
Sriram Narayan's blog on IT. How email shapes us. and how to get back into shape. Email has altered the balance of communication and actual work. It was McLuhan who observed that technology shapes us even as we shape it. How has email shaped us? The inbox is the file cabinet. By the truckload, by the minute. Because it is so cheap, we send and get loads of it. Never mind spam, why have corporate notice boards disappeared? Of luddites and of having access to the latest information. To me, this sounds like...
blog.sriramnarayan.com
XPloring around: Pair Programming Payoff
http://blog.sriramnarayan.com/2010/03/pair-programming-payoff.html
Sriram Narayan's blog on IT. For a project that runs for, say six months or more, there should no extra development cost on account of pair programming. Period. If there is extra cost, it means pairing is not paying off for you. Pairing should pay off in the following difficult-to-measure ways:. Lesser rework during development on account of misunderstood/ill-defined requirements. These things surface quickly when pairs talk to each other. Faster/better process of bringing new team members up to speed.
blog.sriramnarayan.com
XPloring around: How to do XYZ in Agile?
http://blog.sriramnarayan.com/2010/03/how-to-do-xyz-in-agile.html
Sriram Narayan's blog on IT. How to do XYZ in Agile? Clients sometimes ask, "How do you do estimation in Agile? Or, in general "How do you do XYZ in Agile? Continuous delivery of valuable functionality. Happy team (team includes client). The agile manifesto starts off by saying:. We are uncovering better ways of developing. Software by doing it. And helping others do it. I was speechless. Turned out that the organization still retained the services of a group called SEPG (software engineering process...
cd-with-thoughtworks-go.blogspot.com
Continuous Delivery with ThoughtWorks Go: Use infrastructure automation tools for application deployment
http://cd-with-thoughtworks-go.blogspot.com/2013/10/use-infrastructure-automation-tools-for.html
Continuous Delivery with ThoughtWorks Go. Use infrastructure automation tools for application deployment. Http:/ www.thoughtworks.com/insights/blog/use-infrastructure-automation-tools-application-deployment. Tuesday, October 08, 2013. Subscribe to: Post Comments (Atom). What Go users say. The power of pipeline templates and parameters. Modeling higher order workflows with Go. Traceability with upstream pipeline labeling. Does Go support my favorite build/deployment tool? Users write/talk about Go.
cd-with-thoughtworks-go.blogspot.com
Continuous Delivery with ThoughtWorks Go: Modeling build promotions into Go
http://cd-with-thoughtworks-go.blogspot.com/2013/10/modeling-build-promotions-into-go.html
Continuous Delivery with ThoughtWorks Go. Modeling build promotions into Go. Http:/ www.thoughtworks.com/insights/blog/build-promotion-go. Wednesday, October 16, 2013. Subscribe to: Post Comments (Atom). What Go users say. The power of pipeline templates and parameters. Modeling higher order workflows with Go. Traceability with upstream pipeline labeling. Does Go support my favorite build/deployment tool? Why continuous delivery needs devops, and why devops needs infrastructure-as-code. One task per job.
SOCIAL ENGAGEMENT