Top all-time · #10794
Andrew Ingram
Personal blog · andrewingram.netwebprogramming
Andrew Ingram's personal blog at andrewingram.net covers web and programming. Since 2007, 7 different Hacker News readers have linked it 15 times, most often “Common Pitfalls with Django and South”. The last post was in 2023, but the archive is still widely read.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link posts on Django schema migrations and on JavaScript form-reset handling. The comments only ask about or cite these posts, and none judge the writing.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
The personal website of Andrew Ingram, a London-based web developer.
Most-linked posts?
- Common Pitfalls with Django and South2 people · 3 mentions · first linked 2012-12-04
- Recipe kits, a great alternative to installable libraries2 people · 2 mentions · first linked 2023-07-20
What Hacker News says?
https://andrewingram.net/ I’m a bit tired of the design, I want to rethink it to better support short form content; but also because I’m a bit bored of the hyper-minimalist Medium-esque aesthetic. It’s actually fairly overengineered, so I’ll make sure the next version is even more overengineered. I’ve also been working on a level viewer for Mario Maker 2, had some fun problems. Next step is to switch the rendering t…
Comment linking /
on “Ask HN: Share your personal site”Submitted Common Pitfalls with Django and South as a story · 108 points
HN discussionBut if you were fetching the same data with a REST API (one that doesn't allow inclusion of relation fields, such as the JSON-API spec), you'd be doing the same amount of I/O and have the same horrible n+1 problem just between the client and server rather than inside the server, so it's spread across numerous requests rather than just one. Tools like Dataloader solve the n+1 problem quite effectively, and they've be…
Comment linking /posts/optimising-graphql-request-waterfalls/
on “Why not use GraphQL?”Submitted Deriving a Data Model from a Design with GraphQL as a story · 3 points
HN discussionDunno if it'll help at all, but I did write a thing about GraphQL connections that may clear up some things: https://andrewingram.net/posts/demystifying-graphql-connecti...
Comment linking /posts/demystifying-graphql-connections/
on “Why not use GraphQL?”Submitted Readability, Uniqueness, Hackability and Meaning in URL Design as a story · 2 points
HN discussionI'm assuming that most of the pitfalls I wrote about a couple of years ago are still applicable today, with either South or Django's own migrations: http://andrewingram.net/2012/dec/common-pitfalls-django-sout...
Comment linking /2012/dec/common-pitfalls-django-south/
on “Django 1.7 Released”Submitted Recipe kits, a great alternative to installable libraries as a story · 1 points
HN discussionThere was an interesting chat-log[1] someone posted on /r/Django on reddit talking about dealing with South migration merging/conflicts, and other issues that crop up in a multi-person project. I'm curious about the best practices for data-migrations as well; I've seen a few places[2][3] suggest that wrapping your fixture loading "./manage.py loaddata <fixture>" in datamigrations is better than leaving it up to init…
Comment linking /2012/dec/common-pitfalls-django-south/
on “Schema Migrations for Django”Submitted Do what you like to my CSS, but stay out of my HTML as a story · 1 points
HN discussionI’ve been trying out the pre-release version for the last couple of months, just published a quick brain dump of my thoughts related to the major changes (router, server components, etc) as they stand today. I’ve already heard from the team about the plan for my last concern, and it seems viable. https://andrewingram.net/posts/thoughts-on-next-13-react-18-...
Comment linking /posts/thoughts-on-next-13-react-18-3-dynamic-with-some-limits/
on “Next.js 13”Technically the spec is part of GraphQL itself now, but an optional recommendation, not something you’re obliged to do. That said, like you I am a fan. It’s a pretty defensible pattern, more here for those interested: https://andrewingram.net/posts/demystifying-graphql-connecti... The overall verbosity of a GraphQL queue tends to not be a huge issue either, because in practice individual components are only concerni…
Comment linking /posts/demystifying-graphql-connections/
on “REST vs GraphQL vs gRPC”never noticed that. did find someone who wrote some js to help: http://www.andrewingram.net/articles/undo_form_reset_script_...
Comment linking /articles/undo_form_reset_script_for_kids_who_cant_reset_good/
on “Making beautiful forms; Square and Recurly”The need for hitting nested “paged” data structures on first render isn’t that contrived, but I’ve never found myself needing to juggle the cursors, since you’re usually only hitting the first page for the nested ones. Loading subsequent pages would be a standalone query, rather than running the root query again with different cursors. (the example I came up with for this article a few years has a fairly realistic e…
Comment linking /posts/optimising-your-graphql-request-waterfalls/
on “Solving the double (quintuple) declaration Problem in GraphQL Applications”I think it depends on the project, but I've found that using installable libraries becomes a bottleneck over time as you find yourself running into their limits, or trying to customise them in ways they really aren't design for. I wrote something about it a few years ago when shadcn was relatively new on the scene https://andrewingram.net/posts/recipe-kits-a-great-alternati...
Comment linking /posts/recipe-kits-a-great-alternative-to-installable-libraries
on “Shadcn/UI now defaults to Base UI instead of Radix”
