tinix

24 ms·

241.
by tinix 9y ago
FWIW, I routinely throw many GBs of pickled dataframes into Redis all the time, and then cluster the workload between multiple processes that are coordinated as a sort of namespaced job queue, all via Redis pubsub, blpop, l/rpush, and
242.
by tinix 9y ago
> The observed effects include ptosis of the eyelids, relaxation, drowziness, the feeling of pressure at a centered spot on the lower edge of the brow, seeing moving patterns of dark purple and greenish yellow with the eyes closed, a ton
243.
by tinix 9y ago
I'm still waiting for github to release some machine learning api that suggests bug fixes or possible changes based on changes-sets derived from github issues. They are sitting on SO MUCH DATA...
244.
by tinix 9y ago
Sorry, I can't edit my post now, and I just realized I copied the wrong link for that first reference: [0] http://www.ams.org/notices/199903/zworski.pdf Resonances in Physics and Geometry Anyway, to further e
245.
by tinix 9y ago
I don't know how to make it much simpler, but I'll try to ELI5 for you. Geometry has a direct relationship to resonance[0]. If you can target the specific resonance frequency of the capsid, you can destroy it with a wave form. If
246.
by tinix 9y ago
Mmmm... geometry. Resonance. So you take this known and documented knowledge of lipid mechanics[0], and apply that to geometry of pathogens. Very much like electroporation[1] but, with magnetic fields and RF instead of direct application of
247.
by tinix 9y ago
Just because it quits working doesn't mean you don't still own it. Might wanna lay off the green leaf, bro. Hahaha
248.
by tinix 9y ago
None of your points are derogatory to MongoDB in particular, any more-so than any other database. Your points are wholly reflective of bad implementors and their implementations, not to the underlying technologies. If one misuses a tool, th
249.
by tinix 9y ago
Using AWS is the problem here, and that's why it's so expensive. You could do this on bare metal WAY faster and more efficiently, and then you own the hardware forever, for the price you paid to do it for a month with a third part
250.
by tinix 9y ago
Most of your points are ripe with folly. 1. ORMs are slow, but generally they are worth it, and it's trivial to dive into raw queries when needed for performance reasons. 2. Mongo supports relationships, not sure what you're tryin
251.
by tinix 9y ago
THIS, so much this!!!! I'm working on overhauling (rewriting, from scratch) a project right now where the previous developer decided in his infinite wisdom that using ES as a database was a good idea. I have tried repeatedly to explain
252.
by tinix 9y ago
Man, people just looooove to link 5 year old blogs about fault tolerance, meanwhile that isn't even relevant anymore, and honestly, it wasn't relevant at the time either, because changing the write concern is trivial. The real nug
253.
by tinix 9y ago
Call this hilarious if you want, I think it's rather cool, thanks for the pointer. Once this is out of beta it will definitely be useful, if not already.
254.
by tinix 9y ago
I just wanted to say thanks, for taking the time to dig into this recent issue: https://gitlab.com/gnachman/iterm2/issues/794 in regards to IO lag that is pretty relevant to this discussion. I was pretty surp
255.
by tinix 9y ago
As someone who has lived and spent a lot of time in both very humid and hot areas, like South America and the Southeastern US, and as someone who has also lived in the PNW... I have to say, you simply need to accept that you simply don&#x27
256.
by tinix 9y ago
Why do you all act like one party needs proof, but only because they are refuting what was said originally, also, without proof. Neither is providing proof, so asking one party for proof and not the other is obviously absurd.
257.
by tinix 9y ago
Preregistration of clinical trials causes medicines to stop working http://chrisblattman.com/2016/03/01/13719/ ...nuff said
258.
by tinix 9y ago
There is no schema change, that's the point. You just don't get it... but that's okay.
259.
by tinix 9y ago
1. Change model code to add the new field, test, and commit it to version control. Then it's merged to staging, where it's tested in a production-like environment with a recent production data snapshot. After that's approved,
260.
by tinix 9y ago
You are setting up a comical hypothetical situation in which the developer is blundering through their job in a mindless inept manner. I'll just stop you right there. No amount of best practices, process, or tooling will fix an incompe
261.
by tinix 9y ago
The models live in version control. It's that simple. If your data structure is changing so often in such a way that you need to keep a history, then I'm afraid you have some fundamental problems that no amount of tooling or proce
262.
by tinix 9y ago
> Just out of curiosity, have you had to maintain/modify any of these apps over these years and years? Absolutely. > If so, without any schema changes? Usually, to be honest, yeah... Core, basal units of any given business proces
263.
by tinix 9y ago
> So where is your data model enforced if not in your tables? It's enforced... ...in the models. :P
264.
by tinix 9y ago
If you're leaning on migrations often, with SQL, then I think you should not be using SQL, obviously (or you're just doing something wrong) Or, one should use a SQL database that allows more abstract data types (like JSON blobs in
265.
by tinix 9y ago
Data structure, both storage, and in-memory, are very much a part of architecture.
266.
by tinix 9y ago
Oh please, tell me how I'm misinformed? If you need a migration library because you added a column to your database, then you have a serious problem. If you need a migration library because you don't know how to write SQL, then yo
267.
by tinix 9y ago
I dunno what to tell you without specific details about your application and environment in general. Clearly, you need a better system architecture if you're having to do migrations constantly.
268.
by tinix 9y ago
Yeah, pretty much. Haven't had a problem yet where I needed automated migrations, and I have been doing this for years upon years upon years. Like I said, if you're leaving heavily on migrations, you're doing something wrong.
269.
by tinix 9y ago
> I'm not sure why you put quotes around migrations as if it's some alien, obscure or weird feature. If you've never written a web application that needs migrations then you're not writing the kinds of applications (o
270.
by tinix 9y ago
> The benefit of having your admin business logic wrapped in REST endpoints is that you are writing and testing all your admin logic the same way as you write and test all your other endpoints. You write all your business logic in REST e

More ›