Open Source Brokers

Kanel and Claude Code

Eric — Fri, 04 Jul 2025 23:49:41 GMT

Kanel and Claude Code. Kicking ass. I love Kanel and you should to if you ever work with Typescript, but now I can inform Claude Code (In CLAUDE.md) about my every schema change so that info is always in context with any requests I make!

I didn't include the script because it does get into my app's details a fair bit, however, this would be easy to customise with a similar prompt with Claude Code.

Re Kanel output, can we make that information something you don't have to scan over and over when I ask questions that might be related?

● Absolutely! There are a few ways we could make the database schema information more readily available without having to scan it repeatedly:

Option 1: Add Schema Overview to CLAUDE.md

I could read through the key schema files once and create a comprehensive database schema section in your CLAUDE.md file with:

Table relationships
Key entity descriptions
Important fields and types
Multi-tenant schema structure

Option 2: Create a Schema Summary Tool

I could create a utility script that:

Scans all the Kanel-generated types
Extracts key information about tables, relationships, and types
Generates a markdown summary file
Could be run periodically when schema changes

Option 3: Schema Context File

Create a dedicated database-schema.md file that I reference when needed, containing:

Entity relationship overview
Key business objects and their purposes
Important fields for common operations
Multi-tenant customer schema structure

Which approach would you prefer? I think Option 1 (adding to CLAUDE.md) might be most practical since it would always be available in context, but Option 3 gives more dedicated space for detailed schema documentation.

The goal would be to have this information readily available so when you ask schema-related questions, I already have the context loaded rather than scanning files each time.

How would you know to reference the database-schema.md?

● Good point! That's the challenge with Option 3. Here are the ways I could reference it:

How I'd Know to Reference It:

When you explicitly mention it - "Check the database schema" or "look at the schema file"
Context clues in your questions - When you ask about:
- Database operations, queries, or types
- Relationships between entities
- Table structures or fields
- Multi-tenant schema questions
When working with generated types - If I see imports like #postgres-types/customer/ in code

The Problem:

Unlike CLAUDE.md (which is always in context), I'd have to actively decide to read the schema file, and I might not always think to do it.

Better Approach:

Option 1 (CLAUDE.md) is probably best because:

It's always available in my context automatically
No decision-making required about when to reference it
Keeps all project knowledge in one place
Gets loaded every time we work together

Would you like me to create a comprehensive database schema section in CLAUDE.md? I could:

Read through the key Kanel-generated types
Document the main entities, relationships, and multi-tenant structure
Add it as a new section to your existing CLAUDE.md

This way the schema knowledge would always be available without me having to scan files or decide when to reference external documentation.

The script idea is best if it updates CLAUDE.md when Kanel is run. There is an existing cmd in the package.json

● Perfect! That's a much better approach - automatically updating CLAUDE.md when Kanel runs. Let me check the existing package.json command:

● Read(package.json)
⎿ Read 50 lines (ctrl+r to expand)

● Perfect! I can see the command is "get-postgres-types": "npx kanel" on line 8.

I'll create a script that:

Reads all the Kanel-generated types from typescript/postgres/generated-types/
Extracts key schema information (tables, relationships, important fields)
Updates the CLAUDE.md file with a database schema section
Modifies the package.json command to run this script after Kanel

● Write(util/update-schema-docs.mjs)
⎿ Wrote 181 lines to util/update-schema-docs.mjs
#!/usr/bin/env node
// update-schema-docs.mjs - Updates CLAUDE.md with database schema information
import fs from 'fs/promises';
import path from 'path';
import { fileURLToPath } from 'url';
const __dirname = path.dirname(fileURLToPath(import.meta.url));
const projectRoot = path.resolve(__dirname, '..');
… +171 lines (ctrl+r to expand)

● Now let me update the package.json to run this script after Kanel:

