Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
hakunin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
26 ms
·
331.
▲
by
hakunin
3y ago
Copying my comment from another article: This time I used VSCode for nearly 2 months. Thought it's the end of an era, I'm not coming back to Sublime Text. I decided to push through and customize the configs just right for me, it w
332.
▲
by
hakunin
3y ago
Rails and Phoenix when it's up to me, custom Go+React stack at work. I actually went 3 years building Phoenix projects (2015-2018) and went back to Ruby/Rails, because it's really hard to beat the ergonomics, low ceremony, an
333.
▲
by
hakunin
3y ago
I agree that some claims about e2e are misleading. That said, you could interpret "mathematically impossible" very charitably as risk assessment math. It's mathematically impossible to improve investigability while also impro
334.
▲
by
hakunin
3y ago
Generally: 1. NPR Up First podcast while brushing teeth. 2. This site for tech and adjacent nerdy topics. 3. Macrumors, 9to5mac, and various blogs via RSS. 4. Apple News+ subscription (that I got as part of Apple One) — check regularly for
335.
▲
by
hakunin
3y ago
I gotta admit, perhaps a bit naive of me, that the concept of "tech charlatans" didn't click for me until now. It's true, they are out there, and I see it now. I mean, I know there are phone scammers, but they probably b
336.
▲
by
hakunin
3y ago
I considered that, but couldn't find a way to precisely control amount of RAM used when you read from it.
337.
▲
by
hakunin
3y ago
Are you saying that the file would just entirely be loaded into a page cache eventually? I imagine, even if true, it still wouldn't result in OOM killing the server/worker daemons on account of this data?
338.
▲
by
hakunin
3y ago
>the data was fragmented in such a way that efficient lookup was possible Yeah, there's a build step that sorts and arranges data into "cells", making binary search possible. Not sure about kernel/user space. I'm
339.
▲
by
hakunin
3y ago
I'm no systems programmer, but I remember trying to research mmap approach. It's been 3 years, so I'm not sure what stopped me, but something didn't feel right. Perhaps it was the lack of control over how memory is used.
340.
▲
by
hakunin
3y ago
Not 100% what the article is about, just a short story. In one of my old jobs we had megabytes of infrequently accessed static key-value data. If we simply loaded it into a const (i.e. a hash table), it would blow up the RAM so much, that w
341.
▲
by
hakunin
3y ago
To be frank, alcohol, most drugs, and fat are not the same. Every time I go to a place where smoking is not culturally frowned upon, I can't make a few steps without inhaling vomit-inducing smoke. If it wasn't for this, then I wou
342.
▲
by
hakunin
3y ago
The truth is, this does happen, but you want it to happen less. Banks accept certain amount of risk due to logistical limitations, but always seek ways to reduce it.
343.
▲
by
hakunin
3y ago
This is a good explanation for Bitcoin-type ledger, but as far as I understand, banks don't share a global ledger. In US they run settlements through FED, which is the closest thing to global ledger we got, but internally they keep the
344.
▲
by
hakunin
3y ago
This is a checksum-like trick for manual record keeping, and isn't specifically relevant to the grandparent. It isn't required in digital world. The grandparent talks about having to write 2 separate transactions in 2 accounts in
345.
▲
by
hakunin
3y ago
In most cases microservices are an anti-pattern, because they are trying to solve problems that can be solved without incurring their complexity and sacrifices. However, I remember that Sagas originally were proposed to deal with multiple 3
346.
▲
by
hakunin
3y ago
The difficulty is different. Front-end is very capricious, idiosyncratic, inconsistent. You have to deal with lots of annoyances, puzzles. You still might have some connectivity responsibilities, like restoring a web socket connection, mana
347.
▲
by
hakunin
3y ago
You're the reason I wrote "split _almost_ perfectly". That said, looks like your history involves .NET -> Python/.NET. I went .NET -> PHP -> Ruby/Elixir/Go. It took me some time to withdraw from .NET b
348.
▲
by
hakunin
3y ago
What's missing here is the programming language. There are incredibly flexible, concise, low-ceremony languages, with implicit types where placing an IDE between you and code kinda obfuscates them. These are the languages where I think
349.
▲
by
hakunin
3y ago
How do you use stream deck in a typical remote work setting?
350.
▲
by
hakunin
3y ago
The first 3 sentences of the article are implying that the whole thing is written with "if you must" attitude. That said, a lot of companies have front-end teams, and those front-end teams commit years to building React components
351.
▲
by
hakunin
3y ago
Huge scale typically leads to the opposite: more backend generalization, not catering to a specific front-end. That's why Facebook built GraphQL — because they run on anything, like fridges, TVs. That's specifically an attempt to
352.
▲
by
hakunin
3y ago
> you need to make a ticket for the backend work first and the front end work can only start once the backend work is finished In practice, a lot of this can be done in parallel. Once the design is established, front-end can start workin
353.
▲
by
hakunin
3y ago
I'm suggesting to pass via JSON what we used to pass via HTML back when front-end was templates on the server. I still prefer those days, like I alluded to in the first paragraph of the article. It used to be: write your template by in
354.
▲
by
hakunin
3y ago
Have you looked at this from the angle of object constructor or function parameters? Let's say you build an object called Person. They have first_name, last_name, phone_number. That's what you probably will pass into a new Person.
355.
▲
by
hakunin
3y ago
Redesign: I've responded to the redesign argument in another comment. It's easy to find if you search the page for "rare event". Mobile app: this is addressed in the article. Naming: Usually most naming for different par
356.
▲
Reliable communication allows for simpler interfaces
(notes.max.engineer)
2 points
by
hakunin
3y ago
|
0 comments
357.
▲
by
hakunin
3y ago
Author here. Here's an additional piece of wisdom that I picked up in over 20 years of doing this. Reliable communication allows for simpler, less coupled interfaces. Unreliable communication demands increasingly elaborate and coupled
358.
▲
by
hakunin
3y ago
For reads and offloading front-end work, I think the article's approach should be good for your use case. Just make sure that your backend code is cleanly written. Create proper domain objects to represent pages that you will be servin
359.
▲
by
hakunin
3y ago
> showing the same data or exposing the same flows elsewhere in the application required nearly a total reimplementation on the backend. This created an explosion in size of the codebase and complexity. I'm trying to understand how
360.
▲
by
hakunin
3y ago
The "page" becomes the resource for reads. You get great scalability, because you can use your database in the most efficient way possible to provide entire data for the page. You can maintain 100% back-end clarity on what each pa
More ›