Chiara C. Rizzarda's Blog, page 31

#ChthonicThursday: Ninpumuna, Goddess of Salt

Ninpumuna was a deity from Mesopotamian mythology, associated explicitly with salt springs. Her name translates to “mistress of the salt spring,” and she is primarily recognized as a goddess linked to these natural features and possibly the underworld. She is mentioned in contexts related to offerings and rituals, often alongside other deities associated with the underworld. The connection with salt springs is significant in the context of the geography of ancient Mesopotamia, where salt deposits and springs were essential for various practical and ritual purposes. As the goddess of these natural features, Ninpumuna would have been venerated for her control and influence over resources crucial for daily life and religious practices.

The sources of salt in Ancient Mesopotamia were primarily two:

Salterns, evaporation pools where salt was extracted from seawater. Historical documentation suggests that salterns existed in areas where the water table was closer to the surface, allowing for salt crust formation;Groundwater, which contributed to the availability of salt resources, influenced the salinity of rivers like the Euphrates and Tigris as they approached the Shatt al-Arab. This salinity affected irrigation practices, leading to salt accumulation in the landscape.

Evidence from cuneiform tablets indicates that salt was a significant commodity in ancient Mesopotamia, with records dating back to the Early Dynastic period (circa 2900–2350 BCE), which made salt one of the commodities that needed to be managed at an urban scale.
The salt trade became a vital economic activity during Hellenism. The Seleucid administration developed a tax system related to the salt trade, reflecting its economic significance.
Major centres for salt trade included Seleucia on the Tigris and Uruk, where extensive archival records have been found.

While Ninpumuna is less prominent than major deities like Enlil or Inanna, her worship is documented in texts from the Ur III period, particularly in the cities of Ur and Puzrish-Dagan. She is primarily attested in texts dating back to the reigns of kings Amar-Sin and Ibbi-Sin, roughly within a forty-year span of the Ur III period.

She appears in offering lists alongside other deities such as Ninazu—the deity of the underworld, healing, and agriculture—and Ningishzida, “Lord of the Good Tree”, and… well, snakes. But that’s a different story. Documentation includes references to her clergy, such as a “saĝĝa of Ninpumuna,” which translates to “temple administrator” and indicates she had dedicated priests responsible for her worship.

In case you want to learn more, scholarly works include those by Dina Katz, Annabelle Staiger, and Mark E. Cohen, discussing her character and worship in the context of Sumerian religion, and she features in The God Ninurta in the Mythology and Royal Ideology of Ancient Mesopotamia by Amar Annus.

Autodesk University 2024 – My Personal Selection (1)

The catalogue of classes for Autodesk University 2024 is here, and I have the privilege of having been selected amongst the speakers, so around October 13th I’ll be flying to San Diego with my significant otter and I’ll bask in a whole week of networking and high-level training. The event includes more than 650 sessions, and one of them is mine: “The Three-Horizons Problem: Using LEGO Serious Play for Climate-Resilient Infrastructure Design” (id. CI1542). It’s my most ambitious project so far and I’m super-thrilled to be able to present it. It’ll take place Tuesday, Oct 15 3:00 PM – 4:00 PM.

You can bookmark classes by clicking on the symbol at the top right corner of each page.

I’ve been browsing the catalogue and here’s my personal selection of the classes I’m considering attending. They’re roughly grouped by topic.

 

Industry Innovation, Gamification and Design Thinking

Kenton Grant, AS4425 | Establishing a Design Technology Department
Tuesday, Oct 15
1:30 PM – 2:30 PM PDT

This session will explore Olson Kundig’s journey in forming a new design technology (DT) department, sharing insights from their foundational year. It will highlight their collaboration with leadership to align the department’s vision with firm goals, strategies for fostering creativity and efficiency and building a dynamic team. The discussion will cover empowering DT leaders, overcoming challenges, and best practices for establishing a successful DT department. Attendees will learn both strategic and practical aspects of building and leading a DT department that significantly impacts project outcomes and firm-wide innovation.

Olson Kundig was the design firm behind these spectacular kinetic facades.

 

Sen Zhang, AS2603 | Revit as a Game Engine
Tuesday, Oct 15
1:30 PM – 2:30 PM PDT

