Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hakunin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
451.
▲
Maintainable Code Explains Itself
(max.engineer)
3 points
by
hakunin
5y ago
|
0 comments
452.
▲
Mindful Code Reviews
(max.engineer)
1 points
by
hakunin
5y ago
|
0 comments
453.
▲
Mindful Code Reviews
(max.engineer)
2 points
by
hakunin
5y ago
|
0 comments
454.
▲
by
hakunin
5y ago
In case anyone else feels that this article leaves enough wiggle room to accidentally end up with something like 015a described, here are the 3 rules I implied in answering the above post: 1. All structure and content goes to backend. 2. Fi
455.
▲
by
hakunin
5y ago
> if you have a person's profile picture, and you want to round it, should that be a property on the JSON structure? You can decide what to leave to frontend on a case-by-case basis. I would say unless people can choose if a picture
456.
▲
by
hakunin
5y ago
I think this is totally fine if you're willing to accept some performance trade offs in favor of productivity, you're staying mindful of limits and scoping, and just generally you're accustomed to living in the GraphQL world.
457.
▲
by
hakunin
5y ago
I'd argue that the difference between "we're changing schema for all callers" vs "we're changing schema for 1 page of 1 frontend that we fully control" is so profound, as to render that whole concern moot.
458.
▲
by
hakunin
5y ago
If everything on the page is slow to load, then I would agree. Twitter is such a crazy outlier that I can't even imagine what they have to deal with. In a usual case you'd get a rare 1-2 slow retrievals, and the rest of the page c
459.
▲
Don't build a general-purpose API to power your own front end
(max.engineer)
128 points
by
hakunin
5y ago
|
107 comments
460.
▲
by
hakunin
5y ago
Someone has to maintain an always-running listener for `/events`. If a server does that, and triggers client calls, we call that webhooks. If a client does that, and triggers internal functions, it's what the op describes. I think
461.
▲
CMS Trap (2013)
(max.engineer)
2 points
by
hakunin
6y ago
|
0 comments
462.
▲
A rubygem to look up data directly from disk
(github.com)
1 points
by
hakunin
6y ago
|
0 comments
463.
▲
by
hakunin
6y ago
I wrote about this a few years ago.[0] The gist to avoiding premature over-architecting is to keep sticking with as static/hardcoded behavior as possible to meet the requirements. Just make sure it’s well organized and cleanly written
464.
▲
by
hakunin
7y ago
How about git push heroku master from local branch?
465.
▲
Reasons Not to Implicitly Memoize
(max.engineer)
3 points
by
hakunin
7y ago
|
0 comments
466.
▲
Three Reasons Not to Implicitly Memoize
(max.engineer)
11 points
by
hakunin
7y ago
|
0 comments
467.
▲
by
hakunin
7y ago
People ate bats; Chinese government covered up the virus for a while; big US pharma wasn’t incentivized to research a solution; underinsured Americans were afraid to go to doctor; immigrants were afraid to go to doctor; US government just s
468.
▲
by
hakunin
7y ago
Latest update[1] says it's routing issues, which sounds less bad than what it could've been. [1]: https://status.heroku.com/incidents/1973
469.
▲
by
hakunin
7y ago
I can’t help but wonder if perhaps the helpfulness of a lot of these principles is different for people who can or cannot see/hear in their mind. https://news.ycombinator.com/item?id=19618927
470.
▲
by
hakunin
7y ago
Pick up the phone and stay silent until they speak. It should also help reduce incidence of scam calls.
471.
▲
by
hakunin
7y ago
I've seen your other projects from years ago, e.g. your bookmarks site. I think you have great ideas and skill. I appreciate the effort towards being no bullshit. May I suggest a no-BS approach that replaces highly subjective humor wit
472.
▲
Don't use docker to run your app in development
(hakunin.com)
2 points
by
hakunin
8y ago
|
0 comments
473.
▲
by
hakunin
9y ago
Some weird tricks that worked for me: 1. Hire a weight lifting trainer. I go 3 times a week, and I never have to think about it. The "not having to think" is important. 2. Get a standing desk. I don't always use it (especiall
474.
▲
by
hakunin
9y ago
Yes, a typical Elixir/Erlang application is a process tree with parent processes acting as supervisors to children processes. Each supervisor knows how to handle its children crashing, and properly replace crashed processes. They can d
475.
▲
by
hakunin
9y ago
Yes, connecting to any node connects you to all nodes. I have done exactly this in a production app.
476.
▲
CMS Trap
(hakunin.com)
1 points
by
hakunin
10y ago
|
0 comments
477.
▲
by
hakunin
10y ago
We went with good old Heroku and Redis for the real-time Elixir component. It isn't a full-blown OTP setup by far, but we just needed stable performance with many websocket connections, for which it didn't even break a sweat. We h
478.
▲
by
hakunin
10y ago
Hey folks, I am the back-end/infra dev on this project, AMA. It's built with a combination of Elixir/Phoenix, Rails, and React (+Native). If you'd like to work with me on stuff like this feel free to apply by shooting us
479.
▲
by
hakunin
10y ago
My thoughts conveying similar message from a different angle: http://hakunin.com/cms-trap (for those who might've missed it when it got upvoted on HN 3 years ago).
480.
▲
ElasticSearch gems and modules, clearly explained
(hakunin.com)
1 points
by
hakunin
11y ago
|
0 comments
More ›