What if we did not take anything we think we know about the domain, the people, the organisation for which we are building software for granted? If we turned our attention to and focused on how these things appear to us, rather than assuming they are objects external to our consciousness? Would it help us produce "better" software in some sense?
This is a question that Phenomenology, a philosophical approach founded by Edmund Husserl in the early XXth century, attempts to answer within various quarters of human experience.
This talk is an invitation to apply phenomenological investigation tools and concepts like epoché or reduction to code and coding, and observe what is left of things as obvious as domains, users, stakeholders, experts, or even code itself, when we forego assumptions of their objective existence.

While the title of this session sounds pretentious, phenomenology being a complicated word buried under decades of complex writings, I will try to avoid the jargon and anchor it into the day-to-day experience of people actually working with code.
The purpose of this session is to provoke, awaken, puzzle participants and encourage them, or us, to step aside and really think about the things we don't question anymore.