DESCRIPTION: The introduction explains what are the industy wide problems the book aims to tackle, why are they worth solving
and how can all this benefit You. Of course there's some personal introduction and you will read about how the author came up with this whole idea.
DESCRIPTION: The book starts off with asking then answering some of the most fundamental questions about our work. Questions we usually don't even think about,
concerning the very nature of software and development itself. Why? Because the answers will define the core philosophy of Full Context Development.
DESCRIPTION: This chapter defines the conceptual, high-level framework we will use to evaluate technology choices.
It starts with business value and arrives at all the tools we have to influence it.
It finishes with a structural overview of the main ideas of Full Context Development.
DESCRIPTION: Here we discuss the exact business mechanics how the User API delivers the 4 business value types.
This ensures our system and decisions are grounded in real facts.
Then we summarize the actions developers can take to influence each value category.
DESCRIPTION: This chapter teaches what's relevant for a software engineer about the components of customer experience
so we can later discuss our influence over this area and evaluate our technical decisions from the perspective of our users.
DESCRIPTION: This chapter introduces how to view the software you create as a product, what defines it's quality
in this regard and summarizes all the ways the different technical attributes affect it. It also connects everything discussed
in the previous 2 chapters with this topic to offer a systemic overview of our influence over the users.
DESCRIPTION: Here you will learn not only about the ways we have to create positive experiences for the users
but all the technical details how we actually implement that (even unknowingly) with the everyday work wo do.
Rest assured it's relevant to all engineers regardless of specialization.
DESCRIPTION: Here we set the stage for the next couple of chapters about the organizational aspect of our work.
It explains how much of the Full Context reaches us in a typical software company
and how can we uniquely utilize that knowledge. This defines the baseline the book teaches you how to exceed.
DESCRIPTION: Our technical choices can deeply affect the efficiency of organizations.
This chapter explains the elementary knowledge about organizational structure and performance
to help you understand all the relevant factors while discussing our influence over this area.
DESCRIPTION: The main topics discussed here are the 2 major process optimization methodologies,
specifically adopted by the author to the software development workflow. This is a hands down take
on the subject that's easily applicable in technical decision making.
DESCRIPTION: You will learn a method how to approach evaluating the consequences of technology choices
over the performance of an organization. It also includes the final API of the material the Developer API,
describing how technology affects our lives and feelings.
DESCRIPTION: In this chapter we laser-focus on code. The goal is to identify both the general and the
specific attributes of any codebase that has a relationship with the other elements of the Full Context.
You will learn the universal optimization targets of code.
DESCRIPTION: The cherry on top of the cake, the best part of the material, you will learn how the timeless and universal
properties of any software technology ripple through the Full Context and finally deliver business value. This a practical overview
that can be used as a checklist at evaluation.
DESCRIPTION: In the final chapter we build up a complementary work methodology that helps to identify and track the real values of any software project
and show how to constantly align our decisions with them.
DESCRIPTION: These guides offer exact processes to follow when identifying the value-defining elements of the Full Context.
Here you will learn how to analyze the purely business related factors that should influence your decision-making process.
DESCRIPTION: What are the relevant properties of a project that should drive technical decisions? This is another
timeless topic that will help you to better align your choices with the real goals regardless of the technolgies in use.