kdeldycke / cqlengine-relation-columns

:wrench: Adds new relation columns to CQLengine storing pointers to other model instances.

My name is Kevin Deldycke, I'm a high-tech Engineering Manager.

Short Bio

I've held various positions in several industries and sectors as VP, Product Manager, Founding Engineer and Consultant.

After 15+ years of relevant engineering work, and 3+ years of hands-on management experience, I now build teams from scratch with self-sustaining culture, and my intent is to keep doing so.

Enabling engineers, leading managers, and make them feel productive is the most impactful thing I can bring to the table. So I'm always on the lookout for a high-tech management position, at a fast growing start-up with ambitious vision.

My most relevant experience was in growing a team from 0 to 12 at a world-class cloud computing provider. We built up the whole IAM ecosystem, as well as the Billing and Payment stack.

Achievements

• 💰 Designed, implemented and operated Scaleway's billing pipeline, generating multi-million dollars of revenue (and growing!). The whole thing. All by myself.

• 🚀 Then I built a team of 12 people to enhance and expand on the full Billing, Payment and IAM domain of the company. In doing so, I was given the fancy title of Product Manager, then VP.

• 🤝 Established lasting trust and loyalty. No one from my team resigned under my authority, in a company with a very high employee turnover rate.

• 🥇 World trending GitHub developer, and top-1% open-source developer.

• 🌟 21,000+ GitHub stars. The most popular repository being the Falsehoods Programmers Believe in. It is regularly featured on popular media.

• 💵 Wrote the best open-source payroll software in the world.

• 🌐 Created and managed the African subsidiary of my first employer.

• 🛰 Authored code that's running on Mars.

• 🤡 Wasted 6 years solving an XKCD joke.

More

• Interviews
• LinkedIn resume

cqlengine-relation-columns's Issues

Merge Relation and CompositeRelation

There's no need for the Relation column: the latter is a legacy implementation now that the CompositeRelation column supports all use cases of Relation.

Once we get rid of Relation, we can reuse its name for CompositeRelation.

Implement model register

Models we pointing to in relation columns are imported from an hard-coded location constant MODELS_MODULE in file cqlengine_relation_columns.py.

We need to replace this crude implementation by a proper model registry.

Push to PyPi

Once #1 is cleared, rework the whole packaging and push a proper release to PyPi.

Rename module

Rename this module to adopt (future) CQLengine conventions and increase dicoverability. Wait for issue https://github.com/cqlengine/cqlengine/issues/219#issuecomment-52365956