This session will explore the concept of treating Building Information Modeling (BIM) software as a game engine, drawing parallels between BIM management and game design. It will cover designing user-friendly workflows, handling exceptions, and keeping users engaged, all within the limitations of Revit software. The presentation will showcase games built entirely within Revit and efforts to gamify professional production work at Ennead Architects, highlighting innovative approaches to using BIM in architecture.

Ennead Architects designed the Shanghai Astronomy Museum, and it’s a wonder to behold.

 

Laura Kalinowski, EDU1050 | Enhancing Lesson Plans and Strengthening Industry Partnerships: A Collaborative Workshop for CTE Teachers
Tuesday, Oct 15
3:00 PM – 4:00 PM PDT

This collaborative workshop aims to foster innovation, collaboration, and partnership within the Career and Technical Education (CTE) community. It will focus on enhancing lesson plans, building industry partnerships, and engaging post-secondary educators to better prepare students for the evolving workforce. Industry professionals are invited to contribute their expertise in designing hands-on activities and industry-specific lesson plans, while teachers are encouraged to bring their ideas for collaboration. Attendees will actively engage, ask questions, and help establish a national network of STEM teachers and industry partners.

Laura Kalinowski, EDU1054 | Empowering Tomorrow’s Innovators: Fostering a Connection Between Industry and STEM Programs for Girls
Tuesday, Oct 15
4:30 PM – 5:30 PM PDT

Also dubbed “Maker Girl Mania: Inspiring Future STEM Leaders Part Two,”, the presentation will delve into the vital connection between industry and STEM education to inspire girls. Highlighting the impactful programs Maker Girl Mania and Tech Girls, the session will showcase how industry collaboration enhances STEM learning experiences, fostering creativity, problem-solving skills, and innovation. Participants will gain insights into best practices for engaging with schools and existing programs, aiming to create supportive environments for girls to excel in STEM fields. Join us to unlock the potential of the next generation of female innovators.

If you want to educate yourself on the ongoing effort to close the gap between women and men in STEM education, you can start by reading this.

Jared Coelho, CS4375 | AEC Workforce Development: The Path to Human Flourishing
Wednesday, Oct 16
4:30 PM – 5:30 PM PDT

This session will highlight the partnership between Autodesk and the California Prison Industry Authority (CALPIA), focusing on how integrating Autodesk software into their Continuing Technical Education program helps marginalized communities enter the architecture, engineering, and construction industry. The discussion will emphasize proactive engagement strategies to enhance the pipeline of talented and productive entrants from these communities.

Labour in prison isn’t an issue I suggest you take lightly. You can start by reading this, and then you can watch the special by John Oliver on the topic.

 

Jordan Giboney, AS3002 | M&E Magic in AEC
Wednesday, Oct 16
4:30 PM – 5:30 PM PDT

This class will showcase how the gamer generation, now in the workforce, is leveraging technology for fast, high-quality results in architecture, engineering, and construction. Participants will learn how the Autodesk Media and Entertainment collection can enhance AEC storytelling, visualization, and simulation and explore game engine workflows to create immersive experiences that expedite project completion.

 

Harrison Daigle, AS2579 | Outcome-Based Design: The Shift of Design Technology and Tools
Thursday, Oct 17
12:00 PM – 1:00 PM PDT

This session will explore the evolution of design and drafting tools, from CAD and BIM to AI, and how these technologies can prepare teams for the future. It will draw on experiences from a multidisciplinary design firm, highlighting the varied technology adoption rates and digital maturity across planning, landscape, architecture, and interiors. The focus will be on using lessons learned from completed projects as quantitative outcomes to inform new projects. By analyzing over 50 years of digital asset creation and completed projects, the session aims to uncover the potential within digital archives for enhancing future design processes.

 

Data Management

Jeremiah Owens, CS3022 | Data Sharing: When, Where, Why, and How?
Tuesday, Oct 15
1:30 PM – 2:30 PM PDT

This talk will address the importance of data sharing and collaboration in the design world, emphasizing how essential it is for minimizing costly construction mistakes. It will explore the potential of cloud tools for collaboration and discuss the challenges and questions surrounding effective data-sharing practices. Key questions to be answered include when and how to share information, the frequency of sharing, and ensuring that all project information is accessible to everyone.

 

Urban Design and Heritage

Ciaran Garrick, AS2220 | Preserving Our Heritage: Technology Strategies for the Digitization and Reuse of Existing Buildings
Tuesday, Oct 15
12:00 PM – 1:00 PM PDT

