Quiz · 6 questions
🔧 Parameterize, Never Fork
How one implementation serves apps that disagree
Level 0Loose Parts
0 XP0/48 lessons0/13 achievements
0/100 XP to next level100 XP to go0% complete
Quiz
01What is a shim, in this architecture?
02The shared schema builders take the subject column name as a parameter and emit CREATE TABLE IF NOT EXISTS. Why does that combination matter?
03Why does the rule 'no shared module imports another shared module' exist?
04The first queue module allowed to import another carries a written reason. What does that record actually buy?
05An app needed to put an entire interactive offline surface where every other app puts one sentence. What did that require of the shared component?
06The written list of exceptions to the queue kernel's no-import rule said one edge while the code had grown four (five today), yet no consumer broke. What kept the field safe?
Comments 0
🔔 Reply notifications (sign in)Sign in — Please sign in to comment.
No comments yet — be the first.