rikatee

13 ms·

61.
The Django anti-pattern preventing your prod rollback(djangodoctor.medium.com)
2 points by rikatee 6y ago|0 comments
62.
Fixing inefficient Django ORM calls in brownfield projects(djangodoctor.medium.com)
2 points by rikatee 6y ago|0 comments
63.
Detect when using the wrong Django model field(djangodoctor.medium.com)
2 points by rikatee 6y ago|0 comments
64.
Auto detect flaky Django migrations(djangodoctor.medium.com)
2 points by rikatee 6y ago|0 comments
65.
Thinking CharField? Think Again(djangodoctor.medium.com)
2 points by rikatee 6y ago|0 comments
66.
NullBooleanField Is Dead(djangodoctor.medium.com)
1 points by rikatee 6y ago|0 comments
67.
Django's {% static %} is not just about S3(djangodoctor.medium.com)
1 points by rikatee 6y ago|0 comments
68.
Naked settings.py in your Django codebase?(djangodoctor.medium.com)
1 points by rikatee 6y ago|0 comments
69.
by rikatee 6y ago
If anyone would like to read more on the topic I wrote a blog post that includes this point and others: https://djangodoctor.medium.com/the-real-difference-between-... because while Django Doctor suggests potential improvem
70.
by rikatee 6y ago
not a fan of foxes, I see :)
71.
The hidden cost of Django's unique_for_date(djangodoctor.medium.com)
3 points by rikatee 6y ago|0 comments
72.
by rikatee 6y ago
I'm working on private repo support. chat with me at django.doctor if you want to get in on the private beta
73.
by rikatee 6y ago
Thanks! Even the simple "Syntax Error" comment could be the difference between bed time and another cup of coffee.
74.
by rikatee 6y ago
There will be shortly. In summary: - we dont' collect ANY personal data because we don't need ay. we don't even have a database, We can't misuse your persona data if we don't have it! - we don't create any non-
75.
by rikatee 6y ago
That's good insight, thanks :)
76.
by rikatee 6y ago
Maybe I'm grandiose but I see the "form factor" as key: MP3 players existed before ipods. Some people found the new form factor more convenient. Similarly they way Django Doctor works is more convenient: - it's suggests
77.
by rikatee 6y ago
I'm sorry swiley :'(
78.
by rikatee 6y ago
Glad to be of service :)
79.
by rikatee 6y ago
Agreed in general, but Django Doctor is not a linter. It suggests code improvements the dev can choose to commit with one click. Linters block builds until the code conforms to a pre set style, often requiring the dev to manually do it them
80.
by rikatee 6y ago
Nice! They're quite different beasts though. Restyled enforces code style, while Django Doctor suggests fixes for Django specific anti patterns and has a fox for a mascot. See. Completely different ;)
81.
by rikatee 6y ago
Your wish is granted kind of: https://github.com/marketplace/django-doctor/ It's a github app, rather than an action. Actions still require you to update a yaml file to use. Regarding CI: I don't think D
82.
by rikatee 6y ago
In general I agree, but specifically for this: It does mean you don't have to do it _for this particular feature_. If we can "reduce hard" then that's a good thing. It's one less configuration to manage.
83.
by rikatee 6y ago
in the case of Django Doctor - there is no direct alternative you can run locally. Nothing else does this: - finds Django anti patterns. pretty sweet. - suggests the fix in the PR. One click fix? yes pls. - Check your entire codebase in sec
84.
by rikatee 6y ago
Nope, all 100% pure custom code. The closest to existing tools are: https://github.com/lamby/django-lint/ https://github.com/PyCQA/pylint-django but- you have to set those up yourself in a C
85.
by rikatee 6y ago
Not to nitpick, but restyled and Django Doctor do different things in different ways, so I don't think it's and OR
86.
by rikatee 6y ago
Our business model will soon become clear: oranisations will pay. Individuals not. Currently still ironing out things and seeking feedback so at the moment free to all so I can get maximum feedback :) btw, we dont actually have any of the u
87.
by rikatee 6y ago
Blocking the build works well for things that are boolean "correct" or "not correct", but some things are not are just "food for thought". Django doctor points out when something looks like it can be improved,
88.
by rikatee 6y ago
I've been in a few organization with hundreds of repos. It can be a pain to upgrade libraries. In this context, with SaaS you don't need to. But yes, SaaS is not a silver bullet. If you like convenience and getting updates, bug fi
89.
by rikatee 6y ago
Unfortunately not. It's aimed at SaaS so users gain some convenience but lose a bit of other things :)
90.
by rikatee 6y ago
Thanks for the feedback, and glad you found it useful :)

More ›