tomlemon

9 ms·

31.
Genius (YC S11) is hiring for iOS, full stack, devops, and front end(genius.com)
1 points by tomlemon 12y ago
32.
Genius (YC S11) is hiring for iOS, full stack, devops, and front end
1 points by tomlemon 12y ago
33.
Sandi Metz at Code Genius (Brooklyn) 1/22(code.genius.com)
1 points by tomlemon 12y ago|0 comments
34.
(Rap) Genius still only 8 devs(meta.genius.com)
1 points by tomlemon 12y ago|1 comments
35.
by tomlemon 12y ago
Also soon we're going to take our annotation technology to OTHER SITES! This will allow anyone to create annotations anywhere (and save us the trouble from copying EVERYTHING to Genius.com)
36.
by tomlemon 12y ago
I feel you on "only A players" being a bromide – but I do think there are some counter-intuitive elements to "why do that" and "how to do that" and "what makes an A player anyway" that I tried to spel
37.
by tomlemon 12y ago
Slash for all HUMANS! it's basically the best book ever – i'll add a link in to the annotation..
38.
The Genius ISMs(meta.genius.com)
18 points by tomlemon 12y ago|11 comments
39.
Genius (YC S11) – Full Stack, DevOps, Android, iOS(meta.genius.com)
1 points by tomlemon 12y ago
40.
Genius (YC S11) is Hiring
1 points by tomlemon 12y ago
41.
How Rap Genius Fired A Cofounder — And Just Raised $40 Million (Annotated!)(businessinsider.com)
8 points by tomlemon 12y ago|0 comments
42.
by tomlemon 12y ago
The annotated transcript is HERE: http://news.rapgenius.com/Lemon-how-launching-the-worst-vers...
43.
Mixergy interview with Rap Genius co-founder Tom Lehman re: Worse being Better(mixergy.com)
2 points by tomlemon 12y ago|1 comments
44.
Genius for iPhone is Here(news.rapgenius.com)
6 points by tomlemon 13y ago|1 comments
45.
by tomlemon 13y ago
Tom Lehman here (Rap Genius co-founder) The fact that all our text and song page URLs end in "-lyrics" is a relic of a time when we hosted almost exclusively lyrics. Making the changes required to host all kinds of annotated texts
46.
Rap Genius is Back on Google(news.rapgenius.com)
242 points by tomlemon 13y ago|188 comments
47.
Google Has Officially Penalized Rap Genius For Link Schemes(searchengineland.com)
502 points by tomlemon 13y ago|283 comments
48.
by tomlemon 13y ago
Here's the actual annotated excerpt: http://poetry.rapgenius.com/Junot-diaz-the-brief-wondrous-li...
49.
Rap Genius Seeks iOS Genius to Build Genius iOS App
1 points by tomlemon 13y ago
50.
by tomlemon 13y ago
I feel you, but if someone happens to CATCH you wearing incognito socks (perhaps while you're mid step or something).. well, that's basically the most beta feeling in the world (so I don't think it's worth the risk!!)
51.
by tomlemon 13y ago
I explain more in http://news.rapgenius.com/1901085 (Click the green lines FOR ANNOTATIONS)
52.
How Rap Genius Raised $1.8M in Seed Funding Without Knowing What We Were Doing(news.rapgenius.com)
146 points by tomlemon 13y ago|103 comments
53.
by tomlemon 14y ago
> If Heroku wasn't providing enough performance for their money (regardless of technical cause), then why did they stick around so long? We didn't know how bad the performance was because Heroku's tools (logs and New Relic) reported inc
54.
by tomlemon 14y ago
If you use Heroku and New Relic, make sure you install the gem we wrote to make New Relic report correct queue times: https://github.com/RapGenius/heroku-true-relic
55.
Money Trees – Rap Genius Response to Heroku(rapgenius.com)
283 points by tomlemon 14y ago|100 comments
56.
by tomlemon 14y ago
Rap Genius cofounder here. Below is the full unedited text of https://help.heroku.com/tickets/37665 , a Heroku support ticket I logged about 1 year ago. Sorry it is so long, but I think you'll find it interesting: Tom@Rapgenius| about 1 ye
57.
Rap Genius responds to Heroku's Technical Summary(rapgenius.com)
15 points by tomlemon 14y ago|0 comments
58.
by tomlemon 14y ago
http://rapgenius.com/Jesper-joergensen-routing-performance-u... Just put it up on Rap Genius – create an account to help explain this post to the Heroku users it affects!
59.
by tomlemon 14y ago
> Their response to Heroku's response ought to have been along the lines of: "Hurray! Everyone's boat is rising with the tide." Not this. If Heroku actually knew about the problem for a long time and yet didn't officially respond or apo
60.
by tomlemon 14y ago
When Heroku's apology for misleading its customer is ITSELF misleading.. that's bad > Especially the one line about the date of the report, that's just pedantic. What they claim to have known and when is very relevant to how much you ca

More ›