Top all-time · #5711
cramer.io
Personal blog · cramer.ioprogrammingcareer
cramer.io is a personal blog at cramer.io about programming and career. Since 2014, 14 different Hacker News readers have linked it 20 times, most often “On Pull Requests”. No feed was found, so read it on the site itself.
Too few sampled comments (13) to say how often HN recommends it.?
Why HN links it
HN readers link cramer.io posts on pull requests and code review, usually to support praise of Phabricator's review workflow over GitHub. Other linked posts cover threaded comments in PostgreSQL, Redis and serving Python apps.
Summarised by Claude from a sample of 13 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- On Pull Requests3 people · 5 mentions · first linked 2014-05-05
- /2014/05/03/on-pull-requests3 people · 3 mentions · first linked 2016-02-21
- /2010/05/30/scaling-threaded-comments-on-django-at-disqus/2 people · 3 mentions · first linked 2014-11-21
- Mocking Python Requests with Responses2 people · 2 mentions · first linked 2014-05-21
- Scaling SQL with Redis2 people · 2 mentions · first linked 2014-05-13
What Hacker News says?
> 1. Phabricator is actually a suite of different applications that do specific things (e.g. source code hosting, issue tracking, project management, ...). Although Phabricator ticked all our feature boxes, some of the components it ships with are very immature and/or don't get a lot of attention from the development team. The features which aren't explicitly marked "experimental" work very, very well in my experien…
Comment linking /2014/05/03/on-pull-requests/
on “Dear open-source maintainers, a letter from GitLab”Submitted Scaling SQL with Redis as a story · 125 points
HN discussionPhabricator is a really solid GitHub alternative. Some of the largest open source projects are using it and lots of companies. I believe that the GitHub pull request workflow and issue tracker does not scale to large projects and very much prefer Gerrit/Phabricator. Phabricator was created at Facebook for a large development team (mobile apps) and it shows. They have solutions for issues which only appear at scale (…
Comment linking /2014/05/03/on-pull-requests
on “GitLab Master Plan”Submitted On Pull Requests as a story · 58 points
HN discussionPhabricator is a brilliant piece of software. Very well written code, an emphasis on security, nice UI, tons of features. Once you get used to it, the Differential code review process feels very natural (better than pull requests, even). Further reading: http://gregoryszorc.com/blog/2013/10/14/phabricator-is-aweso... http://cramer.io/2014/05/03/on-pull-requests/
Comment linking /2014/05/03/on-pull-requests/
on “Gogs, an alternative to Gitlab”Submitted Mocking Python Requests with Responses as a story · 9 points
HN discussionJust use Phabricator! It's the best code review system I've used so far. Many large open source projects and companies have adopted it. Someone neatly wrote up the main advantages: http://cramer.io/2014/05/03/on-pull-requests Phabricator's issue tracker is also an excellent choice over GitHub's simplistic issue tracker. Also, Gerrit isn't that hard and I've seen small teams get productive with it within a 1-2 weeks.…
Comment linking /2014/05/03/on-pull-requests
on “Abandoning Gitflow and GitHub in favour of Gerrit”Submitted Mocking Python Requests with Responses as a story · 7 points
HN discussionhttp://cramer.io/2010/05/30/scaling-threaded-comments-on-dja... This is where recursions is useful. For many scenarios adjacency list + recursive CTE scales better than any other hierarchy model.
Comment linking /2010/05/30/scaling-threaded-comments-on-django-at-disqus/
on “PostgreSQL Magic”Submitted Distributing 3rd Party JavaScript with Python Packages as a story · 2 points
HN discussionTake a look at Phabricator: http://phabricator.org/ It has it's own code review workflow which is, in my opinion, superior to Github's. A nice summary: http://cramer.io/2014/05/03/on-pull-requests/
Comment linking /2014/05/03/on-pull-requests/
on “Google has quietly launched a GitHub competitor”Submitted Be a Problem Solver as a story · 1 points
HN discussionIt's a fine substitute for GitHub. Both are source code and project management tools. Just because they have different user interfaces doesn't meant that they don't solve the same problem. Phabricator is much more flexible and that comes with a small cost in complexity, but the result is a system which provides a superior workflow, especially in enterprise environments: https://www.quora.com/What-are-the-advantages-…
Comment linking /2014/05/03/on-pull-requests/
on “GitLab 8.3 released with Auto-merge and GitLab Pages”We have used these for our discussion features on Pathwright. With ltree, you don't have as much flexibility when sorting by multiple values. With the Recursive CTE, you can go nuts and still end up very efficient. I believe Disqus uses this, as well: http://cramer.io/2010/05/30/scaling-threaded-comments-on-dja...
Comment linking /2010/05/30/scaling-threaded-comments-on-django-at-disqus/
on “Representing Trees in PostgreSQL”That's the method that Disqus used as well.[1] Later on they used a materialized path solution [2], but I remained impressed that the recursive query worked so well at their scale, enough so that I used the same method in a personal project that had a hierarchical comment system. Happily, it wasn't much of a hack to do this in Django... the raw query support is quite good; you don't have to sacrifice the ORM to do s…
Comment linking /2012/04/08/using-arrays-as-materialized-paths-in-postgres/
on “Tree structure query with PostgreSQL”Take a look at this: http://cramer.io/2010/05/30/scaling-threaded-comments-on-dja...
Comment linking /2010/05/30/scaling-threaded-comments-on-django-at-disqus/
on “Tree structure query with PostgreSQL”Hard to say since every tool out there moves very fast and we're just building what we think our users want. Overall my personal opinion is the "pull request" model is flawed for businesses but great for open source. Phabricator doesn't serve two masters in that regard. This means we focus more on developer efficiency and code quality. Tools like arcanist are harder to convince people to adopt, but save me personall…
Comment linking /2014/05/03/on-pull-requests
on “GitHub lock-in?”Here's a few interesting use cases for Redis, including using it to reduce write contention to an SQL db: http://cramer.io/2014/05/12/scaling-sql-with-redis/ The examples are in Python.
Comment linking /2014/05/12/scaling-sql-with-redis/
on “How to take advantage of Redis just adding it to your stack (2011)”and you should be using it: http://cramer.io/2013/06/27/serving-python-web-applications/
Comment linking /2013/06/27/serving-python-web-applications/
on “Researching a new form of HTTP caching optimization”
