Day: February 1, 2018

Hogan Assessments announced Jan. 29 that Scott Gregory will assume the role of CEO effective March 1. Gregory succeeds current CEO Tomas Chamorro-Premuzic, who has resigned and will leave the company Feb. 28.

“Scott is uniquely positioned to become Hogan’s next CEO,” said Robert Hogan, the company’s founder and president. “He has a thorough understanding of every type of client organization Hogan serves, deep knowledge of our assessments and research dating back to his work with us during Hogan’s early years.”

Gregory, who completed his Ph.D. under Robert and Joyce Hogan at The University of Tulsa, was one of Hogan’s first employees and has served in various capacities with the company, including his current role as partner and vice president of consulting, leading Hogan’s domestic and international consulting teams. From 2013-16, he was Hogan’s general manager, Twin Cities. Prior to that, he served as vice president of talent management and organizational development at Pentair. He also was a consultant for Personnel Decisions International and Hogan’s partner, MDA Leadership Consulting.

Throughout his career, Gregory has consulted for half of the Fortune 100 and worked with personality assessment in North and South America, Australia, Asia and Europe.

Tags: CEO, consulting, Fortune 100, Hogan Assessments, Personality assessment, Scott Gregory, Tomas Chamorro-Premuzic https://goo.gl/qaie6F #HR #WorkForce #CLO

ICYMI: The concept of API management has been around for a decade now and is something that is now part of the fabric of the cloud with services like AWS API Gateway. API management is about requiring all consumers of any API resource to sign up for any API access, obtain a set of keys that identify who they are, and pass these keys in with each API call they make from any application. Since every API call is logged, and every API call possesses these keys, it opens up the ability to understand exactly how your APIs are being used through reporting and analytics packages which come with all modern API management available today. This is the fundamentals of API management, allowing us to understand who is accessing our digital resources, and how they are putting them to use–in real time.

The security of API management comes in with this balance of opening up access, being aware of who is accessing what, and being able to throttle or shut down the access of bad actors–more than ever it is about authentication and requiring keys for all API calls. If you want access to any digital resources from a company, organization, institution, or government agency in a machine-readable format, for use in any other web, mobile, or device application–you use the API. This allows ALL digital assets to be made available internally, to trusted partners, and even to the public, while still maintaining control over who has access to what, and what types of applications they are able to use them in. APIs introduce more control over our digital resources, not less–which is a persistent myth when it comes to web APIs. https://goo.gl/hQ1byC #DataIntegration #ML

Apache Camel empowers you to define routing and mediation rules in a variety of domain-specific languages, including a Java-based Fluent API, Spring or BlueprintXML Configuration files, and a Scala DSL. Apache Camel uses URIs to work directly with any kind of Transport or messaging model such as HTTP, ActiveMQ, JMS, JBI, SCA, MINA or CXF, as well as pluggable Components and Data Format options. Apache Camel is a small library with minimal dependencies for easy embedding in any Java application.

Completion for Apache Camel URI in Eclipse XML Editor

Thanks to this new community project aiming at providing an Apache Camel Language Server Protocol, Eclipse XML Editor is proposing completion for Apache Camel URIs. https://goo.gl/JfqtDC #DataIntegration #ML