The problem is that Linux has memory overcommit and it will OOM when a process faults a page in, not just when someone allocates memory.
So the OOM condition can hit any random process, not necessarily one that just tried to allocate. If you don't have some sort of selection, then you would still have an OOM killer, only it will be killing completely at random.
In the Netherlands the law is pretty straigtforward that this is a bad idea:
> The "Nature of Employment" Rule: If you are hired as a software developer, almost any software you create (even in your own time) can be claimed by your employer.
We always advise our employees to request an exception for it. We are pretty relaxed about it, but we don't give out a blanket exception
The second example given (extracting information from a web view) is also weird. The rust code has the exact same flaw as the java code, which is that they do not validate the source. I think the author didn't really understand the underlying problem here. Bounds checking was not the issue with the java (android) code
I hate to impune their skills since I don’t know the person and this could just have been a hastily written and poorly thought through article, but for me it brings into question their claims as a cyber security expert with 10 years experience.
From what I understand, they only have to review/audit the times a gem was yanked, to see if it was a legitimate action. I reckon there is a lot less occurrences
If the syntax isn’t obvious without looking at the manual, you might as well use an actual standardized syntax. For months (without context, and where you need an absolute interval), I just interpret it as 4 weeks.
If the syntax isn't obvious, you should use however much verbosity it takes to make it obvious, because people will still ignore the standard and make mistakes.
if your manager is ok with it, don't register it as a sick day. Makes it potentially more complicated with the company doctor. Just consider it a workday spend on ...whatever. Manager being ok with it means you deserved it though :) (EU based engineering manager speaking)
In EU companies have to appoint a medical expert that checks worker's health (for free) upon joining the company, and routinely (1-2 times a year, depends on country I guess). Edit: Could be something that only companies whose workers have to do physical labour ("blue collar" jerbs)
If you call in sick for more than three days you usually go through your own doctor, so that you get a certification that you're taking X days off in order to cure yourself
It is compulsory at least for all companies over 50 people. There is a three level risk profile of the work the team does that assigns the respective doctor hours to the team. That is mostly for work related incidents or prevention as per the EU legislation.
For long term absence each country has different rules and paperwork.
I know the UK isn't EU any more, but I've never seen that before we left and I've worked in lots of companies in the UK, big and small.
In theory you should get a sick note after 3 days, because the government pays SSP (statutory sick pay) if you're ill, but in practice most companies pay you at your normal salary rate (if you're permanent, not per hour) and don't bother asking for sick note as the SSP is little more than minimum wage. Of course, this is in tech, I know that there are a lot of crappier jobs where employers trust their staff less, and I suspect in those industries the sick note is very much required.
We are using Clickhouse combined with GDPR's Data Deletion Requests. We store the user-ids in a separate system, and run the ALTER/DELETE statements once per week. Works pretty smooth, though I would prefer some more automation within Clickhouse for them.
Data for in-active users gets deleted because our clickhouse retention policy is lower than the in-active-user timeout
As a sidenote, I saw your talk on Clickhouse to the CMU database group [1] back when and was extremely impressed with your deep technical knowledge yet down-to-earth presentation. Still haven't had an opportunity to use Clickhouse for production work, but would welcome it.
Thank you!! That was the most fun I've ever had on a tech talk. Any Pavlo is a one man army when it comes to fun questions and there were more like him in the audience. The whole series of quarantine talks was great.
We recently setup Clickhouse on GKE using the Altinity operator (and signed up for Altinity support).
There's been so many queries where I've thought 'that's going to need a join and aggregation across tens of billions of rows, no way!' - and then Clickhouse spits back a query result in 10 seconds...
We are using Altinity too. Great support up to now. We are about to go live with it. For us (see my bio for company link) having a company manage the cluster was paramount. We just want to use the data and API, not manage the machines/VM's and k8s clustering stuff.
I think similar to other situations e.g Starburst with Presto/Trino. There really are a limited number of devs pushing a long the core projects and a lot of people needing support. Each start up in the space can likely grow the pie for support and adoption and a few big enterprises will still hire in house devs.
Don't know if op was indeed talking about ING, but their app was, for a time, very wrong on Android as they seemed to have rewritten it on a Cordova/Phonegap stack which subsequently tanked their rating on the play store. Looks like they have released a new native version since then - at least on the french store.
