TOXIC LEADERSHIP & Building Worker Resilience by Gary L
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Reversible Programming with Negative and Fractional Types
9 A Computational Interpretation of Compact Closed Categories: Reversible Programming with Negative and Fractional Types CHAO-HONG CHEN, Indiana University, USA AMR SABRY, Indiana University, USA Compact closed categories include objects representing higher-order functions and are well-established as models of linear logic, concurrency, and quantum computing. We show that it is possible to construct such compact closed categories for conventional sum and product types by defining a dual to sum types, a negative type, and a dual to product types, a fractional type. Inspired by the categorical semantics, we define a sound operational semantics for negative and fractional types in which a negative type represents a computational effect that “reverses execution flow” and a fractional type represents a computational effect that“garbage collects” particular values or throws exceptions. Specifically, we extend a first-order reversible language of type isomorphisms with negative and fractional types, specify an operational semantics for each extension, and prove that each extension forms a compact closed category. We furthermore show that both operational semantics can be merged using the standard combination of backtracking and exceptions resulting in a smooth interoperability of negative and fractional types. We illustrate the expressiveness of this combination by writing a reversible SAT solver that uses back- tracking search along freshly allocated and de-allocated locations. The operational semantics, most of its meta-theoretic properties, and all examples are formalized in a supplementary Agda package. CCS Concepts: • Theory of computation → Type theory; Abstract machines; Operational semantics. Additional Key Words and Phrases: Abstract Machines, Duality of Computation, Higher-Order Reversible Programming, Termination Proofs, Type Isomorphisms ACM Reference Format: Chao-Hong Chen and Amr Sabry. -
Toxic Leadership and Voluntary Employee Turnover: a Critical Incident Study
Toxic Leadership and Voluntary Employee Turnover: A Critical Incident Study By Richard P. March III B.A. in German, May 2002, Franklin & Marshall College M.A. in German and Second Language Acquisition, May, 2005, Georgetown University A Dissertation Submitted to The Faculty of The Graduate School of Education and Human Development of The George Washington University in partial fulfillment of the requirements for the degree of Doctor of Education May 17, 2015 Dissertation Directed by Neal Chalofsky Associate Professor of Human and Organizational Learning The Graduate School of Education and Human Development of The George Washington University certifies that Richard P. March III has passed the Final Examination for the degree of Doctor of Education as of February 24, 2015. This is the final and approved form of the dissertation. Toxic Leadership and Voluntary Employee Turnover: A Critical Incident Study Richard P. March III Dissertation Research Committee Neal Chalofsky, Associate Professor of Human and Organizational Learning, Dissertation Director Maria Cseh, Associate Professor of Human and Organizational Learning, Committee Member Thomas Reio, Professor of Adult Education and Human Resource Development, Florida International University, Committee Member ii © Copyright 2015 by Richard P. March III. All rights reserved. iii Abstract of Dissertation Toxic Leadership and Voluntary Employee Turnover: A Critical Incident Study Contributing to the burgeoning corpus of literature examining the deleterious impacts of toxic leadership upon employees and organizations, the present study utilizes 15 study participants’ reported critical incidents of toxic leader targeting to conceptualize and to narrate the relationship between toxic targeting and voluntary employee turnover. The study found evidence to support a direct link between toxic targeting and voluntary employee turnover and reports the categories of leader characteristics study participants’ identified as toxic. -
Let's Get Functional
5 LET’S GET FUNCTIONAL I’ve mentioned several times that F# is a functional language, but as you’ve learned from previous chapters you can build rich applications in F# without using any functional techniques. Does that mean that F# isn’t really a functional language? No. F# is a general-purpose, multi paradigm language that allows you to program in the style most suited to your task. It is considered a functional-first lan- guage, meaning that its constructs encourage a functional style. In other words, when developing in F# you should favor functional approaches whenever possible and switch to other styles as appropriate. In this chapter, we’ll see what functional programming really is and how functions in F# differ from those in other languages. Once we’ve estab- lished that foundation, we’ll explore several data types commonly used with functional programming and take a brief side trip into lazy evaluation. The Book of F# © 2014 by Dave Fancher What Is Functional Programming? Functional programming takes a fundamentally different approach toward developing software than object-oriented programming. While object-oriented programming is primarily concerned with managing an ever-changing system state, functional programming emphasizes immutability and the application of deterministic functions. This difference drastically changes the way you build software, because in object-oriented programming you’re mostly concerned with defining classes (or structs), whereas in functional programming your focus is on defining functions with particular emphasis on their input and output. F# is an impure functional language where data is immutable by default, though you can still define mutable data or cause other side effects in your functions. -
Notes on Functional Programming with Haskell
Notes on Functional Programming with Haskell H. Conrad Cunningham [email protected] Multiparadigm Software Architecture Group Department of Computer and Information Science University of Mississippi 201 Weir Hall University, Mississippi 38677 USA Fall Semester 2014 Copyright c 1994, 1995, 1997, 2003, 2007, 2010, 2014 by H. Conrad Cunningham Permission to copy and use this document for educational or research purposes of a non-commercial nature is hereby granted provided that this copyright notice is retained on all copies. All other rights are reserved by the author. H. Conrad Cunningham, D.Sc. Professor and Chair Department of Computer and Information Science University of Mississippi 201 Weir Hall University, Mississippi 38677 USA [email protected] PREFACE TO 1995 EDITION I wrote this set of lecture notes for use in the course Functional Programming (CSCI 555) that I teach in the Department of Computer and Information Science at the Uni- versity of Mississippi. The course is open to advanced undergraduates and beginning graduate students. The first version of these notes were written as a part of my preparation for the fall semester 1993 offering of the course. This version reflects some restructuring and revision done for the fall 1994 offering of the course|or after completion of the class. For these classes, I used the following resources: Textbook { Richard Bird and Philip Wadler. Introduction to Functional Program- ming, Prentice Hall International, 1988 [2]. These notes more or less cover the material from chapters 1 through 6 plus selected material from chapters 7 through 9. Software { Gofer interpreter version 2.30 (2.28 in 1993) written by Mark P. -
Design Patterns in Ocaml
Design Patterns in OCaml Antonio Vicente [email protected] Earl Wagner [email protected] Abstract The GOF Design Patterns book is an important piece of any professional programmer's library. These patterns are generally considered to be an indication of good design and development practices. By giving an implementation of these patterns in OCaml we expected to better understand the importance of OCaml's advanced language features and provide other developers with an implementation of these familiar concepts in order to reduce the effort required to learn this language. As in the case of Smalltalk and Scheme+GLOS, OCaml's higher order features allows for simple elegant implementation of some of the patterns while others were much harder due to the OCaml's restrictive type system. 1 Contents 1 Background and Motivation 3 2 Results and Evaluation 3 3 Lessons Learned and Conclusions 4 4 Creational Patterns 5 4.1 Abstract Factory . 5 4.2 Builder . 6 4.3 Factory Method . 6 4.4 Prototype . 7 4.5 Singleton . 8 5 Structural Patterns 8 5.1 Adapter . 8 5.2 Bridge . 8 5.3 Composite . 8 5.4 Decorator . 9 5.5 Facade . 10 5.6 Flyweight . 10 5.7 Proxy . 10 6 Behavior Patterns 11 6.1 Chain of Responsibility . 11 6.2 Command . 12 6.3 Interpreter . 13 6.4 Iterator . 13 6.5 Mediator . 13 6.6 Memento . 13 6.7 Observer . 13 6.8 State . 14 6.9 Strategy . 15 6.10 Template Method . 15 6.11 Visitor . 15 7 References 18 2 1 Background and Motivation Throughout this course we have seen many examples of methodologies and tools that can be used to reduce the burden of working in a software project. -
Jean Lipman-Blumen: Bush: Perhaps the Most Toxic Leader of Our Time
Jean Lipman-Blumen: Bush: Perhaps the Most Toxic Leader of Our Time http://www.huffingtonpost.com/jean-lipmanblumen/bush-perhaps-the-mo... March 11, 2013 As President George W. Bush exits the White House, the trail of destruction he leaves behind bears many earmarks of a toxic leader. Toxic leaders, by virtue of their dysfunctional personal qualities and destructive behavior, inflict serious and enduring harm on their followers, as well as many others who happen to cross their path. In fact, the "quick and dirty" measure of toxic leaders is that they leave us worse off than they found us. Few could deny that the label "toxic leader" seems custom-made for our forty-third president, who turns over the keys to the Oval Office in just a few days. Bush has left the US in disarray domestically and has diminished our position internationally. Mostly, he has done this through a combination of incompetence, arrogance, and stubbornness, characteristics which President Bush shares with many other toxic leaders. Incompetence draws toxic leaders into poor decisions. Arrogance keeps toxic leaders from recognizing the inadequacy or downright destructiveness of their choices. And stubbornness makes toxic leaders persist on their poisonous course even when others shine a spotlight on its toxicity. But these traits aren't even the worst of toxic leadership. Incompetence, arrogance, and stubbornness actually fall on the mild end of the "toxic" spectrum, compared to those of other deliberately evil leaders. If incompetence, arrogance, and stubbornness were the only claims against Bush, it would be tragic enough. Unfortunately, Bush has earned the title of a full-fledged toxic leader by violating the basic standards of human rights of both ordinary American citizens, as well as our alleged opponents. -
Scala by Example (2009)
Scala By Example DRAFT January 13, 2009 Martin Odersky PROGRAMMING METHODS LABORATORY EPFL SWITZERLAND Contents 1 Introduction1 2 A First Example3 3 Programming with Actors and Messages7 4 Expressions and Simple Functions 11 4.1 Expressions And Simple Functions...................... 11 4.2 Parameters.................................... 12 4.3 Conditional Expressions............................ 15 4.4 Example: Square Roots by Newton’s Method................ 15 4.5 Nested Functions................................ 16 4.6 Tail Recursion.................................. 18 5 First-Class Functions 21 5.1 Anonymous Functions............................. 22 5.2 Currying..................................... 23 5.3 Example: Finding Fixed Points of Functions................ 25 5.4 Summary..................................... 28 5.5 Language Elements Seen So Far....................... 28 6 Classes and Objects 31 7 Case Classes and Pattern Matching 43 7.1 Case Classes and Case Objects........................ 46 7.2 Pattern Matching................................ 47 8 Generic Types and Methods 51 8.1 Type Parameter Bounds............................ 53 8.2 Variance Annotations.............................. 56 iv CONTENTS 8.3 Lower Bounds.................................. 58 8.4 Least Types.................................... 58 8.5 Tuples....................................... 60 8.6 Functions.................................... 61 9 Lists 63 9.1 Using Lists.................................... 63 9.2 Definition of class List I: First Order Methods.............. -
Impact of Toxic Leadership on Counterproductive Work Behavior with the Mediating Role of Psychological Contract Breach and Moderating Role of Proactive Personality
Monografico DOI: http://dx.doi.org/10.25115/eea.v39i4.4879 Volumen:39-4 // ISSN: 1133-3197 Impact of Toxic Leadership on Counterproductive Work Behavior with the Mediating role of Psychological Contract Breach and Moderating role of Proactive Personality MUHAMMAD BILAL KAYANI1, IMRAN IBRAHIM ALASAN2 1 LIMKOKWING UNIVERSITY OF CREATIVE TECHNOLOGY, CYBERJAYA, MALAYSIA E-mail: [email protected] 2LIMKOKWING UNIVERSITY OF CREATIVE TECHNOLOGY, CYBERJAYA, MALAYSIA E-mail: [email protected] ABSTRACT This paper focused the conceptualizations of toxic leadership and analyzes the relationship between toxic leadership and counterproductive work behavior (CWB). The mediating role of psychological contract breach was measured between the toxic leadership and counterproductive work behavior, also by analyzing the moderating effect of proactive personality. The selected sample for research comprised of 355 nurses serving in public sector of Pakistan and questionnaire was used as a research tool. Findings of the data revealed that toxic leadership is having a positive significant relationship with CWB and a negative with PCB in partial mediation model. PCB was found to be positively associated with CWB whereas Proactive personality was identified for weakening the relationship of PCB and CWB. The results of the study elaborated that firms ought to illuminate unmistakably to managers about the antagonistic outcomes brought about by toxic oversight, and may join rules or approaches to rebuff toxic practices. Given the counterproductive impact of toxic leadership, more information is exclusively required regarding causes of toxic leadership and the paper concluded with recommendations for future research and action. Keywords: Toxic Leadership, Psychological Contract Breach, Counterproductive Work Behavior, Proactive Personality JEL classification: J53, M10, M59. -
THE ALLURE of TOXIC LEADERS: WHY FOLLOWERS RARELY ESCAPE THEIR CLUTCHES By: Jean Lipman-Blumenissues: January / February 2005
THE ALLURE OF TOXIC LEADERS: WHY FOLLOWERS RARELY ESCAPE THEIR CLUTCHES by: Jean Lipman-BlumenIssues: January / February 2005. Categories: Leadership. • Share on LinkedIn • Share on googlePlus • Share on facebook • Share on twitter • Share by email Toxic leadership is a growing — and costly — phenomenon. Yet individual and organizations can stop the insidious spread of toxicity, by understanding why we are seduced by the false promises of toxic leaders, and by setting up organizational defence mechanisms to counter the spread of toxicity. This author has some excellent suggestions. This article is based on her book, The Allure of Toxic Leaders: Why We Follow Destructive Bosses and Corrupt Politicians – and How We Can Survive Them, Jean Lipman-Blumen (New York: Oxford University Press), 2005. A curious paradox surrounds toxic leaders wherever they take the stage, from the executive suite to the religious pulpit. It is this: While most of us followers complain about toxic leaders, nonetheless, we almost always stay the course. How do we explain that paradoxical scenario, evident in virtually every society from earliest recorded history? Why do we followers not only tolerate, but so often prefer, and sometimes even create toxic leaders – in for-profit corporations, non-profits, government, even educational and religious institutions? Why do we permit so many toxic leaders to hold sway in virtually all arenas of human endeavour? As you might suspect, there are no easy answers here. Yet, a major part of the answer can be pieced together from three enduring sources: the internal needs and human condition of the followers; the interactions between followers and their own environments; and followers’ relationships with toxic leaders. -
61A Lecture 6 Lambda Expressions VS Currying
Announcements • Homework 2 due Tuesday 9/17 @ 11:59pm • Project 2 due Thursday 9/19 @ 11:59pm • Optional Guerrilla section next Monday for students to master higher-order functions . Organized by Andrew Huang and the readers 61A Lecture 6 . Work in a group on a problem until everyone in the group understands the solution • Midterm 1 on Monday 9/23 from 7pm to 9pm Friday, September 13 . Details and review materials will be posted early next week . There will be a web form for students who cannot attend due to a conflict 2 Lambda Expressions >>> ten = 10 An expression: this one evaluates to a number >>> square = x * x Also an expression: evaluates to a function Lambda Expressions >>> square = lambda x: x * x Important: No "return" keyword! A function with formal parameter x that returns the value of "x * x" >>> square(4) 16 Must be a single expression Lambda expressions are not common in Python, but important in general (Demo) Lambda expressions in Python cannot contain statements at all! 4 Lambda Expressions Versus Def Statements def square(x): square = lambda x: x * x VS return x * x • Both create a function with the same domain, range, and behavior. • Both functions have as their parent the environment in which they were defined. Currying • Both bind that function to the name square. • Only the def statement gives the function an intrinsic name. The Greek letter lambda Example: http://goo.gl/XH54uE 5 Function Currying def make_adder(n): return lambda k: n + k >>> make_adder(2)(3) There's a general 5 relationship between (Demo) >>> add(2, 3) these functions 5 Newton's Method Currying: Transforming a multi-argument function into a single-argument, higher-order function. -
CSE 341 : Programming Languages
CSE 341 : Programming Languages Lecture 10 Closure Idioms Zach Tatlock Spring 2014 More idioms • We know the rule for lexical scope and function closures – Now what is it good for A partial but wide-ranging list: • Pass functions with private data to iterators: Done • Combine functions (e.g., composition) • Currying (multi-arg functions and partial application) • Callbacks (e.g., in reactive programming) • Implementing an ADT with a record of functions (optional) 2 Combine functions Canonical example is function composition: fun compose (f,g) = fn x => f (g x) • Creates a closure that “remembers” what f and g are bound to • Type ('b -> 'c) * ('a -> 'b) -> ('a -> 'c) but the REPL prints something equivalent • ML standard library provides this as infix operator o • Example (third version best): fun sqrt_of_abs i = Math.sqrt(Real.fromInt(abs i)) fun sqrt_of_abs i = (Math.sqrt o Real.fromInt o abs) i val sqrt_of_abs = Math.sqrt o Real.fromInt o abs 3 Left-to-right or right-to-left val sqrt_of_abs = Math.sqrt o Real.fromInt o abs As in math, function composition is “right to left” – “take absolute value, convert to real, and take square root” – “square root of the conversion to real of absolute value” “Pipelines” of functions are common in functional programming and many programmers prefer left-to-right – Can define our own infix operator – This one is very popular (and predefined) in F# infix |> fun x |> f = f x fun sqrt_of_abs i = i |> abs |> Real.fromInt |> Math.sqrt 4 Another example • “Backup function” fun backup1 (f,g) = fn x => case -
Scala-Language.Pdf
Scala Language #scala Table of Contents About 1 Chapter 1: Getting started with Scala Language 2 Remarks 2 Versions 2 Examples 3 Hello World by Defining a 'main' Method 3 Hello World by extending App 4 Delayed Initialization 4 Delayed Initialization 4 Hello World as a script 5 Using the Scala REPL 5 Scala Quicksheet 6 Chapter 2: Annotations 8 Syntax 8 Parameters 8 Remarks 8 Examples 8 Using an Annotation 8 Annotating the main constructor 8 Creating Your Own Annotations 9 Chapter 3: Best Practices 11 Remarks 11 Examples 11 Keep it simple 11 Don't pack too much in one expression. 11 Prefer a Functional Style, Reasonably 12 Chapter 4: Case Classes 13 Syntax 13 Examples 13 Case Class Equality 13 Generated Code Artifacts 13 Case Class Basics 15 Case Classes and Immutabilty 15 Create a Copy of an Object with Certain Changes 16 Single Element Case Classes for Type Safety 16 Chapter 5: Classes and Objects 18 Syntax 18 Examples 18 Instantiate Class Instances 18 Instantiating class with no parameter: {} vs () 19 Singleton & Companion Objects 20 Singleton Objects 20 Companion Objects 20 Objects 21 Instance type checking 21 Constructors 23 Primary Constructor 23 Auxiliary Constructors 24 Chapter 6: Collections 25 Examples 25 Sort A List 25 Create a List containing n copies of x 26 List and Vector Cheatsheet 26 Map Collection Cheatsheet 27 Map and Filter Over A Collection 28 Map 28 Multiplying integer numbers by two 28 Filter 28 Checking pair numbers 28 More Map and Filter examples 29 Introduction to Scala Collections 29 Traversable types 30 Fold 31 Foreach 32 Reduce 32 Chapter 7: Continuations Library 34 Introduction 34 Syntax 34 Remarks 34 Examples 34 Callbacks are Continutations 34 Creating Functions That Take Continuations 35 Chapter 8: Currying 37 Syntax 37 Examples 37 A configurable multiplier as a curried function 37 Multiple parameter groups of different types, currying parameters of arbitrary positions 37 Currying a function with a single parameter group 37 Currying 38 Currying 38 When to use Currying 39 A real world use of Currying.