This talk will explore how technology, particularly Building Information Modeling (BIM), is playing a crucial role in preserving architectural heritage. It will present practical examples of documenting and adapting historic buildings using BIM, highlighting the capture of intricate details and their integration with contemporary spaces. The discussion will focus on developing project-specific BIM strategies for heritage buildings, and the necessary team skills, technology, and data to successfully deliver these projects.

 

Natalia Montero, AS4123 | Toward Safe and Inclusive Urban Landscapes: Bringing BIM and GIS Together
Wednesday, Oct 16
4:30 PM – 5:30 PM PDT

This talk will explore how integrating BIM (Building Information Modeling) and GIS (Geographic Information Systems) can help address spatial challenges in urban and infrastructure projects, enabling data collection and management to prioritize solutions effectively. Participants will learn to implement GIS interoperability with BIM in early-stage planning to create more sustainable, inclusive, and welcoming cities.

 

Artificial Intelligence

Dennis Goff, AS1412 | Artificial Intern: Let the Robots Get the Coffee
Tuesday, Oct 15
1:30 PM – 2:30 PM PDT

This class will explore the impact of AI on the architectural profession, emphasizing that AI can enhance rather than replace the work of architects. It will demonstrate how AI can take over tedious tasks, allowing architects to focus on meaningful design work and enabling junior staff to gain valuable experience. Practical examples from ZGF Architects will illustrate the integration of AI into workflows such as project benchmarking, Revit automation, and semantic search of code documents.

Hangar Design by ZGF Architects

 

Wissam Akra, CS1784 | Overcoming the Project Diversity Dilemma: AI-Powered Solutions for Optimizing Diverse Subcontractor Sourcing
Wednesday, Oct 16
12:00 PM – 1:00 PM PDT

This session will explore the profound impact of diversifying trade partner relationships in the construction industry, highlighting how AI streamlines subcontractor sourcing, enhances compliance, and fosters innovation. Attendees will discover how embracing diversity drives down costs, increases competition, and cultivates a more robust and resilient construction landscape. The presentation will showcase the transformative power of inclusion in propelling the industry forward.

Tough Leaf is a B2B platform that empowers minority and women-owned businesses (XBE) to grow by connecting them with hiring entities such as contractors. Take a look here.

 

Diana Cristina Binciu, AS1653 | From Flat to Fab: Greening Landscapes with Landscape Information Modeling and Artificial Intelligence
Thursday, Oct 17
1:30 PM – 2:30 PM PDT

This session will advocate for the digital evolution of landscape design, transitioning from 2D to Landscape Information Modeling (LIM) with Revit tools and workflows, as demonstrated by Henning Larsen architects. It will also explore how AI can empower landscapers to optimize resource management, enhance water efficiency, and improve sustainability metrics like energy consumption, carbon footprint, and ecological equilibrium.

Henning Larsen Architects is an international architectural firm based in Copenhagen, Denmark, now part of Rambøll.

 

Yael Netser, AS4145 | Ethics in Computational Design: Infusing Equity into AI and Generative Design for Building Design Processes
Thursday, Oct 17
4:30 PM – 5:30 PM PDT

AI and generative design (GD) are revolutionizing the architecture, engineering, and construction industry, enhancing building functionality and sustainability. This talk will present innovative research from Carnegie Mellon University on incorporating equity and social sustainability values into a collaborative GD-ML framework, ensuring ethical and socio-sustainable design decisions are measurable and transparent to all stakeholders for a more equitable and resilient built environment.

 

These are just industry talks. I’ll take a look at the other formats in the upcoming days. What about you? Are you coming to San Diego or attending remote? Do you have a selection already? Share it in the comments!

#ChthonicThursday: Lethe

Lethe, also known as Lesmosyne, was one of the Greek underworld rivers, and particularly the river of unmindfulness (Amelēs potamos): it gained its properties because it flowed around the cave of Hypnos, the god of sleep, son of Night and brother of Death. Whoever drinks from this river experiences forgetfulness. Interestingly enough, though, the Greek word for “truth” is aletheia (ἀλήθεια), which literally is “un-forgetfulness”. If being truthful means remembering, forgetting might not be such a good thing after all.

