541 karma · joined September 23, 2012
[1]: https://about.gitlab.com/2017/02/10/postmortem-of-database-o...
[1] - https://blogs.oracle.com/developers/cloud-foundry-arrives-on...
Finding the problem and creating a solution along with focusing on the process of creating that solution in order to reduce risk of building the wrong solution. Contrasted to building a solution along with a sane dev and production environment for that solution to fit in, to increase possible iteration velocity by reducing deployment inertia.
What we do: We make some of the best Application Delivery Control technology in the world that is easily deployable, in real time; anywhere, anytime and on any platform.
Who we are: KEMP Technologies is one of the fastest growing ADC vendors in the world with over 26,000 customers (including NASA, Apple, EA, Fender, Dyson, SONY & NYPD) and offices in New York, Long Island, Santa Clara, Limerick, Hannover and Singapore. KEMP was ranked #1 ADC vendor by growth in 2013 and #3 ADC vendor by units shipped worldwide in 2013. KEMP Technologies has been named in Crain's 2014 New York Business Fast 50, Inc. 2014 Fast 5000 and Deloitte 2014 Technology Fast 500 and is a disruptive and innovative force in the ADC space globally. http://life.kemptechnologies.com/
If you'd like to learn more: drosen at kemptechnologies dot com
The fact that this project got refunded is also a tell that Google finds value in Voice (maybe). The question I'd ask is what value is it that they see? A couple of thoughts:
* Move voice users out of Hangouts to reduce users of the monolith.
* Test the current user bases' interest in updates - maybe there's something bigger brewing and this update is an experiment to learn about user habits.
* Create a pipeline program to covert users to Fi.
* Release work done over the holiday vacation that was cheap enough / good enough to release.
What we do: We make some of the best Application Delivery Control technology in the world that is easily deployable, in real time; anywhere, anytime and on any platform.
Who we are: KEMP Technologies is one of the fastest growing ADC vendors in the world with over 26,000 customers (including NASA, Apple, EA, Fender, Dyson, SONY & NYPD) and offices in New York, Long Island, Santa Clara, Limerick, Hannover and Singapore. KEMP was ranked #1 ADC vendor by growth in 2013 and #3 ADC vendor by units shipped worldwide in 2013. KEMP Technologies has been named in Crain's 2014 New York Business Fast 50, Inc. 2014 Fast 5000 and Deloitte 2014 Technology Fast 500 and is a disruptive and innovative force in the ADC space globally.
If you'd like to learn more: drosen at kemptechnologies dot com
What we do: We make some of the best Application Delivery Control technology in the world that is easily deployable, in real time; anywhere, anytime and on any platform.
Who we are: KEMP Technologies is one of the fastest growing ADC vendors in the world with over 26,000 customers (including NASA, Apple, EA, Fender, Dyson, SONY & NYPD) and offices in New York, Long Island, Santa Clara, Limerick, Hannover and Singapore. KEMP was ranked #1 ADC vendor by growth in 2013 and #3 ADC vendor by units shipped worldwide in 2013. KEMP Technologies has been named in Crain's 2014 New York Business Fast 50, Inc. 2014 Fast 5000 and Deloitte 2014 Technology Fast 500 and is a disruptive and innovative force in the ADC space globally.
If you'd like to learn more: drosen at kemptechnologies dot com
Things that we've done so far with Concourse:
* A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel
* A job, that based on the completion of a build will upload the resulting artifact to Github and tag the release with a new version, auto generated release notes and checksums
* Travis.ci style github pull request analysis
* A security feed monitor that notifies us when a part of our application is vulnerable and when it is, kicks off a build and sends an email notification
* Automatically updates submodules and gems for git repos and runs specs and tests against the updated artifact.
These tasks were not difficult to implement. Every pipeline for Concourse is explicitly defined in its configuration file [2], which we version control. There is never any reconfiguring or rebuilding "snowflake" servers when we re-deploy our Concourse VMs. They rebuild identically based on the config files.
[1] - http://buildpacks-ci.cfapps.io (Chrome friendly, Firefox not)
In the end, all it would take to get me fully on board is a native XMBC plugin.