rikatee

6 ms·

1.
by rikatee 2y ago
it's a good start. VSCode is most popular. Largest impact. More potential users. More likely to find a customer base.
2.
by rikatee 2y ago
> internally and see a 5-10x boost on some tasks. That's my experience with co-pilots too: - Generating tests - Generating functions consistent with prevailing style of similar functionality in the existing codebase. The greater the
3.
by rikatee 2y ago
I like this. I think AI agents are the future of software development. AI will not replace devs. Devs that use AI will replace devs that do not use AI. The most effective devs will be those employing a fleet of AI agents, acting as the glue
4.
You might be using assert wrong (Python)(highertier.com)
2 points by rikatee 4y ago|1 comments
5.
Python old style string formatting is sometimes best practice(blog.devgenius.io)
1 points by rikatee 4y ago|0 comments
6.
by rikatee 4y ago
FWIW, HN is much more positive (while also raising valid points that will be taken into account going forward)
7.
by rikatee 4y ago
flake8 does not currently support this check, as they are concerned about the false positives from "what if the string it later used in .format(...)" However, Code Review Doctor is more of a "this MIGHT be a problem. have you
8.
by rikatee 4y ago
what's also ironic is I left an easter egg in the code sample for how we downloaded the list of repositories and no one has noticed it yet.
9.
by rikatee 4y ago
klyrs was right about the reply from me (a dev behdind Code Review Doctor) being dismissive in the issue. I apologise for that. FWIW my reaction was classic "expectations not meeting reality": weeks of work to do (what I thought)
10.
We fixed f-string typos in popular Python repos(highertier.com)
139 points by rikatee 4y ago|145 comments
11.
by rikatee 4y ago
Yeah good point that sucks. I will move off wordpress because I'm not a fan of tracking cookies. It's got ridiculous.
12.
by rikatee 4y ago
interestingly 69 of the 666 repos had the f string issues
13.
10% of the 666 most popular Python GitHub repos have these f-string bugs(richardtier.com)
9 points by rikatee 4y ago|3 comments
14.
by rikatee 5y ago
of the codebases checked yep (20 of 666 checked). Bear in mind only 28% of codebases actually use built-in unittest package that this gotcha is affected by, so really it's 20 of 28% of 666 aka 10% ... but that claim would be hard to ju
15.
by rikatee 5y ago
Agreed in perfect world, but unfortunately any process that involves humans will involve human error. We do code review because we expect human error when the code was written by a human, but then we also expect not human error when the cod
16.
by rikatee 5y ago
we were all waiting for you to
17.
by rikatee 5y ago
yes that's exactly the kind of problem :)
18.
by rikatee 5y ago
it does not, it just prints them out in the console
19.
by rikatee 5y ago
the post covers the built-in unittest package, which 28% of devs still use. But pytest is nicer to work with. I think brownfield codebases and inertia are the reason 28% of devs work (or have to work) with unittest
20.
by rikatee 5y ago
you're right thanks! Updated :)
21.
by rikatee 5y ago
deep ninja turtles lore
22.
by rikatee 5y ago
oh dear time for a edit as I did indeed mean Schrödinger!
23.
3 percent of Python codebases we checked had silently failing unit tests(richardtier.com)
98 points by rikatee 5y ago|66 comments
24.
Python repos checked. 11% of 5409 open() calls were never closed(codereviewdoctor.medium.com)
5 points by rikatee 5y ago|0 comments
25.
by rikatee 5y ago
once tensorflow pointed to keras-team this happened https://github.com/keras-team/keras/issues/15854 resulting in https://github.com/keras-team/keras/pull/15876
26.
by rikatee 5y ago
cool product :) it is just linting or do any of the tools do code transformation to offer the fix for the lint failure? (code review doctor also offers the fix if you add the github PR integration)
27.
by rikatee 5y ago
in a blog post about the evils of typos there was a typo! classic https://en.wikipedia.org/wiki/Muphry%27s_law ;)
28.
by rikatee 5y ago
there is also https://pypi.org/project/flake8-tuple/ typo in the url (or in HN's markup) btw: it's https://codereview.doctor
29.
by rikatee 5y ago
can do a good job at allowing long urls for example, but would be whack a mole trying to cater for "all" purposeful implicit string concatenations
30.
by rikatee 5y ago
unfortunately like 10% of the bugs were in the tests themselves. e.g., the sentry one https://codereviewdoctor.medium.com/5-of-666-python-repos-ha... the tests are only as good as the code they're written with, and as

More ›