http://www.brighttag.com/2012/03/01/a-code-to-code-by/ Technology solution to make online data instantly useful in any web or mobile application Mon, 25 Feb 2013 21:52:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.brighttag.com/2012/03/01/a-code-to-code-by/#comment-92 Automating Cloud Applications using Open Source at BrightTag | DevOps.com Mon, 01 Oct 2012 00:20:59 +0000 http://www.brighttag.com/?p=896#comment-92 [...] from the outset and maintaining an obsessive focus on performance and code quality (read our full Code to Code By for more on this [...] [...] from the outset and maintaining an obsessive focus on performance and code quality (read our full Code to Code By for more on this [...]

]]> http://www.brighttag.com/2012/03/01/a-code-to-code-by/#comment-81 Out and About: This Week @BrightTag | BrightTag Tue, 11 Sep 2012 16:53:15 +0000 http://www.brighttag.com/?p=896#comment-81 [...] source is part of our Code to Code By here at BrightTag and those of you attending Cloud Connect in Chicago can learn about how we put [...] [...] source is part of our Code to Code By here at BrightTag and those of you attending Cloud Connect in Chicago can learn about how we put [...]

]]> http://www.brighttag.com/2012/03/01/a-code-to-code-by/#comment-79 Shark Week at BrightTag, Faster Site Performance, Open Source Fri, 31 Aug 2012 17:31:57 +0000 http://www.brighttag.com/?p=896#comment-79 [...] to our Code to Code by, we focused on scalability and leveraged open-source tools to aid our pursuit for velocity and [...] [...] to our Code to Code by, we focused on scalability and leveraged open-source tools to aid our pursuit for velocity and [...]

]]> http://www.brighttag.com/2012/03/01/a-code-to-code-by/#comment-65 Data Loss Prevention, Through the Cloud | BrightTag Wed, 22 Aug 2012 03:34:32 +0000 http://www.brighttag.com/?p=896#comment-65 [...] of the core tenants of our development philosophy is that any network i/o call can, and will, fail. Rather than point fingers about whose at fault, [...] [...] of the core tenants of our development philosophy is that any network i/o call can, and will, fail. Rather than point fingers about whose at fault, [...]

]]>