As it often happens, this concept is lost and subverted in the Roman world: drinking Lethe’s water was a requirement to the shades of the dead, in order to forget their earthly life, and we see this scene in book VI of the Aeneid.

The souls that throng the flood
Are those to whom, by fate, are other bodies ow’d:
In Lethe’s lake they long oblivion taste,
Of future life secure, forgetful of the past.

Lethe is sometimes personified or connected to a goddess. Hesiod identifies her as the daughter of Eris (Strife) in his Theogony, making her the sister of Ponos (Hardship), Limos (Starvation), Algea (Pains), Hysminai (Battles), Makhai (Wars), Phonoi (Murders), Androktasiai (Manslaughters), Neikea (Quarrels), Pseudea (Lies), Logoi (Stories), Amphillogiai (Disputes), Dysnomia (Anarchy), Ate (Ruin), Horkos (Oath).

A merry crowd indeed.

#MerfolkMonday: the Mermaid Passage at Harvington Hall

Harvington Hall is a moated medieval and Elizabethan manor house located in the hamlet of Harvington in Worcestershire, England. Its moat and artificial island trace back to the 13th century to, and the 14th-century building still survives behind a layer of bricks. The hall was owned by several notable figures over the centuries, including Adam de Harvington, Chancellor of the Exchequer, and the Pakington family in the 16th century, and it was under the latter family that the hall was transformed into an Elizabethan manor house, with Humphrey Pakington adding numerous priest holes to hide Catholic priests during the Elizabethan religious persecutions.

The Mermaid Passage is a significant feature within the house’s complex architecture. It is located on the first floor — a tiny, overlooked corridor that leads from the main part of the hall to the Great Staircase — and contains some of the most impressive wall paintings discovered in the hall. These paintings, dating back to the 14th century, were hidden under layers of plaster and depict various scenes, including Biblical scenes like David slaying Goliath. The name is due to the double-tailed mermaid in the picture.

The passage is also notable for its unique architectural design, which — in the very words of the museum curator — will make you “lose all sense of where you are”.

#ChthonicThursdau: Jean Restout’s “Orpheus in the Underworld”

Jean Restout I (1663-1702) was a French baroque painter, and one of his most notable works is “Orpheus in the Underworld to Demand the Return of Eurydice, or Music” (1763), currently preserved at the Louvre Museum.

Today on my Patreon we take a look at this work.

Visualize the Workflow

A few days ago I posted a brief overview of Kanban (far from being the first time I post about it), and some of you reached out to highlight how the first principle, “Visualize the Workflow”, sounded a lot like “Use a kanban board”. A time will come when we’ll have to get into detail on how to set up and use a board. For now, let’s see a decalogue of what’s behind that first principle. Again, the board is just the tip of the iceberg.

Visual Workflow Representation: the kanban board maps out the entire workflow, breaking it into distinct stages. Though sometimes it’s left to the team’s choice, I highly recommend that each stage is represented by a column, making it easy to see the status of tasks at a glance. Columns aren’t for team members nor tasks category. That’s what metadata are for.Task Visualization: cards are meant to represent individual work item which move across the columns as work progresses, providing a clear, real-time view of task status. Cards might have checklists or subtasks, so the level of granularity of each task is a choice to be made.Work in Progress (WIP) Limits: set limits on the number of tasks that can be in any stage of the workflow at one time. This helps identify bottlenecks and ensures a steady flow of work. As we have seen, we should limit the amount of work one starts without finishing it.Clear Policies: define and make visible explicit policies for how work is handled at each stage. This can include criteria for moving tasks between stages, handling blocked items, and prioritizing work. Do you remember the gates of approval in the Common Data Environment? Same principle.Transparency: ensure that all team members have access to the kanban board and can easily understand the current state of the workflow. This promotes shared understanding and accountability, and it’s super-crucial: the board isn’t some secret tool for the project manager to rule them all.Continuous Monitoring and Regular Maintenance: regularly review and update the kanban board to reflect changes in priorities or processes. It’s a dirty job, but someone has to do it. This ensures the board remains an accurate representation of the current workflow.Feedback Loops: incorporate regular feedback sessions, such as daily stand-ups or retrospectives, to discuss the workflow and identify areas for improvement, to help in maintaining the relevance and accuracy of the visualized work.Highlighting Blockers: clearly indicate any blocked tasks on the kanban board to ensure the team quickly identifies and addresses issues that are preventing progress.Flow Metrics: use visual cues and metrics, such as cumulative flow diagrams, to analyze and optimize the workflow. These metrics help in understanding the flow of work and identifying areas for improvement.Collaborative Updates: encourage team members to actively update the board as tasks progress to foster collaboration and ensures that the board reflects the most current information.

