sanyam-khurana
Joined 3 years ago
Karma
13
Submissions
16
Member since
Jan 12
Recent submissions
Comment · 9 months ago
Comment · 1 year ago
Yes, I maintained a cookie-cutter template for over a decade, and it was a pain for me to get it updated. I wanted to get something newer, like a copier, which eliminates the pain of updating, while I can focus on building things.
I have also added temporal (though still testing it) since it's getting a lot popular these days.
Comment · 1 year ago
Thank you for your suggestion. I'll update the README so that people can hit the ground running faster!
Comment · 1 year ago
Thanks, this seems interesting!
Comment · 1 year ago
Happy to let you know that I've just updated the template to use Python3.14 by default, along with matrix tests that also tests the template against Python 3.14 in here: https://github.com/CuriousLearner/django-keel/commit/87eae7e...
Comment · 1 year ago
Interesting. Do you have any opinion on what this should be rephrased to, so that it's clearer?
Comment · 1 year ago
It's configurable. The minimum quality gate check is set at 80% here: https://github.com/CuriousLearner/django-keel/blob/main/temp...
Also, to answer why ever be less than 100% is that it depends. Usually, I prefer writing behavioural & integration tests, over chasing per-line coverage which might give a false confidence.
I'm not saying getting 100% coverage is bad, but with my experience working on several different projects, I've seen that the last 10-20% is usually low-value surface.
For critical modules like auth, money, policies (business-logic), should aim at close to > 95%.
When you reach that 100% mark, in my opinion, you might have to write brittle tests which slows down your refactoring with little risk reduction.
Again, to summarize, it's not a black/white answer on having 100% or no coverage, but this differs from project to project, and generally having anything above 80% that covers the core-business logic of projects tends to work in my opinion.
Comment · 1 year ago
It was all great on Reddit, though until some folks decided to downvote for no apparent reason and then deleted their accounts.
I've chosen copier because of all the pain I've gone through for years just to keep my template and projects running in parallel updated.
Comment · 1 year ago
Interesting! I've loved Strawberry GraphQL.
If you end up adding anything, you may also choose to give back to the template so that others can use it.
I do not understand what you meant by "ty", though?
Comment · 1 year ago
Quite honestly, I haven't. I've been playing with temporal, and since it's picking up pace, I thought to have an option to have Temporal in place of celery.
Comment · 1 year ago
Python 3.14 is there in the repo, though not added in the docs since I haven't tested it with all the infra stuff. The idea is to keep it updated to at the least previous 2 versions of Python/Django at all times so that it's easier for people to keep their projects updated.
Comment · 1 year ago
Definitely, if you find anything that can be improved (even if "docs are not super-clear here), please feel free to raise a PR or report it as an issue.
Comment · 1 year ago
Great question because this has haunted me for over 10 years with cookiecutter. Most of the time I was copy-pasting newer features from running projects back into the template, and then copy-pasting in other running projects.
But Keel is based on copier which has a "pull" based approach. It means unlike cookiecutter where you generate project from template once, you can run `copier update` to update your project with the latest addition to the template. (It takes care of merging based on the initial config that you selected).
It's just running one command `copier update`. Docs here: https://django-keel.readthedocs.io/en/latest/?h=copier+updat...
You don't need to fork it unless you want to make some improvements or build upon the base template itself.
Remote: Yes
Willing to relocate: Yes (Canada/US)
Technologies: Python (Django), OpenAI, LLM, LangChain, LangGraph, Langsmith, Go, distributed systems, Typescript/React, backend/platform, Kubernetes, Docker, Terraform/IaC, AWS, CI/CD, Postgres, Redis, queues/async, observability
Résumé/CV: https://sanyamkhurana.com/ (Master of Computer Science (Machine Learning/Interactive Intelligence specialization) from Georgia Institute of Technology; experience with Fortune 500 + startups; resume available on request)
Email: [email protected]
GitHub: https://github.com/curiouslearner