Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
schneems
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
50 ms
·
541.
▲
Coders Code
(schneems.com)
1 points
by
schneems
9y ago
|
0 comments
542.
▲
by
schneems
9y ago
You would also get Review Apps which are pretty sweet. I work for Heroku, review apps is one of my favorite features we've launched.
543.
▲
Ruby Back End Performance Getting Started Guide
(schneems.com)
2 points
by
schneems
9y ago
|
0 comments
544.
▲
Stopping the Death Spiral of Indecision
(schneems.com)
1 points
by
schneems
9y ago
|
0 comments
545.
▲
The Fastest Way to Generate a Heap Dump on Heroku
(schneems.com)
1 points
by
schneems
9y ago
|
0 comments
546.
▲
The Four Year Typo
(schneems.com)
2 points
by
schneems
10y ago
|
0 comments
547.
▲
by
schneems
10y ago
Unrelated to this thread, I was just thinking to myself a few minutes ago "2015 me would be very surprised at how mad i've been able to bee for this long". So I would be more surprised if people weren't still outraged.
548.
▲
by
schneems
10y ago
Did you read the post? Nate actually mentions not to do this in the post and why.
549.
▲
by
schneems
10y ago
There are some other posts on the new ruby features, this is much more than that. It goes into the depths of the new changes and explains the why and how behind the changes. I loved the section explaining the new hashing. I knew it was fast
550.
▲
Ruby 2.4 Released: Faster Hashes, Unified Integers and Better Rounding
(blog.heroku.com)
2 points
by
schneems
10y ago
|
1 comments
551.
▲
Who Called Git? An Unusual Debugging Story
(schneems.com)
3 points
by
schneems
10y ago
|
1 comments
552.
▲
Writing a Rails Feature – Blow by Blow
(schneems.com)
1 points
by
schneems
10y ago
|
0 comments
553.
▲
by
schneems
10y ago
I put out a course a few years ago after being dissatisfied with the state of free Rails content http://schneems.com/ut-rails/ . I got amazing feedback from those who took it, but while the quality of response was good,
554.
▲
by
schneems
10y ago
Auto playing audio and an ad that takes up half the fold and scrolls with the page, how did you all read this?
555.
▲
by
schneems
10y ago
Almost forgot I open sourced it when I took it down. https://github.com/schneems/WhySpam
556.
▲
by
schneems
10y ago
I made something almost exactly like this 6 years ago. Called whyspam.me Good luck.
557.
▲
by
schneems
10y ago
I wrote the article, ask me anything.
558.
▲
by
schneems
11y ago
A bit late to the party. I find that many maintainers are left with a mountain of issues and very few eyeballs to help process them. I made a tool that helps others get involved with your open source projects to, hopefully, help keep your i
559.
▲
by
schneems
11y ago
> Using this guy's insane logic, we could get rid of all craftsmen, because nobody notices the details anyway. Hyperbolic much? > Why exactly is Rubygems giving idiots access to it's source code? It's open source https
560.
▲
by
schneems
11y ago
Let's keep the questions focused on Rails please.
561.
▲
by
schneems
11y ago
Q: How does anything ever get upvoted on HN if no one browses /newest?
562.
▲
by
schneems
11y ago
Successfully running Rails 5 beta in production and I'm on Rails contributor team. Ask me anything!
563.
▲
Upgrading to Rails 5 Beta – The Hard Way
(blog.heroku.com)
6 points
by
schneems
11y ago
|
4 comments
564.
▲
by
schneems
11y ago
Not sure why this guardian article is on the front page. Not really news, not really tech. As info-tainment goes the subreddit is way better, thanks for the link.
565.
▲
by
schneems
11y ago
Leaking is the wrong word. A leak implies that the memory was retained, RAM usage will go up forever and the process will eventually crash as a result. This is memory that sidekiq needs to do it's job, allocating strings, hashes, array
566.
▲
by
schneems
11y ago
It's all about your own internal GC. When you meet someone, you don't know if they're worth remembering or not. It takes a few encounters (or generations) before your mind realizes that this is necessary information. If you w
567.
▲
by
schneems
11y ago
I wrote the article, ask me memory questions.
568.
▲
Debugging a Memory Leak on Heroku
(blog.codeship.com)
47 points
by
schneems
11y ago
|
8 comments
569.
▲
Debugging a Memory Leak on Heroku
(blog.codeship.com)
1 points
by
schneems
11y ago
|
0 comments
570.
▲
by
schneems
11y ago
Check his previous posts, he does lots of work on backend speed. If you put all that advice into one post, it would be pretty overwhelming.
More ›