Test automation framework architecture efforts are often complete failures. In this article, I will tell you how to make yours successful.

Camilo Rivera‘s insight:

A test automation framework is what you end up with if you want to improve the quality of your testing. However, sometimes these frameworks become so complex that you just usually give up on them and continue working as usual: create tests and the forget about them.

Creating such a framework requires long hours of thinking about how to achieve balance between complexity and maintenance of your tests. Do I include a layer of abstraction here? Do I make this test more granular? Less granular? A good test automation framework will help you deal with these situations by relieving you from such decisions and make you think in business terms.

Please this read this article knowing that everything the author says is true, while at the same time being aware of the amount of work required to get to this point.

All these tips should be applied to all SQL-based projects/applications in a mandatory fashion. This is not the case in the real world, though. I particularly liked the one about trying to get rid of OUTER JOINS.

Hack is a programming language created by Facebook. It is statically typed and works on top of PHP, maintaining compatibility with it. A local server watches the filesystem and does type checking while the developer is coding. Some features unavailable to PHP are included with this language such as generics, collections, and lambdas. Most of the application front-end is currently developed in Hack.

Go’s Familiar Syntax Due to their shared heritage in the C programming language, Go (aka Golang) code should be fairly recognizable to a Java developer. Here is the canonical “Hello world” program, which you can execute and modify through your browser on the Go Playground site: package main import “fmt” func main() { fmt.Println(“Hello world”) } Functions and control structures begin and end with curly-braces. Function parameters are enclosed in parentheses, with empty parentheses for functions having zero parameters. Strictly speaking, Go statements terminate with semicolons just as in Java, although the convention is to let the compiler insert them implicitly. The naming convention for variables and functions is “camelCase”, rather than using underscores (Python people tend to hate this!). Other Go fundamentals closely mirror their Java counterparts, too. Go code is grouped into “packages”. A function main(), located in the package main, is th

A forecast just released by eMarketer argues that Google will lose $1.4 billion in PC search revenue in 2014 as paid clicks partly migrate to mobile devices, where revenue per click has been lower. Some of that PC revenue decline will be offset by growth in mobile paid clicks.

Camilo Rivera‘s insight:

Evolution = Adaptation. Current social media giants are struggling to keep up with new challenges, mobile amid one of them. Google wasn’t able to define a consistent social strategy with Google+ falling into oblivion. Time will tell if they get it right in the mobile space.