9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Better Code Snippets & Suggestions
Date: Mon, 22 Feb 2021 17:10:42 -0800	[thread overview]
Message-ID: <CAJSxfmJqaX4UDgrC-iB4D9W=jccwh68zHCpzw4UfS7juu4qE+w@mail.gmail.com> (raw)
In-Reply-To: <CA6DFE7A-EF62-44F6-9964-DB18E43521F4@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]

My first reaction is that an RNN-based code generator trained on a
particular dataset (e.g. Plan 9 sources) might be more fruitful.

On Mon, Feb 22, 2021 at 3:08 PM William Linkmeyer <wlink10@gmail.com> wrote:

> Dearest Nines,
>
> I’ve been reading these email chains for about three years now. You’ve all
> taught me quite a bit. I understand that this will be a bit off-topic as
> it’s not directly related to Plan9. So be it. I wanted to start a chain and
> chime in on something that I do have experience with.
> I’ve been developing a code suggestion platform. The concept is simple
> relatively simple. As the programmer is typing, patterns in the given code
> block are identified and compared to a database of tagged code snippets.
> The code snippet that is most relevant will be presented to the programmer
> as a suggestion.
> The code snippets all come originally from Stack Overflow, GitHub, and my
> own programs. I’m in the process of tagging these snippets for important
> features such as purpose, list of operations, any applicable design
> patterns, paradigms, etc. The more “essential” features are being tagged as
> well — features such as the number of arguments, return type, etc.
> It’s an interesting project to me. While I think that it’s going well, I’m
> certain that the large-brain folk here have important commentary on it.
>
> With Peace,
> Will
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions
> <https://9fans.topicbox.com/groups/9fans> + participants
> <https://9fans.topicbox.com/groups/9fans/members> + delivery options
> <https://9fans.topicbox.com/groups/9fans/subscription> Permalink
> <https://9fans.topicbox.com/groups/9fans/T4f7afadf357a15b1-Mde89233e3e131ea3f441c36d>
>

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4f7afadf357a15b1-M37e90a17c9db8faca41e70c4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2512 bytes --]

      reply	other threads:[~2021-02-23  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 23:07 William Linkmeyer
2021-02-23  1:10 ` Skip Tavakkolian [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJSxfmJqaX4UDgrC-iB4D9W=jccwh68zHCpzw4UfS7juu4qE+w@mail.gmail.com' \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).