Often we’ve written a script in our heads that may or may not be true. But this script can be limiting us from attaining our full potential. In this linked post (Is Your “Story” Holding You Back? Six Ways to Rewrite It—and Supercharge Your Power by Nancy D. O’Reilly, PsyD) we discover ways our stories are limiting our leadership potential and how to write new stories.Think of these stories as a complete glossary of all of the lessons we have learned from those who have led us in the past. It is unfortunate that most of these stories are based upon someone’s perceptions about us that may not always be true and upon our interpretation of those lessons that my not be accurate.Most of these stories are written from situations that did not go well or where mistakes were made. As leaders we have a responsibility to make certain the lessons we teach those who follow us are based upon truth and not a perception of what we think was the reason and motivation for the lesson. Then we need to be very careful and purposeful in how we communicate those lessons so they are interpreted correctly.So how do we do this?The formula is a 5-step process: continue reading » 5SHARESShareShareSharePrintMailGooglePinterestDiggRedditStumbleuponDeliciousBufferTumblr
You could make the case that the Raiders’ victory over the Los Angeles Chargers on Thursday was the team’s zenith since the return of head coach Jon Gruden.And yet, you could make the case that the Raiders were not the most inspirational team on the field that night. That distinction went to Hayward’s Tennyson High School football squad which uncorked a halftime show for the ages.1980 as a matter of fact. Those Raiders made history, being the first wild card team to win a Super Bowl.Frankly …
Top Reasons to Go With Managed WordPress Hosting Traditional servers require humans and hours–if not days–to launch; Software launches automatically and on demand in seconds or minutesTraditional servers are physically limited–companies have a finite number available to them; Software, as a virtual/information resource, has no such physical limitationTraditional servers are designed to serve many functions (often because of the above-mentioned physical limitations); Software is generally designed to serve a single functionTraditional servers are not designed to be discarded; Software is built around the idea that it runs ephemerally and can be terminated at any momentOn the cloud, these differences can disappear. The operative word is “can”–a look at the current mainstream discussions and advertisements of cloud services shows a distinct lack of interest in taking advantage of the crumbling wall between server and software.Many hosting services that provide “cloud servers” have IT support staff who have to allocate the servers. Others have pricing plans (e.g., large monthly minimums) that essentially force the cloud servers to have the same physical limitations as traditional servers. And finally, very few triumphal case studies for the cloud focus on how the ephemeral or single-function possibilities of cloud servers have led to better, cheaper, faster, more fault-tolerant, and more secure infrastructure designs.(Of note, when considering the above definition of the cloud, Google had the first cloud and the first cloud-enabled infrastructure with its essentially unlimited white-box, cheap servers and revolutionary MapReduce and BigTable technologies that enable ephemeral, single-function applications.)Why Servers are Better as SoftwareServers as software are better: cheaper, faster, more fault-tolerant, and more secure than traditional servers. Much of why servers as software are better goes to the two most commonly-named benefits of the cloud: the cloud is cheaper, and the cloud has virtually-unlimited resources (i.e., it’s easy to scale).The cloud is cheaper in theory because payment is per resource used, but may not be cheaper in practice–because you may be using resources inefficiently. For example, if you have a server that gets used heavily during weekdays, but rarely during the night or on weekends, then if you are paying for a cloud server to handle the heavy traffic 24/7, you’re not paying just for real usage; you’re paying for idle as well. On the other hand, if your server is software, it can relaunch with less resources at night and on weekends and with more resources on weekdays.The cost benefits increase beyond the above day/night example when one considers the single-function paradigm: if each server-as-software only exists to serve a single function, both the resources and the run-time allocated to that function can be limited to the bare essentials. Also, in a single-function server-as-software environment, resources can be scaled up to make the one function run faster without having to worry about having to keep those resources around for other functions.In case it is not wholly obvious, an architecture designed around ephemerality will be more fault-tolerant. Finally, single-function, ephemeral servers can be more secure than traditional servers because they are limited in their access to data and resources (being single-function) and they are built to disappear (being ephemeral).Photo by ManthyTaking Advantage of the Cloud Infrastructure: Database ServersSo how will the server-as-software nature of the cloud change infrastructure design? The biggest advantages should be realized in uses that write critical data (as opposed to read-only or temporary-data write uses), because those are the hardest to change and scale.Take, for example, the database server. In many ways, the place and design of a database server in system infrastructure is much the same as it was at the beginning of the personal computer revolution: a beefy machine that handles all data-related writing and retrieval, perhaps with a backup waiting in the wings. An Oracle database server circa 1995 in a LAN client/server architecture looks very similar to a cloud-hosted MySQL instance serving a web application frontend: humans are required to launch or fail over, physical resources are limiting (prohibitively expensive, humans required, and–in the cloud–slow I/O), and dependent clients require the database server to have 100% uptime.And perhaps the only software-like aspect that a database server might have–a single function–is usually untrue, as database servers often handle many different functions (e.g. authentication, storage and retrieval of user data, storage and retrieval of global data, exact record retrieval, full-text searching, and BI-like aggregation and number-crunching).However, by embracing the software-like aspects of the cloud, database servers can be redesigned, getting better, cheaper, faster, and more secure. One step in redesigning the database server can be to split out its various functions to different servers: a cache server for frequently-read items (e.g. Memcached), an OLAP database server for business intelligence (e.g. Mondrian with a local MySQL database), a full-text index database for text-based searches (e.g. Apache Solr), and different relational databases for other purposes (e.g. PostGIS for geospatial data and MySQL for typical structured transactional data).By breaking out these various functions, the infrastructure designer can allocate exactly the right amount of needed resources to each function, each function will be running on a platform designed to deliver optimal performance, and the security settings can admit only those authorized for the particular function into each server.However, the above functional breakout does not harness the cloud’s essentially-unlimited resources and ephemeral nature. To get the full cloud benefit, one must abandon all traditional databases and move to a database built for the cloud; something like HBase. HBase, based on Google’s BigTable, is probably the most well-known open source database that takes advantage of the unlimited and ephemeral nature of the cloud.Although the most dramatic cloud-driven infrastructure changes may be with respect to database servers, other types of servers may also benefit from the advantages of the cloud.HBase is meant to hold lots of data and be run across many servers in many data centers, and the underlying data can be replicated to clusters of other servers in many data centers with easily automated fail-over. HBase can dynamically scale up and scale down to more or less servers. In other words, if HBase’s single function can serve your database needs, then HBase takes advantage of all four of the server-as-software characteristics of the cloud.Taking Advantage of the Cloud Infrastructure: Other ServersAlthough the most dramatic cloud-driven infrastructure changes may be with respect to database servers, other types of servers may also benefit from the advantages of the cloud.For example, application servers on the cloud may not be as “single function” as they may appear on traditional servers.An application server might have both customer-facing and administrative functions, where the administrative functions (such as running complex reports or extracting and compressing massive amount of data for download) are both rarely used and a drain on resources for customers. In a properly-designed cloud architecture, the administrative functions could run on a separate, more powerful server that is launched on demand and terminated automatically after some period of idleness.An application server might also serve a website and an API, where web site traffic is more consistent, can be cached, and must return within a second, whereas the API results cannot be cached and must be able to handle huge influxes of requests. In a traditional server environment, these functions would likely be combined onto web application servers, but in the cloud they should be divided onto separate servers with different hardware profiles and auto-scaling plans.Servers used for internal data processing can also benefit from the advantages of the cloud. For example, restoring a large compressed database from online storage can be very taxing on server resources in the cloud; simply un-gzipping a few multi-gigabyte files can bring regular operations to halt. This is the perfect time to spin up a separate cloud server to handle the decompression and restoration tasks. Or, another internal example: database backups can also be resource-intensive and slow down database operations; instead, launch a replication slave, sync up the database, and then lock tables and back up from the slave.Final Thoughts on Cloud ArchitectureIn general, architectures that take advantage of the cloud should break down work into jobs that can be run separately on servers that are designed to terminate when not needed. This architectural move from traditional servers to the cloud may be seen as roughly analogous to the move from functional programming to event-driven programming in software design: react specifically to only what is needed, and do not design around waiting or idle time.If you can achieve this in your cloud-based architecture, then you will truly have a faster, cheaper, more fault tolerant, and more secure deployment. guest author 1 Related Posts Why Tech Companies Need Simpler Terms of Servic… Tags:#cloud#cloud computing A Web Developer’s New Best Friend is the AI Wai… More and more companies are moving from traditional servers to virtual servers in the cloud, and many new service-based deployments are starting in the cloud. However, despite the overwhelming popularity of the cloud here, deployments in the cloud look a lot like deployments on traditional servers. Companies are not changing their systems architecture to take advantage of some of the unique aspects of being in the cloud.The key difference between remotely-hosted, virtualized, on-demand-by-API servers (the definition of the “cloud” for this post) and any other hardware-based deployment (e.g., dedicated, co-located, or not-on-demand-by-API virtualized servers) is that servers are software on the cloud.Software applications traditionally differ from server environments in several key ways:Guest author Joe Masters Emison is VP of research and development at BuildFax, the only national provider of building, remodel, and repair records on homes and businesses. He designed BuildFax’s cloud infrastructure and Pragmatic Extract-Transform-and-Load (PETL) data-processing pipeline. 8 Best WordPress Hosting Solutions on the Market
Manoj Tiwary staked his claim for a spot in the Indian Test team with a determined knock of 93, helping India A recover from a wobbly start to reach 369 for nine on Day One of the three-day warm-up game against the touring England on Tuesday.Tiwary’s knock came after quick-fire half-centuries from opener Abhinav Mukund and comeback man Yuvraj Singh as India A skipper Suresh Raina elected to bat after winning the toss at the Brabourne Stadium.The Bengal captain faced 150 balls and hit 11 fours in his 202-minute knock, looking set for a deserving century before he got out trying to play across against England’s pacer Tim Bresnan. At stumps, R Vinay Kumar (25) and Parwinder Awana (11) were at the crease.Tiwary, who came in with India A struggling at 140 for four, pulled the innings together, putting on a century partnership with Irfan Pathan (46). The duo put on 110 for the seventh wicket in 168 balls to take the team past the 300-mark.Earlier, Mukund made 73 with 16 fours after living dangerously in the beginning while Yuvraj, dropped first ball by Samit Patel off Tim Bresnan, slammed four sixes and seven fours for his 80-ball 59 before both fell to England’s main spinner Graeme Swann on either side of lunch.In the battle for the no. 6 spot in the Indian Test batting line-up, Yuvraj definitely impressed more than Raina, who could manage only a tentative 20.Off-spinner Graeme Swann (centre) finished with 3 wickets for 90 runs.Click here to EnlargeThe home team lost Mukund, Murali Vijay (7) and Ajinkya Rahane (4) in their first session total of 113 and then surrendered the wickets of Raina (20), Yuvraj and Wridhiman Saha (20) in the second session.advertisementPathan was out leg before to Swann after tea while Bresnan got rid off Tiwary and Ashok Dinda off successive balls. He ended with figures of 3/59 in 20 overs, having earlier taken the wicket of Rahane, while Swann claimed 3/90 in 23 overs.England XI were handicapped by a right thigh injury to pacer Steven Finn while fielding, who limped off after just four overs and has been ruled out for the rest of the game.
DONE DEAL: Reading sign Chelsea midfielder Lewis Bakerby Paul Vegas10 months agoSend to a friendShare the loveReading have signed midfielder Lewis Baker on loan until the end of the season after Chelsea recalled him from his loan at Championship rivals Leeds.The 23-year-old agreed a season-long loan with Leeds in June but made just two league starts for the leaders.Baker, whose only Chelsea appearance was in 2014, has also had loan spells at Vitesse Arnhem and Middlesbrough.”Importantly, he knows what it takes to meet the demands of this division,” said Royals boss Jose Gomes.Baker is Reading’s second loan signing this month, following the arrival of Ovie Ejaria from Liverpool on Monday. TagsTransfersLoan MarketAbout the authorPaul VegasShare the loveHave your say