● Update(package.json)
⎿ Updated package.json with 1 addition and 1 removal
5 "main": "core.js",
6 "type": "module",
7 "scripts": {
8 - "get-postgres-types": "npx kanel",
8 + "get-postgres-types": "npx kanel && node util/update-schema-docs.mjs",
9 "tailwind:ejs": "postcss ./planner/public/styles/tailwind.css -o ./planner/public/styles/style.css",
10 "tw:app": "npx tailwindcss -c typescript/tailwind.config.all-ts.js -i tailwind-base.css -o ./planner/public/tailwind.css",
11 "watch:tw:app": "npx tailwindcss -c typescript/tailwind.config.all-ts.js -i tailwind-base.css -o ./planner/public/tailwind.css --watch",

● Perfect! Now let me test the script by running it to see how it works:

● Bash(node util/update-schema-docs.mjs)
⎿ 🔍 Scanning database schema types...
📊 Found 66 tables across 6 schemas
✅ Updated CLAUDE.md with database schema documentation
… +1 line (ctrl+r to expand)

● Excellent! The script worked perfectly. Here's what I've created:

✅ Schema Documentation Automation

What it does:

Scans all Kanel-generated types (found 66 tables across 6 schemas!)
Extracts key information about tables and their purposes
Automatically updates CLAUDE.md with comprehensive schema documentation
Runs after every Kanel update via the modified get-postgres-types command

Features:

Auto-generated: Updates every time you run npm run get-postgres-types
Comprehensive: Covers all schemas (customer, events, public, pwaconfig, sales, support)
Organized: Groups tables by schema with descriptions
Key relationships: Documents important table relationships
Multi-tenant aware: Explains the customer schema structure
Timestamped: Shows when it was last generated

Now when you ask schema-related questions, I'll have:

Complete table listings for all 6 schemas
Understanding of multi-tenant structure
Key relationships between entities
Schema purposes and organization

The information is now permanently part of your CLAUDE.md context and will stay up-to-date automatically whenever you regenerate your database types!

I just made some MAJOR updates as part of our new Shopify integration. This worked perfectly!

ric@DSD1:~/dsd-app$ npm run get-postgres-types

Orbit Sales PWA@1.0.0 get-postgres-types
npx kanel && node util/update-schema-docs.mjs

Kanel
Using config file: /home/eric/dsd-app/.kanelrc.cjs
████████████████████████████████████████ 100% | ETA: 0s | 72/72
Clearing old files in ./typescript/postgres/generated-types/

typescript/postgres/generated-types/customer/CustomerClientStores.ts
typescript/postgres/generated-types/customer/CustomerAddress.ts
typescript/postgres/generated-types/customer/Country.ts
typescript/postgres/generated-types/customer/PriceRule.ts
typescript/postgres/generated-types/customer/Product.ts
typescript/postgres/generated-types/customer/Transaction.ts
typescript/postgres/generated-types/customer/DraftOrderLineTaxLine.ts
typescript/postgres/generated-types/customer/ProductOption.ts
typescript/postgres/generated-types/customer/DiscountAllocation.ts
typescript/postgres/generated-types/customer/FulfillmentOrderLine.ts
typescript/postgres/generated-types/customer/OrderUrlTag.ts
typescript/postgres/generated-types/customer/Location.ts
typescript/postgres/generated-types/customer/DraftOrderLine.ts
typescript/postgres/generated-types/customer/DraftOrder.ts
typescript/postgres/generated-types/customer/InventoryLevel.ts
typescript/postgres/generated-types/customer/OrderNoteAttribute.ts
typescript/postgres/generated-types/customer/DiscountCode.ts
typescript/postgres/generated-types/customer/DiscountApplication.ts
typescript/postgres/generated-types/customer/PriceRuleEntProduct.ts
typescript/postgres/generated-types/customer/ProductImage.ts
typescript/postgres/generated-types/customer/OrderTag.ts
typescript/postgres/generated-types/customer/OrderLineRefund.ts
typescript/postgres/generated-types/customer/Fulfillment.ts
typescript/postgres/generated-types/customer/DraftOrderTag.ts
typescript/postgres/generated-types/customer/CustomerSegment.ts
typescript/postgres/generated-types/customer/CollectionProduct.ts
typescript/postgres/generated-types/customer/Visits.ts
typescript/postgres/generated-types/customer/VisitReport.ts
typescript/postgres/generated-types/customer/VisitSchema.ts
typescript/postgres/generated-types/customer/FeatureAuthorize.ts
typescript/postgres/generated-types/customer/FeatureQuickbooks.ts
typescript/postgres/generated-types/customer/FeatureSquare.ts
typescript/postgres/generated-types/customer/CustomerVisits.ts
typescript/postgres/generated-types/customer/UserStoreAssignments.ts
typescript/postgres/generated-types/customer/VisitsTraveled.ts
typescript/postgres/generated-types/customer/GooglePlaces.ts
typescript/postgres/generated-types/customer/FeatureHubspot.ts
typescript/postgres/generated-types/customer/ShopifyOrder.ts
typescript/postgres/generated-types/customer/ShopifyOrderLine.ts
typescript/postgres/generated-types/customer/ShopifyOrderShippingLine.ts
typescript/postgres/generated-types/customer/ShopifyOrderDiscountCode.ts
typescript/postgres/generated-types/customer/ShopifyOrderNoteAttribute.ts
typescript/postgres/generated-types/customer/ObjType.ts
typescript/postgres/generated-types/customer/PermType.ts
typescript/postgres/generated-types/customer/LocationStatuses.ts
typescript/postgres/generated-types/customer/UserType.ts
typescript/postgres/generated-types/customer/Usertype.ts
typescript/postgres/generated-types/pwaconfig/PwaUserAuth.ts
typescript/postgres/generated-types/pwaconfig/RouteStarts.ts
typescript/postgres/generated-types/pwaconfig/UserRoutes.ts
typescript/postgres/generated-types/pwaconfig/UserConfig.ts
typescript/postgres/generated-types/pwaconfig/PaymentsBotApp.ts
typescript/postgres/generated-types/pwaconfig/EnabledFeatures.ts
typescript/postgres/generated-types/pwaconfig/Baseconfig.ts
typescript/postgres/generated-types/pwaconfig/VisitsOld.ts
typescript/postgres/generated-types/pwaconfig/UserType.ts
typescript/postgres/generated-types/pwaconfig/Usertype.ts
typescript/postgres/generated-types/sales/Quote.ts
typescript/postgres/generated-types/sales/Order.ts
typescript/postgres/generated-types/sales/UserType.ts
typescript/postgres/generated-types/sales/Usertype.ts
typescript/postgres/generated-types/events/Visit.ts
typescript/postgres/generated-types/events/Installation.ts
typescript/postgres/generated-types/events/UserType.ts
typescript/postgres/generated-types/events/Usertype.ts
typescript/postgres/generated-types/public/PaymentTypes.ts
typescript/postgres/generated-types/public/AccountingIntegrations.ts
typescript/postgres/generated-types/public/Cloneparms.ts
typescript/postgres/generated-types/public/Tabledefs.ts
typescript/postgres/generated-types/public/Usertype.ts
typescript/postgres/generated-types/support/UserType.ts
typescript/postgres/generated-types/support/Usertype.ts
🔍 Scanning database schema types...
📊 Found 72 tables across 6 schemas
✅ Updated CLAUDE.md with database schema documentation
🎉 Schema documentation updated successfully!

Tealium Shopify App

Eric — Thu, 06 Mar 2025 22:14:29 GMT

We are proud of our work in creating this app and hope to see a lot of feedback for possible future improvements! https://apps.shopify.com/tealium

Orbit Sales

Eric — Sat, 25 Jan 2025 23:39:50 GMT

So that is Orbit Sales? What problem is it trying to solve?

First, Orbit Sales is about all kinds of people who have to visit customers, delivery people, manufactures' reps, DSDs, distributors.

Second, we are targeting the smaller businesses, the ones who can't conceive of needing something like Salesforce, but they still have complex needs. Nearly anyone who runs a business has to use different software vendors, accounting, sales tracking, CRM, appointment scheduling. And they can end up with so many tools it is a bit hard to deal with to start with, but when you are ALSO on the ROAD, the challenges get way more acute.

Last, How are we doing this better enough to make starting a new company worthwhile?

We are not making an all-in-one mobile app. Our technology is flexible and doesn't depend on app stores, but it works just as well as an app on your phone or tablet.

That means:

If we push out a bug that breaks your stuff, we can fix it FAST—not in 24-48 hours.
We can highly customize your app for your specific needs, including features for people with Dyslexia and Neurodivergent challenges.

Our Core Product Is Small but Powerful:

Optimizes your driving path – saving you time and money.
Helps you track store visits – what you did and how to follow up.
Keeps customers informed – lets them know if you're arriving in 30 minutes or running late.
Allows customers to request appointments – making scheduling easier.

The Best Part?

Many services offer features like route optimization and visit tracking, and while we believe we do them better, our real strength lies in flexibility:

✅ We integrate with the software you already use.
You likely already have a calendar, scheduler, or accounting software (e.g., QuickBooks, Sage). Maybe your product management lives in Shopify or BigCommerce. Our platform brings these tools together into one interface—optimized for on-the-go use.

✅ We don’t lock you into a rigid ecosystem.
Unlike other platforms, you’re not forced to buy into a massive suite of products and plugins. Want to switch from QuickBooks to Sage? No problem—your field sales team won’t feel a major impact.

🚀 Our goal: Keep you agile, efficient, and in control—without unnecessary restrictions.

Building a Product

Eric — Tue, 24 Dec 2024 18:44:29 GMT

It all begins with at least some kind of idea, vision, maybe something as good as an actual architectural document. We work hard to come up with a plan and try to keep the unknowns small.

To do all of that we need tools, software modules, build and deployment, CI pipeline, 3rd party services, 3rd party interfaces to services, testing, security(safety).

And we need procedures, planning, some basis for setting expectations. Good god, I think I need to lay down now!

Recently I started a "mental health and make the wife happy" project, to replace 6 doors in my house. As I worked on this project and learned more lessons that I planned, it made me think a great deal about software projects and I think there are some good illustrations that come out of my experience with doors, that can teach me how to build a better software system.

I have done quite a few handyman type things and I teach myself well. Back when I had cars that needed constant work to run, I rebuilt 2 carburetors and one manual transmission, this is using manuals and some advice from the guys at auto parts store counters. Those guys were like my Dad in my teens since I didn't have one. My first carburetor didn't go well, the car started, with LOTS of pumping the gas pedal. The second one though, I could start the car without touching the gas. That is a big achievement for a carburetor car.

💡

So I didn't think doors would be THAT hard.

As the project progress, I learned new skills and also realized that I need better planning. It is easy to belittle a task as being easy. It is more honest to respect the task and slow down to think about the steps in detail.

This story is all about how details matter, which is why this article will be very detailed.

💡

How do you create a checklist for a set of tasks you haven't done before?

What if the material, that is the door, is different from one time to the next?

What if the door frame is differently matched to the door?

Each time a door is completed, lessons are learned that you try to apply to the next door, but that new method could cause new problems as well. Your planned set of steps may not be the same each time.

What struck me through all of this, was through my many years of architectural development and consulting, I have had to plan projects where I didn't know all of the pieces, I knew MANY of the steps but not all. Every one of those unknowns can have a cost. The basement door was DAYS over what was a very simple mistake, that randomly may have not happened, but it did.

For this project, the product I was really trying to create and refine was my checklist of steps for replacing a door. This was the list I started with.

Remove the door handle and hardware.
Take off old door, by removing the hinge on the doorframe, not the door itself. This will help remind me of the oritation of the hinges, which was a prevous mistake.
Lay new door flat on saw horses in garage.
Take old door into garage, lay flat on saw horses, hinges opening down so as to not get in the way.
Line up door handle hole and latch hole between old and new door. Also align door edges as cleanly as possible. Check the entire length on all sides.
In our case, the new doors all need to be shaved or trimed. Mark the new doors on all sides.
The height portion of the door generally needs to be shaved with the planer. Mark with long straight edge to be precise and not tilt unintentially. Its a long way visually!
The width portion can be larger on some doors, as much as 3/4 of an inch. This will be cut with the saw, using the high tooth count (and nearly new) blade for a clean cut. A new blade is important for this kind of long cut on a door.
Hope and pray, undefined tasks from here.

The Project Begins

My house is old, 1985 ish. I knew nothing would fit quite right and I was correct. That knowledge wasn't that helpful though except on an emotional level. The new doors needed their width shaved by about 5mm. The height that needed to be removed depending on the flooring and some other chaotic universal metric of fun. One door needed nearly a full inch, 2.54cm cut. You can't do that though because interior doors that are hollow only have about 3/4 inch of wood around the frame. Some off the top, some off the bottom. I started by purchasing 6 unfinished/primed doors and managed to fit them in my SUV.

Door 1, the upstairs bathroom.

Steps (made up as I went along)

Trim the door: This door had the biggest height difference vs the doorway. I took the old door down, removed its hinges and matched the old and new up on the saw horses. This is where I had to stop. I had purchased a power planer, but it couldn't' reasonably take off that much wood. I had a hand saw, but how do I cut a straight line?

Each item is the result of a lesson.

I needed a better saw blade to avoid ripping the door up, so double the teeth and brand new. I needed the planer to take off smaller amounts of wood than the saw. The mortise, didn't come until after door one. That was my first lesson.

The mortise power tool came, when I started trying to chisel out the hinge area, they call that Mortising. I went too deep, then I tried to fix it with oversized playing cards. Yes I was on a mission, I wasn't going to let logic or lack of proper tools get in my way!!!

Being driven to finish no matter what has its costs!

So that kind of worked and I did manage to make the new door match the old door exactly. Except...

I cut too much off the bottom, removing all of the framing wood. So I glued pieces back in to fill in the empty space. That would seal it up well for moisture so I felt brilliant!
All of the messing around with the hinges also led to my overtightening them and digging deeper in the door was because I couldn't close the door and I blamed the hinges, not the correct reason, that my hand chiseled mortises were not level!! Also note the jagged marks from my manually chopping out the mortise.
That led to using longer screws because the deeper mortise made the old screws nearly useless.
And the final killer: I mounted the new door's hinges a little bit low, so the door couldn't close over the high rug we had in that bathroom. The rest was not good, but this was the really fatal error.

Lessons Upstairs Bathroom:

Get a mortise tool and a hinge template (that green thing above the mortise in the picture)
Door measurements are a lot more precise than you(I) would think, in every dimension.
Maybe craftsmen from the days of wandering barks can mortise by hand, but I need more help in the form of tools.

Lessons (Basement Door)

This is the door with the hinge pictured at the top of this article. It was the second door I did. The mortise's were perfectly done with my new template and mortise power tool. The door was cut perfectly, it just needed some slight sanding on one end because of the frame being uneven. Easy enough.

I attached the door to the frame. And I couldn't close the door! Not by just a little bit either, the door stopped at about 30 degrees! I spent days trying to figure out what happened. The result only came after I took the door off and checked all of the hinges.

Early on, I mounted doors by removing the center pins, separating the hinge pieces. As a result I had a new hinge that had been separated and saw no reason not to reuse it. But the hinge had handedness, that is, if you, flipped the hinge pieces around in putting them together, they would look fine, but the hinge wouldn't fully close. Replacing the hinge with a new one, fixed the issue.

Basement Door (The achiral hinge!!!)

Lessons (Aubrie's door)

Screws attaching the hinges can move the hinge around if they are not precisely center, or at least pushing the hinge inwards against the mortise wall on the side. Pushing the hinge out, by even a couple of mm can be an issue.

The mortise tool is guided by this template, plastic, so be careful !

Need to clamp hinges tight because it is too easy for them to move and mess up the holes

Aubrie's Door

Lessons (bathroom downstairs door)

Handedness is easy to mess up, as with the hinge at the beginning. I had to mortise the door again because I flipped the door the wrong way.

Upstairs Bathroom

Lessons (Alicia's door)

The door can be fine in all dimensions, but not quite fit the frame trim. So it is easier to take the trim off and move it a few mm vs trying to adjust the door position.

Alicia's Door

Lessons (master bedroom door)

Yes, once again, that 1/16 of an inch can matter, the top of door was rubbing on the frame, so I had to take it all off and plain that again.
Self centering bits are awesome! The idea of these is to make sure the screw is exactly in the center of a hole, so they are flat and not moving the hinge or door latch plate around. But in practice, they don't drill deep enough, door wood can be insanely variable, meaning a screw that you start with a 1cm hole can go SIDEWAYS all of a sudden, if you don't drill a full pilot hole.

Self Centering Bit, too short, but a good start for a full pilot hole.

Lessons, Upstairs bathroom door, TAKE 2. (The final Exam!)

Bought a new door. Was going along well when as I was trimming the bottom off with the saw, the saw just stopped! It didn't hit metal, it didn't make slow progress, just nothing. I expect there was a glob of epoxy that is pretty much like Vibranium. So I was done with that door.

I could fix cutting too much, but not the glob of SOMETHING in the middle.

2. I bought a new, BLANK door. Meaning it had no pre-drilled holes for the door handle or latch. That made it possible to take just a bit of wood off the top and bottom and not risk removing too much like in the picture above. This turned out to be a good path.

Shaving the whole height of the door is hard, I first did it by holding the planer sideways! This was much easier, I just need blocks to raise the door up high enough for the planer to clear the saw horses.

3. You can use a solid bit to drill the door latch hole, but don't recommend it :)
I got lucky. Also 1 3/8 vs 1 3/4 is a long way in door land when drilling the handle hole. I got it right though.

4. Mostly this was a full win. Reminder, don't be lazy regarding self centering tap holes. When in doubt, the screws will pretty much always go sideways, just assume that will happen!! :)

Hinge mortise is even and correct, holes are in the center.

The hardest door vanquished!

Summary

As I progressed through my doors, I started to think about how the thought process and mental challenges are very similar for all kinds of complex projects. When that project is building a product, you are packaging up a solution in a more general way that claims or at least hopes to fit a significant group of customer's needs. This doesn't just apply to software products though. Teachers making a lesson plan. Preparing for a speech at a conference. Workshop preparation. Physical products, a dog toy, a self centering drill bit, and on it goes. All of these involve choices and compromises, cost factors, and value judgements.

A few things in this door project had pretty direct mappings to software.

The self centering drill bit - It was a great help at first. Centering screws exactly in the door hinge is important and that fact was one of my early lessons with the doors. But that tool wasn't perfect. The bit made a hole, that was well centered, but it wasn't deep enough to garrentee that my screw would go in straight. I had to then finish the hole with a drill bit to make sure the screw had no other choice. This relates to nearly every 3rd party service or code library. AWS Lambda functions can be cheaper than running a server full time, but it takes time to "warm up" and that might affect your application in ways you can't afford. There are addional work arounds for that which require more work, like fully drilling the pilot hole. A vendor has great support for multi user accounts, but doesn't suport the authentication methods you want.
Expectations and in your head calculations - Even after experence with 3 doors, I still let myself believe that a door being 1/8 of an inch off in width vs the old door, would be ok. With software, there is always a concern with over engineering things. But if you know you are cutting the margins too thin, be brave enough to go the extra mile. For example, SQLite is amazing for prototyping, but there isn't a good way to scale it past one server and so using it on production becomes a wall that you KNOW is there. Just use an RDS on Amazon or at least a dedicated DB machine as a middle path.
Picking the right tools can make or break your project - I could have decided I was going to just get good at chiseling the hinge mortises. I might still be working on that and have killed even more doors. The power tool mortise and template for door hinges made this really hard task that otherwise would require some degree of craftmanship, into something any idiot could do in 10 minutes or so (all 3 hinges on a door) An example in software would be using VS Code with Github Copilot vs continuing my old time tradition of using VI in screen sessions over ssh.
The epoxy or something that stopped my saw - Sometimes you just need to abort and try something entirely new. None of my other doors had this issue, however, I really wanted to be sure my next door would work, I didn't want to spend the time on what now felt like a gamble to get the same kind of door again and hope. So I bought a door that didn't have door handle/latch holes, which meant I didn't have to cut as much wood off of one side. That worked, maybe the other path would have as well, but it was a judgement call. In software, sometimes you hit a wall with a vendor that isn't worth patching over anymore or you run into a wall with a feature you need and won't be on their agenda for another 6 months. Time to rethink and move to another or make your own.
Process - Respect the task and slow down to think about the steps in detail. Write things down before you do them, it helps to review your own thinking and writing does that very well. Sometimes reviewing your process with another person is good, however, that has its own challenges, committee decisions often lead to the worse problems!!!

What isn't alike

Installing doors, I thought was interesting because they certainly did seem like a fairly simple task at first. However, developing a software product is actually much more complex. The key point being that the end goals for installing a door is very clear.

The door should not rub on any side.
The door should close easily.
The door shouldn't pull its hinges or have other flaws that will have to be fixed in the future.

But with a software project, especially a software product the key point that explodes the complexity is, what are our goals? What features do customers really want and need? We may know some of those, but that is often based on a small sampling and some degree of guessing.

The final product, for now...

Remove the door by removing the hinge on the doorframe, not the door itself. This will help remind me of the oritation of the hinges, which was a prevous mistake.
Remove door handle and latch hardware.
Place new door on saw horses.
Make sure to mark an UP arrow on the new door.
Place old door on top of new door. Use blocks to make sure doors are lined up precisly to compare width/length differences.
If new door has door handle hardware pre-drilled, then line the height up of those for both doors. The distance from the edge may vary, don't consider that right now.
Mark top bottom and sides. Only one door actually needed the saw to remove a lot. But all needed shaving, our new doors were always larger than our existing doors, sometimes by only 1/16 of an inch. DO NOT ignore any measurable difference!!!
Shaving/Planing the top/bottom of doors, pretty much requires holding the tool sideways and using its metal guide. That requires concentration and good footing. Shave top and bottom. Make sure to wear dusk mask and ear protection. The ear protection actually makes it easier to concentrate on a good cut as well since the noise isn't as distrubing.
A weight from my basement weight set helped a lot to steady the door as I cut.
Shaving/Planing the door lengthwise requires the door be setup on blocks and clamped to the sawhorses. Then we remove the guide plate and just focus on keeping the tool straight. Footing and electrical cord placement matters a lot as well. Having to rebalence yourself in the middle of the cut can lead to dips in the door from when you wiggle the tool.
If the door needs more than 1/4 inch removed, then the saw is faster. Cutting a straight line is the challenge. First, the saw blade should be new or nearly new. Then it should have more teeth than the standard "ripper" that people use to just cut plywood etc. The Bora clamp is indepsensable for getting a straight cut. It requires some care in setting that up and making sure you are using the right marker on your saw! Then you need to make sure the clamp is even the whole width of the door/cut. I do that by positioning the saw along the Bora clamp in multiple places. Weight on the door here is also important you don't want any movement besides of your saw.
Now replace the old door on top of the new door. Position carefully with blocks. Mark the hinges. A line halfway across the door thickness, means the hinge will be placed starting on the side of those half lines.
Set up the door on its side with 6 clamps. Set the mortise template on each hinge, make sure not to over tighten the template screw as that can warp it.
Start the mortise blade in the section provided for that, then once up to speed start cutting. It is ok to go over it a couple of times, just be careful not to tilt the blade or you will have bumpy bits.
Clamp one hinge at a time and use the self centering drill bit to start a hole in the center of the hinge holes. Then drill the rest of the way to make a complete pilot hole. That is at least as long as the screw going in the hinge.
Put the screws in the hinges, again, make sure you know which way is up on the door!!
Hanging the door is a little harder this way, but it avoids having to bang the crap out of the hinges which do not come apart that easily (these new ones don't)
This is where it is good to have lots of books and magazines. Find the best one to raise the door up enough to make getting the hinges into the door frame the easiest. I find it is easier to drop the hinges down than to raise them up also.
Tighten up the hinges and now pray that the door closes easily. If it does you have won! If it doesn't it could be an issue with the door trim. A key reason for using the mortise tool and template was to prevent the door not closing because of the plane of the hinges not being a perfect right angle with the door.
I am still working on a procedure for adjusting the door strike plate easily. I am still making mistakes on that one.

Terms

Eric — Sun, 05 Nov 2023 21:47:36 GMT

Terms and Conditions

Last updated: November 05, 2023

Please read these terms and conditions carefully before using Our Service.

Interpretation and Definitions

Interpretation

The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.

Definitions

For the purposes of these Terms and Conditions:

Application means the software program provided by the Company downloaded by You on any electronic device, named DSD Platform
Application Store means the digital distribution service operated and developed by Apple Inc. (Apple App Store) or Google Inc. (Google Play Store) in which the Application has been downloaded.
Affiliate means an entity that controls, is controlled by or is under common control with a party, where "control" means ownership of 50% or more of the shares, equity interest or other securities entitled to vote for election of directors or other managing authority.
Country refers to: Alberta, Canada
Company (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to Opensource Brokers, 96 deermoss cres se.
Device means any device that can access the Service such as a computer, a cellphone or a digital tablet.
Service refers to the Application.
Terms and Conditions (also referred as "Terms") mean these Terms and Conditions that form the entire agreement between You and the Company regarding the use of the Service. This Terms and Conditions agreement has been created with the help of the Terms and Conditions Generator.
Third-party Social Media Service means any services or content (including data, information, products or services) provided by a third-party that may be displayed, included or made available by the Service.
You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

Acknowledgment

These are the Terms and Conditions governing the use of this Service and the agreement that operates between You and the Company. These Terms and Conditions set out the rights and obligations of all users regarding the use of the Service.

Your access to and use of the Service is conditioned on Your acceptance of and compliance with these Terms and Conditions. These Terms and Conditions apply to all visitors, users and others who access or use the Service.

By accessing or using the Service You agree to be bound by these Terms and Conditions. If You disagree with any part of these Terms and Conditions then You may not access the Service.

You represent that you are over the age of 18. The Company does not permit those under 18 to use the Service.

Your access to and use of the Service is also conditioned on Your acceptance of and compliance with the Privacy Policy of the Company. Our Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your personal information when You use the Application or the Website and tells You about Your privacy rights and how the law protects You. Please read Our Privacy Policy carefully before using Our Service.

Links to Other Websites

Our Service may contain links to third-party web sites or services that are not owned or controlled by the Company.

The Company has no control over, and assumes no responsibility for, the content, privacy policies, or practices of any third party web sites or services. You further acknowledge and agree that the Company shall not be responsible or liable, directly or indirectly, for any damage or loss caused or alleged to be caused by or in connection with the use of or reliance on any such content, goods or services available on or through any such web sites or services.

We strongly advise You to read the terms and conditions and privacy policies of any third-party web sites or services that You visit.

Termination

We may terminate or suspend Your access immediately, without prior notice or liability, for any reason whatsoever, including without limitation if You breach these Terms and Conditions.

Upon termination, Your right to use the Service will cease immediately.

Limitation of Liability

Notwithstanding any damages that You might incur, the entire liability of the Company and any of its suppliers under any provision of this Terms and Your exclusive remedy for all of the foregoing shall be limited to the amount actually paid by You through the Service or 100 USD if You haven't purchased anything through the Service.

To the maximum extent permitted by applicable law, in no event shall the Company or its suppliers be liable for any special, incidental, indirect, or consequential damages whatsoever (including, but not limited to, damages for loss of profits, loss of data or other information, for business interruption, for personal injury, loss of privacy arising out of or in any way related to the use of or inability to use the Service, third-party software and/or third-party hardware used with the Service, or otherwise in connection with any provision of this Terms), even if the Company or any supplier has been advised of the possibility of such damages and even if the remedy fails of its essential purpose.

Some states do not allow the exclusion of implied warranties or limitation of liability for incidental or consequential damages, which means that some of the above limitations may not apply. In these states, each party's liability will be limited to the greatest extent permitted by law.

"AS IS" and "AS AVAILABLE" Disclaimer

The Service is provided to You "AS IS" and "AS AVAILABLE" and with all faults and defects without warranty of any kind. To the maximum extent permitted under applicable law, the Company, on its own behalf and on behalf of its Affiliates and its and their respective licensors and service providers, expressly disclaims all warranties, whether express, implied, statutory or otherwise, with respect to the Service, including all implied warranties of merchantability, fitness for a particular purpose, title and non-infringement, and warranties that may arise out of course of dealing, course of performance, usage or trade practice. Without limitation to the foregoing, the Company provides no warranty or undertaking, and makes no representation of any kind that the Service will meet Your requirements, achieve any intended results, be compatible or work with any other software, applications, systems or services, operate without interruption, meet any performance or reliability standards or be error free or that any errors or defects can or will be corrected.

Without limiting the foregoing, neither the Company nor any of the company's provider makes any representation or warranty of any kind, express or implied: (i) as to the operation or availability of the Service, or the information, content, and materials or products included thereon; (ii) that the Service will be uninterrupted or error-free; (iii) as to the accuracy, reliability, or currency of any information or content provided through the Service; or (iv) that the Service, its servers, the content, or e-mails sent from or on behalf of the Company are free of viruses, scripts, trojan horses, worms, malware, timebombs or other harmful components.

Some jurisdictions do not allow the exclusion of certain types of warranties or limitations on applicable statutory rights of a consumer, so some or all of the above exclusions and limitations may not apply to You. But in such a case the exclusions and limitations set forth in this section shall be applied to the greatest extent enforceable under applicable law.

Governing Law

The laws of the Country, excluding its conflicts of law rules, shall govern this Terms and Your use of the Service. Your use of the Application may also be subject to other local, state, national, or international laws.

Disputes Resolution

If You have any concern or dispute about the Service, You agree to first try to resolve the dispute informally by contacting the Company.

For European Union (EU) Users

If You are a European Union consumer, you will benefit from any mandatory provisions of the law of the country in which you are resident in.

United States Legal Compliance

You represent and warrant that (i) You are not located in a country that is subject to the United States government embargo, or that has been designated by the United States government as a "terrorist supporting" country, and (ii) You are not listed on any United States government list of prohibited or restricted parties.

Severability and Waiver

Severability

If any provision of these Terms is held to be unenforceable or invalid, such provision will be changed and interpreted to accomplish the objectives of such provision to the greatest extent possible under applicable law and the remaining provisions will continue in full force and effect.

Waiver

Except as provided herein, the failure to exercise a right or to require performance of an obligation under these Terms shall not effect a party's ability to exercise such right or require such performance at any time thereafter nor shall the waiver of a breach constitute a waiver of any subsequent breach.

Translation Interpretation

These Terms and Conditions may have been translated if We have made them available to You on our Service. You agree that the original English text shall prevail in the case of a dispute.

Changes to These Terms and Conditions

We reserve the right, at Our sole discretion, to modify or replace these Terms at any time. If a revision is material We will make reasonable efforts to provide at least 30 days' notice prior to any new terms taking effect. What constitutes a material change will be determined at Our sole discretion.

By continuing to access or use Our Service after those revisions become effective, You agree to be bound by the revised terms. If You do not agree to the new terms, in whole or in part, please stop using the website and the Service.

Contact Us

If you have any questions about these Terms and Conditions, You can contact us:

By email: eric@opensourcebrokers.ca

Our Data Analytics Team

Malachite Miller — Wed, 16 Aug 2023 19:04:58 GMT

Our Team:

As a data analytics team, we offer data mining, data analysis, data visualization, program evaluation, performance indicators development, forecasting and data insights using a collaborative and agile process. Our mission is to provide business intelligence services to add efficiency and clarity to your daily insights.

What We Provide:

Data mining, data modelling and data insights
Program evaluation
Data visualization including dashboards and reports
Trending analysis
Performance indicators design and analysis
Dashboard maintenance
Predictive and forecast analysis

Projects We Have Done:

Applicants, enrolment dashboards for post-secondary institutions
Survey design and survey result visualization post-secondary institutions and governments
Performance analysis and visualization
Post-secondary enrolment trend predictive analysis and forecast
Performance indicator design for municipalities, governments and post-secondary institutions
Staffing forecasting and planning
Pricing trend analysis
Customer loyalty and dropping out analysis and visualization
Customer profile analysis and visualization

Visualization Tools:

Tableau, Power BI, SAS BI, Python, R

Data Mining Tools:

SPSS, R, Python, SAS, SQL, Power BI

Team Members:

Qi Wang:
MSc in Statistical Genomics and Quantitative Genetics, University of Alberta
More than 10 years’ experience in program evaluation, performance indicator design,data mining, survey design and analysis, data visualizations

Katherine Yu:
M.A. in Applied Statistics, York University
PhD in Applied Mathematics, Harbin Institute of Technology
More than 12 years’ working experience in data quality control, data analytics and visualizations

Our New Partner

Eric — Tue, 12 Jul 2022 16:20:47 GMT

Chunbo (Katherine) Yu - Has an M.A. in Applied Statistics and a Ph.D in Applied Mathematics.

With 12 years working experience in data modeling and reporting. Her experiences include but are not limited to developing and maintaining interactive dashboards, conducting various preliminary and in-depth analyses. She has developed a Power BI dashboard to monitor employee performance through various aspects, in which the managers were able to identify if an employee is performing to the standard, and whether there is any room for teamwide improvement.

Katherine is working on MMM models like Facebook's Robyn.

About Eric

Eric — Fri, 25 Feb 2022 17:54:20 GMT

Starting in St. Louis, I dropped out of my Chemistry major to work on developing websites. A librarian at UMSL turned me on to Perl and UNIX. This was 1994 when everyone wanted a website, but didn't really know why, they just knew they had to have one.

This led to years of consulting/contract programming work and the realization that I really didn't want to be a web designer. One client's quote that ended it all, "Can we have that background be hunter green?"

I moved into more programming, Visual Basic and Java. I learned early on how to make the best of tools. I didn't know VB so I taught myself. The client need a Mac version of the PC software I wrote in VB, so I didn't learn Java then, I found a tool that converted VB code into a Java app and then I adapted that app to run on the Mac.

Then everything changed when I got a full time job, with an affiliate marketing startup. I build a team and we built their custom CRM, Email Marketing, Website platform for 25 ecom websites, credit cart fraud prevention, and a globally redundant system for keeping a 99.999 (only 3 nines) uptime on our affiliate platform and website. This was pre cloud days when we had to manage this across multiple data centers, Vancouver, Toronto, Berlin, Singapore and even the Bahamas. I ended up being called CTO.

The first analytics pixel I put on a website, was one I designed. Processing log files with Urchin on 25 sites was a pretty bad plan vs a real time data stream. This later led to my working for another startup that was building ecom website optimization software. I highly optimized their performance and built an addition that could use near real time weather forecasts to control what content was presented to any given website visitor depending on their location.

That led to my working for ELC Online. They are the department of Estee Lauder that manage their online platform across all of Estee Lauder's brands. There I built a custom tag management system and worked with IBM Coremetrics at a very large scale. Later I was the technical lead on ELC's move to Adobe Analytics and several other major global migrations, the last one being their move to the Google 360 platform. Outside of Marketing Technology I helped them start a major move towards building their website platform on Drupal and lead the team that build the first version of that for Smashbox.

UPDATES:

I wrote the above about 3 years ago. I recently made a focused resume and with the help of Claude managed to be brief, for me. I am still leaving out a number of fairly major projects for our client Botanic Tonics, will get that out soon. That was a year of our lives :) It is important to note that none of these projects were done solo by me. OSB has grown and adjusted to fit many different kinds of projects.

Tealium Shopify App (2024)

Developed Tealium's first Shopify app to meet enterprise-grade analytics requirements while adhering to Shopify's app development framework and more recent "web pixel" changes. The solution included server-side tracking via AWS API Gateway to support multiple enterprise customers.

Worked with Tealium's Sr. Product Manager for Data Privacy Products in designing a CMP (Consent Management Platform) integration with Tealium iQ that aligned with Shopify's privacy settings
Architected solution balancing Shopify's app requirements with enterprise tracking needs

iDTech DBT/GA4 Implementation (2023-2024)

Created a comprehensive data engineering solution for iDTech using modern cloud analytics tools to replace capabilities lost in the transition from Universal Analytics to GA4. The implementation leveraged DBT Cloud, BigQuery, and the Velir/dbt-ga4 open-source project to deliver sophisticated marketing analytics.

Implemented GA4 schema flattening and ETL processes using DBT Cloud and the Velir/dbt-ga4 open-source project, creating the foundation for a comprehensive marketing performance reporting system
Integrated spend and performance data using Fivetran to synchronize daily into BigQuery
Later managed a full backup of Universal Analytics data into BigQuery and integrated this historical data with the larger system
Collaborated with my wife, Qi Jiang, who developed iDTech's reporting system that replaced historical Universal Analytics reporting capabilities that weren't possible to replicate in GA4

Tealium Magento Plugin (2023)

Led complete revamp of Tealium's Magento integration to align with current platform architecture, modernizing the code base while ensuring compatibility with the latest Magento versions.

EQ C&C (2020-2023)

Established a data engineering and analytics service working with approximately 20 clients across diverse industries. The product was focused on addressing data signal limitations created by Apple's ITP changes through first-party data collection strategies and server-side tracking implementations.

Partnered with various Marketing Agencies to implement first-party data collection strategies addressing Apple's ITP changes
Developed more reliable attribution solution to counter the impact of third-party cookie restrictions
Designed server-side tracking implementations to maintain marketing measurement capabilities

For J.Jill, implemented a high-performance, scalable data processing solution handling large data volumes with exceptional response times.

Implemented large-scale data processing solution that processed one trillion rows in a partitioned BigQuery table
Built auto-scaling infrastructure on AWS that handled traffic from 150,000 requests per hour on average to peaks of 400,000 requests per hour while maintaining a median 25ms response time
Designed dynamic EC2 load balancing system that automatically scaled from 2-10 nodes based on demand
Developed dashboard reporting for real time 1st party conversion data which also reflected on Facebook ads API sourced data

Facebook Marketing Technology Partner (2021-2022)

Selected as one of 250 global technology partners to support Facebook's largest advertisers, providing technical consulting to approximately 30 clients with focus on Shopify implementations and developing integration strategies between Facebook's marketing tools and client platforms. This included all aspects of web site tracking, CAPI, Lead Ad Chat Bots.

Michael Kors Analytics Implementation (2018-2022)

Managed analytics strategy and implementation for Michael Kors over a four-year engagement, overseeing both technical implementation and team leadership aspects of this major retail brand's analytics transformation.

Hired and supervised a full-time Open Source Brokers employee dedicated to the Michael Kors account
Implemented Adobe Launch and Adobe Analytics solutions in collaboration with internal teams
Integrated analytics validation directly into Michael Kors' existing Selenium test suite, leveraging their substantial website test coverage to simultaneously validate data collection and tagging
Participated in weekly brainstorming sessions with key stakeholders to evolve analytics capabilities

QFD Analytics (2018-2019)

Developed Adobe Analytics data quality monitoring RUM solution
One of the first Edge CDN data collection applications
Designed high-performance data ingestion system for enterprise-scale implementation
Created test environment capable of sustaining 40,000 POST requests per second
Implemented with Sephora as initial enterprise client

Estee Lauder Companies (ELC) Analytics Transformation (2008-2018)

Architected Estee Lauder's global analytics platform transformation, supplementing Adobe Analytics to Google Analytics Premium across 300+ e-commerce sites spanning multiple brands and locales. This multi-year initiative established standardized approaches to analytics implementation and data collection. The intention over time was to eventually reduce costs regarding Adobe Analytics which ran into the tens of millions.

Evaluated and selected the Google Analytics partner that would design Estee Lauder's entire global GA 360 solution (Now named WPromote)
Did a POC comparison between Tealium and Segment.io (Segment later introduced me to the Facebook Marketing partner program)
Recommended Tealium to ELC and helped design a global/multi-brand implementation approach for Tealium iQ with consideration for future Tealium Audience Stream integration
Created standardized templates and comprehensive documentation for Cognizant teams to execute Tealium and GA360 rollouts across 300+ global e-commerce sites
Helped establish cross-brand analytics standards that maintained global consistency while accommodating brand-specific requirements
Assisted in building a Drupal team as starting point for a global project (Smashbox.com continued using this original system)
Participated in Estee Lauder Online's global planning summit (2012)
Served as technical liaison between frontend/backend developers and Perl/PHP developers

About Us

Alicia Lin — Fri, 18 Feb 2022 21:57:56 GMT

OpenSource Brokers...