Libby Gill · RePEc: Research Papers in Economics
Abstract WHEN RUDY KARSAM, CEO OF GLOBAL HUMAN RESOURCES FIRM Kenexa, says that his company defines trust by making a promise and then fulfilling the commitment, he’s ready to back it up. “We have a 90 percent renewal rate among our clients, we serve more than half of the Fortune 500, and we’re operating in more than 100 countries, ” states Karsam in the welcome video posted on the company’s website. But the stats don’t begin to tell the story for this company that prides itself on making business personal. “Our business is so focused on relationships, ” continues Karsam, “that our people have been in our clients’ wedding parties, they’ve become godparents to their children, and many have become lifelong friends.”1 If that’s not making business personal, I don’t know what is.
Cited by 0
Bulletin of Miscellaneous Information (Royal Gardens Kew)
Cited by 0
Ray Buse, Wes Weimer, De Ltadoc · 2011
< else return "";> else return pageParts[0];> / / else return "";
Cited by 0
Altay Brusan, Aytaç Durmaz · Maker Innovations Series · 2022
Commits contain tangible units of progress toward the project’s goal. Each commit is indeed a pace in the project road map. In the ideal world, all commits are self-sufficient and do not require any modification after they are submitted into a repository. However, in the real world, this is not the case all the time! For example, after submitting we may find the commit message is not clear enough or it does not include all pieces of information. For such situations, Git envisioned a list of actions to update history:
Cited by 0
Hagemann, Birger, Hogeweg, Sebastian, Strobel, Gion · Göttingen Research Online · 2024
Cited by 0Open access
Maximilian Steff, Barbara Russo · 2013
We present commit graphs, a graph representation of the commit history in version control systems. The graph is structured by commonly changed files between commits. We derive two analysis patterns relating to bug-fixing commits and system modularity.
Cited by 1
Nitin undefined · 2023
Feedback points to be done Faded image in downloaded article When we proceed to submission other fields are not editable Remove ‘continue’ in submit article popup UI corrections in Editor screen detail screen All articles section sorting and UI Recommend articles UI correction Ordering is not correct in All sections for articles Error issue of ‘Please try again’ while performing action on article and on login after signed up Edit/report functioning
Cited by 0Open access
Patrick Emmenegger, Lucas Leemann, André Walter · Harvard Dataverse · 2020
:unav
Cited by 0Open access
Patrick Emmenegger, Lucas Leemann, André Walter · Harvard Dataverse · 2020
:unav
Cited by 0Open access
Cassalho, Felicio · George Mason University · 2022
Cited by 0Open access
Jacob LaRiviere · Harvard Dataverse · 2020
:unav
Cited by 0Open access
Gordon B. Bell, Mikko H. Lipasti · 2004
Many modern processors execute instructions out of their original program order to exploit instruction-level parallelism and achieve higher performance. However even though instructions can execute in an arbitrary order, they must eventually commit, or retire from execution, in program order. This constraint provides a safety mechanism to ensure that mis-speculated instructions are not inadvertently committed, but can consume valuable processor resources and severely limit the degree of parallelism exposed in a program. We assert that such a constraint is overly conservative, and propose conditions under which it can be relaxed. This paper deconstructs the notion of commit in an out-of-order processor, and examines the set of necessary conditions under which instructions can be permitted to retire out of program order. It provides a detailed analysis of the frequency and relative importance of these conditions, and discusses microarchitectural modifications that relax the in-order commit requirement. Overall, we found that for a given set of processor resources our technique achieves speedups of up to 68% and 8% for floating point and integer benchmarks, respectively. Conversely, because out-of-order commit allows more efficient utilization of cycle-time limiting resources, it can alternatively enable simpler designs with potentially higher clock frequencies.
Cited by 39
Oxford University Press eBooks · 2023
Cited by 0
Titus Barik, Kevin Lubick, Emerson Murphy-Hill · 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering · 2015
Developers who use version control are expected to produce systematic commit histories that show well-defined steps with logical forward progress. Existing version control tools assume that developers also write code systematically. Unfortunately, the process by which developers write source code is often evolutionary, or as-needed, rather than systematic. Our contribution is a fragment-oriented concept called Commit Bubbles that will allow developers to construct systematic commit histories that adhere to version control best practices with less cognitive effort, and in a way that integrates with their as-needed coding workflows.
Cited by 6
Koch, Max · Göttingen Research Online · 2020
Cited by 0Open access
Lucas Leemann, Leonardo Baccini · Harvard Dataverse · 2020
:unav
Cited by 0Open access
Nicholas Chesterley · McGill-Queen's University Press eBooks · 2025
Cited by 0
Hogeweg, Sebastian · Göttingen Research Online · 2024
Cited by 0Open access
Directory of Open Access Journals (EBSCO) · 2016
Cited by 0Open access
Bulletin of Miscellaneous Information (Royal Gardens Kew)
Cited by 0