Readit News logoReadit News
codenamev commented on Will AI code generation kill or elevate software craftsmanship?   therubyaipodcast.com/2388... · Posted by u/codenamev
codenamev · 16 days ago
We explore the tension between two cultures: the traditional craftsmanship ethos (clean, refactored code) and the "just regenerate it" mindset of younger AI-native developers. Obie Fernandez argues this might be less about losing skills and more about redefining them.
codenamev commented on The AI Software Architect   github.com/codenamev/ai-s... · Posted by u/codenamev
codenamev · 3 months ago
Let a team of specialists collaborate with you and your coding assistant of choice to develop and maintain high quality software.
codenamev commented on Launch HN: Codebuff (YC F24) – CLI tool that writes code for you    · Posted by u/jahooma
boratanrikulu · 10 months ago
Allowing LLMs to execute unrestricted commands without human review is risky and insecure.
codenamev · 10 months ago
You are really missing out: https://github.com/e2b-dev/e2b
codenamev commented on Beyond Accuracy: Evaluating Doximity GPT Output for Medical Professionals   technology.doximity.com/a... · Posted by u/codenamev
codenamev · a year ago
At Doximity, we go to great lengths to ensure the quality of our products aligns with the standards physicians require. Across various industries, Large Language Models (LLMs) have become the backbone of numerous applications, driving advancements in everything from natural language processing to automated content creation. As we continue to develop products that make use of these LLMs, the need for rigorous and comprehensive evaluation of their outputs has never been more critical. Strap in as we explore the process for evaluating our Doximity GPT product, Doximity’s HIPAA-compliant medical writing assistant, focusing on the importance of using "ground truths" to establish baseline metrics and the relative performance of contender models.
codenamev commented on Ruby delights built into the language   technology.doximity.com/a... · Posted by u/codenamev
codenamev · 3 years ago
Hey everyone! OP and author here.

I would like to thank everyone for such a lively discussion! It has been a joy reading through and feeling the sentiment ebb and flow in that traditional HN fashion

For those curious and inquisitive minds out there, this article was intended to provoke emotion, fuel your creative soul, and pull you in to the Ruby source code. The precursor to this article was one I wrote on how IRB works and many of it's features. I had accidentally stumbled upon this "samples" directory and like many here wondered _why_ it is there and _what purpose_ was it serving. While many of the examples are a bit dated, they all make use of the standard library in various ways, and many make use of Ruby in ways _I_ hadn't seen before. Even if you don't care for the examples themselves, I hope to leave you with ample reading material to explore those unfamiliar crevices of Ruby.

As many have shouted, there are quite a few pain points in the Ruby language documentation, best practices, discoverability, and onboarding of new comers. This is an incredible time to be a part of this community and make this language as enjoyable to learn as it is to write.

codenamev commented on Ruby delights built into the language   technology.doximity.com/a... · Posted by u/codenamev
nomilk · 3 years ago
How do I run these? For example:

```

ruby sample/biorhythm.rb

ruby: No such file or directory -- sample/biorhythm.rb (LoadError)

```

(I know I could simply copy these files off GitHub, but does the IRB on my computer already know about these biorhythm/calendar files somehow). Am I missing something?

codenamev · 3 years ago
I will update the article, but all of the code snippets were run from the root of the ruby source code. So before you run them:

git clone https://github.com/ruby/ruby.git && cd ruby

u/codenamev

KarmaCake day142July 21, 2014
About
[ my public key: https://keybase.io/codenamev; my proof: https://keybase.io/codenamev/sigs/9sRp_-ddupZQdFg0wetRy9FVKHuxuI__l9WOwLDmXA0 ]
View Original