How to build apps pragmatically
alextoussaint.com
How to build apps pragmatically
1–10 of 51 posts
Re: How to build apps pragmatically
#2What are "Watcher Views"?
Re: How to build apps pragmatically
#3What are "Watcher Views"?
I think they mean the following. In Django, a view function, or view for short, is a Python function that takes a Web request and returns a Web response.
So a watcher view is probably a view that returns an extremely short response. It's just telling you whether more data is available, or not.
They mention websockets as an alternative that's far more complex.
Re: How to build apps pragmatically
#4Like I'm gonna take advice from someone whose personal website doesn't even work.
Re: How to build apps pragmatically
#5Like I'm gonna take advice from someone whose personal website doesn't even work.
What does not work exactly? Here, everything is as expected.
Re: How to build apps pragmatically
#6Re: How to build apps pragmatically
#7What are "Watcher Views"?
From the article:
"These are views that tell you when a model changed last. Watcher Views are light enough so that you can continuously call them to know whether you should fetch recent data. They're far less complex than WebSockets and avoid the performance costs of continuously polling unchanged data from the API."
Re: How to build apps pragmatically
#8Like I'm gonna take advice from someone whose personal website doesn't even work.
Please don't be a jerk on HN. You owe the community better if you're participating here.
https://news.ycombinator.com/newsguidelines.html
Edit: https://news.ycombinator.com/item?id=22064005 is another recent example. Continuing to post like this will get you banned here. Would you please read the guidelines and use HN in its intended spirit?
Re: How to build apps pragmatically
#9More often than otherwise, I’ve found code duplication preferable over abstraction. I only abstract code when I understand the problem space really, really well (I.e. have solved it before), or when I can have some certainty the wrong abstraction won’t cost me too much time to fix.
Re: How to build apps pragmatically
#10More often than otherwise, I’ve found code duplication preferable over abstraction. I only abstract code when I understand the problem space really, really well (I.e. have solved it before), or when I can have some certainty the wrong abstraction won’t cost me too much time to fix.
It does seem that this lesson takes at least a decade to internalize, and as such one can usually estimate the level of experience a person has based upon how much they embrace “DRY” as a hard rule vs a guidepost.