rekahrv

7 ms·

1.
Prompt engineering for Claude's long context window(anthropic.com)
1 points by rekahrv 3y ago|0 comments
2.
How much information is too much information?(sourcery.ai)
2 points by rekahrv 3y ago|0 comments
3.
A Common Misconception About Deleting Objects in Python(blog.dailydoseofds.com)
2 points by rekahrv 3y ago|0 comments
4.
Top AI Coding Assistants in 2023(sitepoint.com)
1 points by rekahrv 3y ago|0 comments
5.
The Contradictions in ‘The Zen of Python’(thenewstack.io)
3 points by rekahrv 3y ago|0 comments
6.
Generating Code Without Generating Technical Debt?(sourcery.ai)
1 points by rekahrv 3y ago|0 comments
7.
Replit AI Manifesto(blog.replit.com)
2 points by rekahrv 3y ago|0 comments
8.
The Impact of Technical Debt – 2022(sourcery.ai)
1 points by rekahrv 3y ago|0 comments
9.
AI Is Writing Code Now. For Companies, That Is Good and Bad(wsj.com)
3 points by rekahrv 3y ago|0 comments
10.
Non-caffeine components of coffee, their effects on neurodegenerative diseases(peterattiamd.com)
2 points by rekahrv 3y ago|0 comments
11.
Webb Maps Surprisingly Large Plume Jetting from Saturn’s Moon Enceladus(nasa.gov)
3 points by rekahrv 3y ago|0 comments
12.
Git: Detect an in-progress cherry-pick, merge, rebase, or revert(adamj.eu)
27 points by rekahrv 3y ago|0 comments
13.
Chatting with Will McGugan: From Side Project to Startup(sourcery.ai)
3 points by rekahrv 3y ago|0 comments
14.
A List of Programming Playgrounds(jvns.ca)
2 points by rekahrv 3y ago|0 comments
15.
Is your code too complicated?(sourcery.ai)
5 points by rekahrv 3y ago|0 comments
16.
Will A.I. Make Us Smarter? [audio](freakonomics.com)
1 points by rekahrv 3y ago|0 comments
17.
The Basics of Python Packaging in Early 2023(drivendata.co)
4 points by rekahrv 3y ago|0 comments
18.
by rekahrv 3y ago
That's an interesting example. Also, the same pattern has happened to other terms as well: 1. At first, a quite specific meaning. 2. As time goes on, the same term gets used for more & more things.
19.
by rekahrv 3y ago
Great book. The interview with Peter Attia on Star Talk was also interesting (and some parts hilarious): https://startalkmedia.com/show/medicine-3-0-extending-human-...
20.
by rekahrv 3y ago
Yeah, anything that contradict s PEP-8 conventions looks unnatural in Python. :-)
21.
by rekahrv 3y ago
Yes, that's a great point. Some names are generally unclear, but more often, they are unclear in a context. Do you have some "contextual" examples?
22.
by rekahrv 3y ago
I agree with those points, both on the positive and negative side. Do you have some examples of vague or misleading names?
23.
by rekahrv 3y ago
Yes, exactly. Thanks for the clarifying question. :-) Any kind of artifact in code: modules, functions, classes, arguments, variables...
24.
What are some good and bad names you've encountered in Python code?
3 points by rekahrv 3y ago|10 comments
25.
by rekahrv 3y ago
“Every six months or so, someone would ask in our meetings, ‘Should we think about general purpose code generation,’ but the answer was always ‘No, it’s too difficult, the current models just can’t do it,’” Lol
26.
by rekahrv 3y ago
TLDR: * Falsy values (empty string, empty list) should have the same behavior as None. * Don't use `==` for comparison with None or NaN
27.
Comparing to None in Python and Pandas(sourcery.ai)
4 points by rekahrv 3y ago|1 comments
28.
The time to be unpredictable and human(christianheilmann.com)
1 points by rekahrv 3y ago|0 comments
29.
by rekahrv 3y ago
Thanks a lot, that's very insightful. Comparing the launch of Effective XGBoost to Effective Pandas: What do you think: What are the reasons XGBoost had so much more sales in the first days? * bigger audience? * better topic? * anythin
30.
by rekahrv 3y ago
PDEP-8 suggesting various changes regarding the `inplace` and `copy` arguments: https://github.com/pandas-dev/pandas/pull/51466

More ›