julik

8 ms·

61.
by julik 1y ago
FBW with servo delay, manual trim that you do not use often etc. would be a severe problem in a situation like this, especially for a guy who was captain on an IL-76 (where the yoke is the size of a cab truck steering wheel and has direct f
62.
by julik 1y ago
Super impressive!
63.
by julik 1y ago
The OG voice messages.
64.
by julik 1y ago
"8h" is "a decent 9-to-5 workday". Then you sometimes have overtime...
65.
by julik 1y ago
Anthony is building MarketMonkey - https://www.youtube.com/watch?v=XPYLx1RtvAU Autodesk Flame is a great example of fixed-layout high-density UI - (look for tutorial videos and screenshots). Maya, Houdini - most apps from t
66.
by julik 1y ago
That movie is absolutely excellent in all too many aspects, but the one I like most (and most relevant for the HN crowd, I think) is the politics in the business. Thanks to amazing script and stellar performances you get it all: * Unfair bl
67.
by julik 1y ago
I'd say having the luxury to say "No" to things is underrated, and it does come packaged with small teams.
68.
by julik 1y ago
This rings true, but I also saw a lot of situations where just as spaghetti was being tangled, the few folks who resisted it were overruled, again and again. This is hardly the property of languages or frameworks - just orgs being orgs and
69.
by julik 1y ago
I have worked on quite a few Ruby web apps and built quite a few myself. Maybe 3% of the cases I encountered were about Ruby not being performant enough to do what I needed it to do. Where did the rest of the productivity of end users get l
70.
by julik 1y ago
This is a great presentation/article, thank you for posting it since I haven't seen it go by elsewhere. What holds me, personally, from Sorbet is the fact that it tries (unwillingly) to dictate which features of Ruby are "bad
71.
by julik 1y ago
You do need to keep tabs on whether they are or not, that is true - and you will have a bit of management to do if they are under constant heavy write load. For me, this all works out because I don't have too many tenants - and I have
72.
by julik 1y ago
Thanks!
73.
by julik 1y ago
Much appreciated! --humbly signed-- a fellow admirer of Geert Van Schlänger
74.
by julik 1y ago
I wouldn't say so, with use cases I saw the databases of tenants would almost never exceed available memory. A database could be loaded into memory in its entirety for the duration of the request, provided the disk IO on the server is
75.
by julik 1y ago
That is true, but in my experience this is less of an issue if your migration allow running against "current - 1". If your migration borks on one of the tenants - your system should still work, and you can grab that tenant and inv
76.
by julik 1y ago
That is what most tenanting scale-ups do. "Jumbo"-tenants get relocated either to separate partitions, or to partitions which are more sparsely populated.
77.
by julik 1y ago
Something like that, yes. A tenant that hasn't been opened yet - well, you create the tenant first, and then proceed "as normal". With ActiveRecord, your `pool:` configuration defines how many database handles you want to kee
78.
by julik 1y ago
The "hard problem" with DB tenanting is drawing the line where your "common" apex DB model begins, and where the tenanted data ends.
79.
by julik 1y ago
Kind of, yes. If you are going to be doing this at scale, you will either need to pin servers to shards of users, or retrieve the DB from some durable storage "just in time", or... use a network mount. Note also, that with small-e
80.
by julik 1y ago
That would be the FD limit, divided by 3 (the DB itself, the shm file and the WAL).
81.
by julik 1y ago
And these are exactly the ones I'm using here ;-)
82.
by julik 1y ago
Good point. Also: nothing makes it impossible to apply migrations to multiple tenants in parallel, this is pretty much only IO. I didn't have to since my tenant numbers were very low, but very doable.
83.
Shardines: SQLite3 Database-per-Tenant with ActiveRecord(blog.julik.nl)
255 points by julik 1y ago|75 comments
84.
by julik 1y ago
I haven't been in the business of writing WAFs, but if I got an assignment of "block every string in the request body that contains /etc/passwd or /etc/hosts, including filenames in multipart forms" – I wo
85.
by julik 1y ago
So that's why immediately when I hear "WAF" I read "...and the site will break in weird and exciting ways due to arbitrary, badly developed heuristics outside of your control, every odd day of every even week" - I r
86.
by julik 1y ago
"Who signed off on your WAF rules" would be a great reverse interview question then.
87.
by julik 1y ago
This is what surprises me in this story. I could not, at first glance, assume that either Substack people or Cloudflare people were incompetent. Oh: I resisted tooth and nail about turning on a WAF at one of my gigs (there was no strict req
88.
by julik 1y ago
Ok so: there is a blogging/content publishing engine, which is somewhat of a darling of the startup scene. There is a cloud hosting company with a variety of products, which is an even dearer darling of the startup scene. Something is
89.
by julik 1y ago
I agree that JSX is a mistake, but I disagree with the "separation of concerns" part. The "separation" is useful when we know that separate people are going to be editing and changing the presentation versus the UI code.
90.
by julik 2y ago
I'd say these days the support is pretty decent across the board, if you can limit your app to a relatively modern set of evergreen browsers (or at least - to the versions from "2 years old or newer").

More ›