nhoughto

13 ms·

121.
by nhoughto 5y ago
Interesting insights, my brain always goes to how to reduce inefficiency but there are many more things at play.
122.
by nhoughto 5y ago
Surprising, that seems very inefficient. As a bank offering a mortgage I have to set an interest rate for entire period? Naturally I’m going to be conservative to ensure profit.. which hurts the consumer. Variable or short term fixed rates
123.
by nhoughto 5y ago
Still feels like golang or maybe a 3rd party addition (not sure if that’s possible? Assume not) could just make a GC with a few more knobs, and would be a net benefit to the community. Every time I read about golang gc feels like the soluti
124.
by nhoughto 5y ago
yeah i don't see it as an attack and was very surprised Github suspended his account, less so that NPM unpublished the package. It is easy to think of these platforms as unbiased repositories, but as soon as something is deemed 'w
125.
by nhoughto 5y ago
Reminds me of a similar potential gotcha in Postgres https://www.2ndquadrant.com/en/blog/on-rocks-and-sand/ The linting story for postgres schemas isn't as good as it is in golang tho, so harder to autom
126.
by nhoughto 5y ago
Since when can you chargeback after 2 years? I thought it was limited to a couple of months?
127.
by nhoughto 5y ago
If you bind ec2 and have any access in docker you likely can GET from ec2 metadata endpoint and get sts creds, don’t need root for that.
128.
by nhoughto 5y ago
Yep, a migration script (if you have data you care about) is very important, it should be reviewed before being excluded. It has the power to blow away your data if done poorly. So having an explicit SQL statement (whether hand crafted or g
129.
by nhoughto 5y ago
very mature at this stage too, lots of good defaults.
130.
by nhoughto 5y ago
mostly dev dependencies, i guess you really pay the price for not having a compressed intermediate format like a JAR: - storybook is 420MB (! will look into this one!) - babel is 110MB - sentry sdk is 92MB (?) - aws-sdk is 63MB - typescript
131.
by nhoughto 5y ago
Tbh haven’t gone deep into it, now you ask maybe I should. It compresses ok, zstd to 240MB. React + react native, we lack etc tons of stuff. My guess/hope is mostly dev dependencies.
132.
by nhoughto 5y ago
I like the benefits but our node_modules is 1.9GB, def not checking that in. A Git bot that parses changes to yarn lock and comments with size/loc/files of all the deps etc, kinda like how coverage bots work. get all the observabi
133.
by nhoughto 5y ago
Ah ok sounds like a good setup, I could never get past the slow image pull times for systems like that though? Maybe I missed a setting. Containerd especially was quite slow at pulling images. Image of 2GB~ could take a couple of minutes to
134.
by nhoughto 5y ago
Yep Specially crafting a zip file can make it streamable but it’s not the general default. Can GNU unzip read from stdin? Not sure but I don’t think so?
135.
by nhoughto 5y ago
Yep true, generally baking caches into build images is a bit fragile tho, the more caches and different types of jobs you have the larger the set of combinations of images you need to cover it. Often ends up easier to decouple build image f
136.
by nhoughto 5y ago
One improvement that would be nice in gitlab is an extension / similar feature to the FF_USE_FASTZIP flag. The default way to cache things is zip, which no matter the compression isn't a great fit, you really want a format that is
137.
by nhoughto 5y ago
yep, we do a scheduled daily build with all caching off, to test that it all works without caching, and a good way to rebuild your caches without old dependencies/files etc. Good backstop.
138.
by nhoughto 5y ago
yeah it worked, as in the ecosystem was consistent with a single non-blocking pattern.. and then almost immediately went in 5 different directions around how to program around it.. callback hell, async/await, generators, promises etc..
139.
by nhoughto 5y ago
More mental overhead and tough ecosystem, you end up in the coloured functions problem where you choose to write non blocking code so now all your dependencies / libraries must too. Nodejs worked because it was like this from day 1 but
140.
by nhoughto 5y ago
Had the same thought, my experience with unity support is its a blackhole. Good that there are some good examples even if from times past.
141.
by nhoughto 5y ago
Lots of interesting nuggets in here, i'm also interested in the ASG driven db node replacement approach, has anyone seen any more info about the nuts and bolts of how this works? The idea of treating db nodes less like pets seems great
142.
by nhoughto 5y ago
how important was being able to disable postgres full page writes under zfs? that was almost a throw-away line in the article but could be really important for some pg workloads i'd think? certainly got my attention
143.
by nhoughto 5y ago
Interesting problem, I imagine many here grew up on computers not because it was valuable or strategic but because they couldn’t not, such was it’s draw. Learning the concepts by brute force was the norm, the idea of not knowing what a file
144.
by nhoughto 5y ago
Few interesting areas: - JS dependencies are a problem because of the sheer number, which is really because of all the authors of the dependencies and how they update, backwards compat or not etc. if you had 10 big things by 10 authors they
145.
by nhoughto 5y ago
“Minimum” secure product is interesting, I’ve definitely gone down the slippery slope of going too secure, and it doesn’t feel like the wrong thing at the time but looking back it slowed us down. Very hard to craft a minimum.
146.
by nhoughto 5y ago
yeah sorry i just made up 'mapped generic columns', my progression was trying to find a soln for immutable key/values (immutable enabling some different tradeoffs then others might have) where most of my values are bigints so
147.
by nhoughto 5y ago
Ah yeah it’s probably jsonb (duh). That’s not efficient, but sometimes you don’t care about that!
148.
by nhoughto 5y ago
Recently went deeep on efficient kv storage in postgres, there is an order of magnitude different in storage size between different approaches (naive skinny table, EAV, array values, mapped generic columns etc). I wonder what approach this
149.
by nhoughto 5y ago
Is an interesting topic and seems to have an interesting history, is there any good books on the topic? Something less academic and dry than I’d expect a floating point book to be but more all encompassing and accessible?
150.
by nhoughto 5y ago
yep this is fairly common where the original form-factor, a piece of paper/plastic card, was the target. The intent of capturing the name was to put it on the card, and long names can't fit so we have to truncate them or abbreviat

More ›