and NDAs should be limited to something like one year after your employment ends. no standalone "money for silence" contracts allowed of course. that would create a big incentive to keep your employees happy, avoid controversial projects like selling data to the military, publish or patent research instead of sitting on it and increase competition in all markets. could also help against sexual harassment.
Why event a year for a NDA? 1 month after leaving the company should be max. They are Meta, who cares what BS they are building to destroy peoples life's. There is no reason to keep these things secret. This is not MI6 or the CIA, its a massive corporation, they should not have any such rights.
Well they may think you should do extra work without extra pay, but you shouldn't think that.
If you want to grow the company, (and all companies want to grow), or new companies want to start, we gotta train new people. That means you, too. Knowledge transfer and good culture is how the industry changes for the better. Otherwise it's all the pointy haired ones exploiting useful idiots.
Yes, LSPs can supply a variety of refactoring commands (rename, extract to, inline, etc.) that the LSP server can implement directly, deterministically, locally.
I assume they meant a log like a WAL. A WAL should be (quite literally?) all you need for durable workflows.
A distributed WAL (to survive a machine death) would also probably be something I'd want, and … something I'm not sure you're getting directly from SQLite.
Folks this is meant to be an honest question, not a snarky comment. I'm not a DBA, I'm DevOps/SRE and logs for me always meant execution logs. I'm just curious if between those involved in database domain logs is used to refer to WAL.
I think the original poster in this thread was joking. A fair number of databases use "logs" as a core mechanism for storing and sorting data. "Logs" in this context is not to be confused with stdout/stderr output that you may collect from a running program and forward somewhere like Cloudwatch/Elasticsearch etc. "Logs" in the context of databases here refers to the data structure; which can generally be defined as simply an append-only "file" (I put file in quotes because just because something is a log does not mean it is necessarily written to disk yet - that's why write-ahead logs exist). It's not just write-ahead logs.
Google "Log-structured merge trees" if you want an interesting read.
Your comment is essentially borderline conspiracy theory that HIPAA is somehow setting up a surveillance state.
> As a government regime, do you want to build an effective surveillance system where health data on large numbers of suspects can be pulled into a data fusion system at the push of a button, once a judicial framework for rubber-stamping is in place?
Sure, and I'm right there with you that people should protest frameworks for judicial rubber-stamping. But HIPAA is like the only privacy law in America, basically, and having it mandate that medical data is encrypted can be good on its own.
While there are standardized formats for medical data, many are so ill-adopted that building some sort of surveillance system would be a monumental task; the bulk of data I've worked with has been in poorly documented, non-standard formats.
> Both of these are easier when smaller vendors are forced out and larger vendors are the only ones left standing
Clearer regulations and standardized, interoperable data formats benefit smaller players.
> It's clear that politicians don't get this from the way they talk about a "mere 1%" wealth tax. None of them would speak of adding a "mere 20%" to the income tax rate, even though that's mathematically the same thing.
Uh … sure I would? Why not? The top bracket was 70% in the 80s. So that 61% is still a fair bit short of what it was then. (And the 80s isn't the highest point, either.)
IDK if it would be a good idea or not, but I'd entertain the debate, certainly. To state that this is unarguable, though, well…
> Knowledge only cements itself in the brain when it's regularly referenced.
While true, this is a molehill, not a mountain, of a bar, like "coding once in a while". I'm doing mostly SRE work, and this syntax has no trouble sticking in my head, and I encounter it pretty regularly? (And heck, most of my work these days is in Python, so there I get the >=,< syntax and yearn for the ~mines~ caret, and I still recognize it?)
If you're actively developing a codebase, this definitely isn't going to be arcane trivia.
I'd argue that complaining about using combined "greater than" and "less than" operators instead of the caret is about the same size of molehill as complaining about the usage of it. Seeing either of them in dependencies at my job would be a pretty mundane event that I wouldn't bother trying to do anything about.
reply