Advertisement

Context, Rules, and Principles

  • Ervin Varga
Chapter
  • 336 Downloads

Abstract

Context awareness is like defensive programming in a sense that it creates a powerful feedback loop and control mechanism to reinforce or reject an action or idea. This chapter explains the interplay between context and knowledge (partly embodied as a set of rules and principles), as well as give examples of how things can turn upside down when actions are thoughtlessly executed. The aim of this chapter is to demonstrate the following concepts: context, rules, and principles.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

Further Reading

  1. 1.
    Petzold C (2000) Code: the hidden language of computer hardware and software. Microsoft Press, Redmond, WA. This book is all about the socio-technical context surrounding computers and computing/communication. It starts from the early periods of a human history, and analyses our need to communicate. The book shows how different theoretical and practical solutions were built on top of each other until it arrives at a modern computer architecture; it sets up a quest to reach the roots regarding the established binary number systemGoogle Scholar
  2. 2.
    English edition: Dostoevsky F (2008) The idiot (trans: Martin EM). Digireads.com Publishing, New York, NY. This book is a masterpiece in the domain of human psychology (F. Nietzsche, who rarely gave compliments, called Dostoevsky “the only psychologist from whom I was able to learn anything.”). Through the story, that depicts the never-ending battle between good and evil, the book challenges a reader to tune in to detect even the most delicate contextual variations. Such an ability is crucial for becoming a good communicator.

Regular Bibliographic References

  1. 3.
    Varga E (2016) Simplicity can’t be attained greedily. www.linkedin.com/pulse/simplicity-cant-attained-greedily-ervin-varga. Accessed 25 Jun 2017
  2. 4.
    Gamma E, Vlissides J, Johnson R, Helm R (1994) Design patterns: elements of reusable object-oriented software. Addison-Wesley, Reading, MAzbMATHGoogle Scholar
  3. 5.
    Varga E (2016) Instead of rules tell a story. www.linkedin.com/pulse/instead-rules-tell-story-ervin-varga. Accessed 25 Jun 2017
  4. 6.
    Varga E (2016) Do APIs matter? www.apress.com/gp/blog/all-blog-posts/do-apis-matter/11524110. Accessed 25 Jun 2017
  5. 7.
    Weimer C, Bolger F (2017) Continuous code inspection: advancing software quality at source. PRQA Programming Research, SurreyGoogle Scholar
  6. 8.
    Ackley DH (2013) Beyond efficiency. Commun ACM 56(10):38–40CrossRefGoogle Scholar
  7. 9.
    Lions JL (1996) Arian 5 flight 501 failure – report by the inquiry board. www-users.math.umn.edu/~arnold/disasters/ariane5rep.html. Accessed 18 Aug 2017
  8. 10.
    Armour PG (2013) When faster is slower. Commun ACM 56(10):30–32CrossRefGoogle Scholar
  9. 11.
    Holmes N (2011) The profession and digital technology. IEEE Comput 44(12):114–116CrossRefGoogle Scholar
  10. 12.
    Bouwers E, Visser J, Deursen AV (2012) Getting what you measure. Commun ACM 55(7):54–59CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Ervin Varga
    • 1
  1. 1.Expro I.T. ConsultingKikindaSerbia

Personalised recommendations