Rails Design - Modules with Boundaries and Injection Recently, a colleague Severin Räz suggested that we could be using module to create namespaces (to organize our code with high cohesion) and private_constant to enforce API boundaries (enforce low coupling).

Intro This article was inspired by [Julián Pinzón] and his talk at Ruby Australia 2023 All you need is Rails (Engines): Compartmentalising your Monolith. Its widely known that Engines are a power way to create a full ‘sub-rails application’.

Rails with Strong Boundaries between the Modules This experiment was inspired from an internal Tech Talk at Garaio REM by a colleague Severin Räz. He suggested that we could be using module to create namespaces (to organize our code with high cohesion) and private_constant to enforce API boundaries (enforce low coupling).

Restricting access to pages - for various users

Restricting access to pages - for both static and live pages

Quick features and sample usage of Phoenix and LiveView (with minimal explanations)

Motivation It is helpful to be able to configure your cli-tasks to work the same as lucky. In lucky you can configure the application’s behavior / settings in the config folder.

Exploring how to upgrade crystal projects (Lucky)

A simple but reasonably comprehensive overview of Lucky features - with the context of a ‘mini-project’

Generally people remember stories and much of children’s play involves taking on a persona. Conveniently, many courses involve multiple units, thus allowing multiple rounds of “play” and “identity” for students. The stories they make need to be thoughtful and challenging enough that students successfully complete the “Hero’s Journey,” with a healthy sense of being uplifted by the challenges encountered on the way. This is quite doable with a thoughtful implementation of an Agile Kickoff process. One of my favorite books on this subject is in the resources below.

Helpful feedback has little to do with what the teacher thinks, for example the pre-supposition the teacher makes about the outcomes of student projects, and is much more about developing an openness to what actually works and what others like, without an absolute truth either stated or implied by the curriculum. Let the students decide what to do by emphasizing these two types of feedback: - Natural feedback - Collaborative feedback

Frequent, even daily, mini-reflections lead to adaptable students and curriculums. Ideally, guide the students to where they are comfortable to self-reflect with you. This of course means guiding the kids to where they have the confidence and insight to self-reflect and self-correct instead of relying (or even fearing) external assessment and correction.

Options - choosing what’s best for you

Learn to set-up mail catcher for safe email testing with an introduction to Docker

step 0: buy a domain name For these instructions use the (Namecheap)[https://www.namecheap.com/] service to buy your Domain. step 1: point your domain name at: username.github.io (optional) This takes quite a steps and disables https (more steps follow to renable ssl).

As part of the ECIS Leadership Conference - April 2020, Guide and Lead Managing Partner, Tim Logan gives an overview of the importance of agility in building schools as life-affirming 21st century organisations.

As part of the ECIS Leadership Conference - April 2020, Guide and Lead Managing Partner, Tim Logan gives an overview of the importance of agility in building schools as life-affirming 21st century organisations.

Four steps for students to give and get safe and effective feedback.