HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
shariq
burgundy
Python2015–2015
shariq / burgundy

burgundy

aesthetically pleasing words

3Distinct people
4Mentions
0Explicit recommenders
118GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

aesthetically pleasing words

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour4 dated mentions

Observed mentions: 2015-11-30 00:00:24 UTC to 2015-11-30 05:05:47 UTC.

01232015-11-30 00:00:00 UTC to 2015-11-30 01:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsNov 30, 00:002015-11-30 01:00:00 UTC to 2015-11-30 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 02:00:00 UTC to 2015-11-30 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 30, 02:002015-11-30 03:00:00 UTC to 2015-11-30 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 04:00:00 UTC to 2015-11-30 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 05:00:00 UTC to 2015-11-30 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 30, 05:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Nov 30, 00:002015-11-30 00:00:00 UTC2015-11-30 01:00:00 UTC303
Nov 30, 01:002015-11-30 01:00:00 UTC2015-11-30 02:00:00 UTC000
Nov 30, 02:002015-11-30 02:00:00 UTC2015-11-30 03:00:00 UTC000
Nov 30, 03:002015-11-30 03:00:00 UTC2015-11-30 04:00:00 UTC000
Nov 30, 04:002015-11-30 04:00:00 UTC2015-11-30 05:00:00 UTC000
Nov 30, 05:002015-11-30 05:00:00 UTC2015-11-30 06:00:00 UTC101

What Hacker News says

4 sources
Ooh front page; I guess this calls for a bit of an explanation! First off - used this code for training the models: http://karpathy.github.io/2015/05/21/rnn-effectiveness/ Very very easy to setup and train; highly recommend playing around with your own training data (just a text file!) This project's code: github.com/shariq/burgundy Styled and deployed the website about a year ago at a hackathon; it then used a nice wordlist with hand picked words. (repo/wordserver/old_burgundy_words.txt) Few days ago: got the server to start training a bunch of models (~200), with randomized parameters, using the original wordlist as the training data. (repo/rnn/rnn.py:forever) Yesterday: woke up at 3 AM after my sleep schedule rolled around, started exploring the output of models trained to different numbers of epochs and run at different temperatures.
Read the rest
Subjectively looked at the outputs, decided some model/epoch/temperature tuples were horrible, got rid of those. Wrote a few different scoring functions (just using intuition for what kinds of bad outputs seemed to be commonly occurring) to score the model/epoch/temperature tuples. Got the top ~10 scoring tuples from each scoring function, plus added some additional interesting ones along the way, and then used a pronunciation scoring function (repo/rnn/pronounce.py) to select the top 5 of all of these. Funny enough, the top 5 tuples all used different models and a varying range of temperatures (i.e, not the same model from different epochs, and picking the right temperature significantly improved how well the model performed) (repo/rnn/explore.py) Since the models would still occasionally output words which were completely unpronounceable, I put some code on top of the models which would generate a bunch of words then discard the bottom 1/3rd of unpronouncable words. A significant portion of generated words from these models also started with a "c" or "b" for some reason: gave those a high chance of being discarded. Short words were also uninteresting, and extremely long words would occasionally show up: added probabilistic filters for length. Finally, initialization time of LuaJIT is very high, so I had the server keep a pool of words which gets reseeded as it runs out. (repo/rnn/rnnserver.py) If you want to train your own word generator and you need some pointers, would love to help: @shariq
In Word generator using recurrent neural networks

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.