Kirjahaku

As the Roman empire declined and ‘fell’, contemporary glorification of the emperor’s triumphal rulership reached new heights, strewing traces of the empire’s perennial victory across the physical and mental landscape of late antiquity. In this, the first comprehensive study of how a great imperial ceremony actually developed and how it influenced both the eastern and western heirs to the Roman legacy, the Roman triumph’s resurgence and afterlife is documented from the Tetrarchy to the end of the Macedonian dynasty in Byzantium and to Charlemagne’s successors in the early medieval West. This perspective shows that celebrations of the ruler’s victory experienced unceasing change in ritual form and content and that these changes mirrored broader trends in the development of society and the monarchy. At the same time, it casts new light on the late Roman origins of the trappings of early medieval kingship. Far from the imperial capital, the cult of triumphal rulership permeated local elites, as commanders in the provinces imitated the supreme victor by staging triumphs of their own, and the new Germanic kings followed suit. Classicists, medievalists, Byzantinists, specialists of art and ritual will find here new data and approaches to a central problem in the transformation of the Roman Empire which culminated in the new civilization by Byzantium and the Germanic Kingdoms.

Apply the industrial engineering science of invention and assembly to how software is described, planned, and built, allowing you to be free to flex your practices according to your needs, putting principle over habit and rules.Reading about Agile practices is like reading diet advice. Everything sounds unique and good; everything starts with good intentions. Then reality sets in. Organizations adapt their practices, but lose sight of grounding principles. A bias toward ceremonies, metrics, and recipes comes at the expense of efficiently getting the real work done. Managers and developers are incentivized to game the system. Organizational metrics become detached from the reality of what is being delivered and how.The Agile Codex shows you how to describe a software project as an acyclic dependency tree of sized work items, scoped to be operated on by one software engineer each and completed within a week. It provides Open Source tooling to help you visualize, sequence and assign these work items to account for risk and increase predictability in your delivery times. You’ll see the value of doing this as it applies to efficiently planning and adjusting software projects in the face of learning and change. Finally, the book covers the collaborative agile principles required to bring this skill set and practice to a software team.Throughout the book you’ll be reminded that software engineering is not a rote task - it is primarily a skilled, creative act. As such, you’ll see that we need to account for the space needed toresearch, plan, create, and adjust. The Agile practices serving the codex deal with this intersection between the engineering problem of software delivery flow, and the human reality of how work is described, owned, executed, and transitioned from one state to another.Everything an agile team does must serve the codex. The creation and the care and feeding of this structured tree of work sets the frame in which all other team actions take place and against which all successes or failures can be evaluated.