What aren’t you doing into your kanban board?

Pair Programming (and how to achieve it)

Pair programming is a software development technique where two programmers work together at a single workstation.

The Roles in Pair Programming are divided between:

Driver: the programmer who writes the code, typing each line as the pair collaborates on the solution.Navigator: the programmer who reviews the code as it is being written, offering suggestions, identifying potential issues, and considering the overall direction of the solution.

The two programmers frequently switch roles, with the driver becoming the navigator and vice versa. This role switching allows both programmers to actively participate in the coding process and gain a comprehensive understanding of the problem and solution.

The primary goals of pair programming are:

Improved code quality: by having two programmers review and discuss the code, potential errors or suboptimal solutions can be identified and addressed early in the development process.Knowledge sharing: pair programming facilitates the exchange of knowledge and skills between the two programmers, allowing them to learn from each other and expand their expertise.Continuous learning and problem-solving: the collaborative nature of pair programming encourages continuous learning and fosters a problem-solving mindset, as the programmers work together to find the best solution to the problem at hand.

But how do you achieve it effectively? Let’s take a look at 15 principles.

Communication: continuous and open dialogue between the two programmers is crucial. Both partners should articulate their thought processes clearly, and this requires a correct mindset / culture. As many Agile practices, you can’t just introduce it out of the blue: it will create more harm than good.Collaboration: both members should contribute equally, leveraging each other’s strengths and compensating for weaknesses. Pair programming is not a method to provide training to a lesser able resource: they will turn into the scribe of the tutor.Role Rotation: regularly switch roles between the “driver” (who writes the code) and the “navigator” (who reviews and suggests improvements).Respect and Empathy: maintain a respectful and empathetic environment where each programmer’s input is valued.Active Listening: both programmers should actively listen to each other’s ideas and feedback without interrupting.Code Quality: make sure participants focus on writing clean, efficient, and maintainable code. Peer review in real-time helps in catching errors early.Shared Goals: align on common objectives for the task at hand, ensuring both partners are working towards the same outcome.Emergent Learning and Teaching: use the session as an opportunity for mutual learning. Experienced developers might mentor juniors, in this context, if juniors are free and able to provide fresh perspectives.Patience and Persistence: understand that it takes time to develop a rhythm and effective collaboration. Patience is key.Environment Setup: ensure the working environment is set up to facilitate seamless collaboration.Feedback Loop: provide and accept constructive feedback continuously to improve both the process and the outcome.Problem-solving: approach problems collaboratively, brainstorming solutions together rather than working independently.Distraction Management: minimize external distractions to maintain focus and productivity during pair programming sessions.Time Management: be mindful of time, taking regular breaks to maintain focus and avoid burnout.Documentation: keep documentation up-to-date and ensure both partners are aware of any changes on the ongoing project.

The principles can be applied in any situation where both participants have the skill and knowledge to participate in the development of the product but might provide different perspectives. Can you think of any?

The header picture is taken from here.

What’s Kanban?

Too often the methodology is reduced to the implementation of a visual task management board (Trello, ClickUp, a Planner, you name it), which remains underused and which people struggle to see the significance of.
That’s because Kanban is a whole system and the bpard itself isn’t enough to drive innovation.

Here’s a list of 10 principles you should keep in mind.

Visualize the Workflow: the visual board has the aim to represent the workflow stages, making it easier to see work in progress (see next point) and identify bottlenecks.

Limit Work in Progress (WIP): set limits on the amount of work that can be in progress at each stage to ensure focus and prevent overload. In other words: do not start too many things at once.

Manage Flow: continuously monitor and optimize the flow of work through the system, for instance removing the bottlenecks you previously indentified.

Make Process Policies Explicit: clearly define and communicate the rules and policies that govern the workflow to ensure everyone understands and follows them. If nobody follows what you’re saying, you might be the problem.

Implement Feedback Loops: use regular feedback mechanisms, such as stand-up meetings and reviews, to gather input and make necessary adjustments.

Improve Collaboratively, Evolve Experimentally: foster a culture of continuous improvement through collaboration and small, incremental changes based on empirical evidence. Standards are awesome as long as they don’t prevent us from exploring new things.

Focus on Customer Needs and Expectations: prioritize work based on customer value and requirements, ensuring that the most important tasks are completed first.

Measure and Optimize for Efficiency: use metrics to measure performance and identify areas for improvement. Data gathering is crucial for the continuous business justification of improvement.

Empower the Team: encourage team members to take ownership of their work and make decisions that improve the workflow and outcomes. Note: this calls for the right company culture, or it will be rejected.

Minimize Waste: identify and eliminate activities that do not add value to the customer, gold-plating and redundancies.

How about you? Do you work in Kanban, or do you simply use a kanban board?

#MerfolkMonday: the Underwater Bells of Whitby Abbey

A story in Whitby — a seaside town located on the North Yorkshire coast in the North East of England, between Scarborough and Redcar — tells of the day Henry VIII decided to send his men to wreck the local Abbey (yeah, it’s the Dracula one, I talked about it here). The King’s men stripped the Abbey of its riches, and this included the bells, as the King wanted them transported to London either to sell them or to melt them and forge new cannons for his warships.

The people of Whitby didn’t take it well.

The King’s men carefully carried the bells down the 199 Abbey steps, while people in town were throwing silent curses at them, loaded them on the ship bound for London and… the ship sank. Some people say it was a favour from the local merfolk, though I find it improbable since the other legend connecting Whitby to mermaids is one where two exhausted mermaids are captured after a storm, held captive and almost stoned to death.
Anyway, the ship sank with the bells and it’s said that you can still hear the ringing of the Whitby Abbey bells underneath the waves just off the Black Nab in the North Sea. Whether hearing them is a good or a bad omen I couldn’t tell you, but one can easily guess.

Some resources on LEGO Serious Play

As my workshop with the Women in BIM group and my class at Autodesk University in San Diego approach, many of you asked me to provide additional resources on the LEGO Serious Play methodology, so here’s a handful of them.

Foundations and State of the Artthe LEGO SERIOUS PLAY Open Source Guide Issued by LEGO Group (uploaded on Slideshare by Marko Rillo);Johan Roos (one olf the inventors of the method), Thinking from Within: A Hands-on Strategy Practice (2006)Sean Blair and Marko Rillo, Serious Work: How to Facilitate Meetings and Workshops Using the LEGO SERIOUS PLAY Method (2016) and Building a Better Business Using the Lego Serious Play Method (2014);the methodology explained by the Seriousplay Community;Matt Statler and Johan Roos, Everyday Strategic Preparedness (2007);Stuart Brown and Christopher Vaughan, Play: How It Shapes the Brain, Opens the Imagination, and Invigorates the Soul (2009);Stefano Tardini, Elisabetta Frick, Lorenzo Cantoni, White Paper on LEGO ® SERIOUS PLAY A state of the art of its applications in Europe on ResearchGate or here.

Facilitation TechniquesSean Blair, MASTERING the LEGO® Serious Play® method: 44 facilitation techniques on serious.global;Jacquie Lloyd Smith and Denise Meyerson, Strategic Play: The Creative Facilitator’s Guide #2: What the Duck! (2017);Loizos Heracleous and Claus Jacobs, Crafting Strategy: Embodied Metaphors in Practice (2011);David Gauntlett, Creative Explorations: New Approaches to Identities and Audiences (2007) and Making is Connecting (2011);Dave Gray, Sunni Brown, and James Macanufo, Gamestorming (2010) including over 80 games to help facilitate creative thinking and problem-solving.

Sector ApplicationsJulia Trebbin, Gaining Insights Through LEGO® SERIOUS PLAY® as a Brand Research Tool – LET IT CLICK WITH THE BRICK (2016) on LeanSP;Mads Bab and Ilona Boniwell, LEGO Serious Play for Positive Psychology (here);Caitlin Ferreira, Unlocking Student Creativity with LEGO® Serious Play: a Case Study from the Graduate Marketing Classroom (2024) published in the Journal of Marketing Education;Sean McCusker, Lego® Serious PlayTM: Thinking about Teaching and Learning (2014) reclaiming LSP for the educational domain (here).

Do you have more books to suggest? Comment below.