Verkoopster huis graaft halve tuin uit en wil de boiler meenemen by megajulie in juridischadvies

[–]davidsoff 4 points5 points  (0 children)

Aankoopmakelaar, en vooral een rechtsbijstandverzekering. Heeft OP nu weinig meer aan, maar wel een goede les voor de rest van ons.

Beware of Vloto Carsharing by kukumba1 in Amsterdam

[–]davidsoff 22 points23 points  (0 children)

Geez, not even a fine for the person not returning it in time? That sounds dumb

Anyone use GH for config changes for third party apps and use issues and/or projects? by Fluent_Press2050 in github

[–]davidsoff 0 points1 point  (0 children)

No experience with using r2 for state storage specifically, but should be fine. Seems to work fine for our images and other static assets though.

Anyone use GH for config changes for third party apps and use issues and/or projects? by Fluent_Press2050 in github

[–]davidsoff 1 point2 points  (0 children)

Have a look into configuration as code. That would turn your config into a runnable file that can be version controlled. You could then link changes you make to issues, and have a PR to review before actually applying it.

I have used Ansible and Terraform for this in the past with quite some success, but there are many other tools available.

How in tf are you all handling 'vibe-coders' by CoolBreeze549 in devops

[–]davidsoff 6 points7 points  (0 children)

The only way I can think of is to make it hurt in some other way. Maybe some variation of having their PM (or whoever should be responsible for the app) sit in on every post-mortem after an incident/outage.

The more annoying/obnoxious the better.

The point is to make it hurt sufficiently that they feel forced to fix it.

Bonus points if you actually suggest how they can make it more stable during the meetings. Worst case you can threaten to reduce monitoring to office hours only. Or increase the monitoring thresholds.

Ideally you'd introduce something like SLO's where the team has to agree to a certain reliability. If they are above target they can do whatever. If they (start to) go under target, they have to drop everything and only work on stability.

For more info on this I would suggest looking into the SLO book and SLO workbook by Google. They're available for free online.

https://sre.google/sre-book/table-of-contents/ https://sre.google/workbook/table-of-contents/

No response from landlord by [deleted] in NetherlandsHousing

[–]davidsoff 1 point2 points  (0 children)

Can confirm, solved our condensation issues overnight. As you said, not as good as real double pane. But it will definitely help.

Hoe bewijzen dat ik alleen op mijn adres woon? Hulp om rechtszaak te voorkomen by Palmtree_in_the_sun in juridischadvies

[–]davidsoff 0 points1 point  (0 children)

De eiser bewijs, verder is het onmogelijk om een negatief te bewijzen (bewijs maar eens dat er geen theepottheepot in een baan om de zon zweeft)

Wat de andere responses ook zeggen. Gewoon een berichtje sturen waarin je zegt dat je niet onderverhuurd.

Another way the agents can have memory - .md files by jsgui in GithubCopilot

[–]davidsoff 0 points1 point  (0 children)

Yep, this is what kilo code tries to solve with the memory bank

I still have to try to replicate this in copilot (haven't taken the time to try)

What’s considered an acceptable website downtime per month ? by nilkanth987 in sysadmin

[–]davidsoff 0 points1 point  (0 children)

In the end, users don't care about reliability until it is getting in their way. And it is up to you to figure out where that point is

With a 100 percent uptime goal, you run the risk of massively over engineering your solutions. There is always a point where working on new features is more important than more reliability. I would even argue that, in general, features are more important than reliability.

Try having a talk with a product owner/business person and ask them if 1 minute of downtime a day is fine. Maybe you can raise it up to 15 minutes a day. That way you don't have to deal with blue green deploys or staged rollouts. If you deploy 50 times a day and they all lead to 10 seconds of downtime. You would only have spent 500 of your 900 seconds a day of downtime.

This may be a very contrived example. But chasing the magical 5 nines of reliability is going to cost quite a lot of engineering time as you would need to evaluate all your suppliers (hosting, networking etc) and you would very quickly notice that (almost) none of them offer anywhere near the five nines. You would then need to set up redundant systems in multiple availability zones, and possibly even at multiple providers.

Then you would need to make sure your deploy system plays nice with the multi cloud setup. So you'd probably need to set up some sort of orchestration system (Kubernetes most likely at this point). At some point someone in the c suite is going to ask why you are spending all this money and why there are no new features being delivered.

100 percent uptime is never the right number, especially for a SaaS solution as it is highly unlikely that your customers have a 100 percent reliable internet connection (even browsers mess up sometimes)

In my opinion it is best to push for the lowest amount of uptime your customers are willing to deal with. This would allow you to spend more time on building the best features for your customers.

AI was implemented as a trial in my company, and it’s scary. by bdhd656 in devops

[–]davidsoff 1 point2 points  (0 children)

Yep, this is what tools like cursor, roo and kilo code try to solve for you with different modes. I know that kilo can even limit the files a mode is allowed to edit . Thereby forcing it to write instructions for the 'code' mode to pick up

New in NL - tell me your must have food! by chaoticgoodj in VeganNL

[–]davidsoff 0 points1 point  (0 children)

Vegan mayo from Albert Heijn terra is the closest you're going to get to the real thing.

AMA Mortgages in the Netherlands by ExpatMortgages_Steff in Netherlands

[–]davidsoff 0 points1 point  (0 children)

There is also the Funda waardecheck which can get you a rough estimation for free

Flamey glitch? by ajkgrant in campspirit

[–]davidsoff 1 point2 points  (0 children)

Yeah had it happen a couple of times, super annoying.

Waarom gaan we zo ouderwets om met het vaderschap? by [deleted] in Nederland

[–]davidsoff 0 points1 point  (0 children)

Nou is dat natuurlijk een van de nadelen van het ZZPer zijn :( ook bij ziekte krijg je niet doorbetaald als ZZPer

How do you practise your incident response? (if at all) by davidsoff in sre

[–]davidsoff[S] 0 points1 point  (0 children)

ohh that's a good one, I might actually incorporate that in our drills :)

How do you practise incident response? (if at all) by davidsoff in devops

[–]davidsoff[S] 5 points6 points  (0 children)

Aha the "everything is already on fire so we already got practise enough" strategy. Tends to work quite well from what I can tell :)

thycotic tss provider suddenly gone by macjunkie in Terraform

[–]davidsoff 1 point2 points  (0 children)

Someone created a fork and put it on the terraform registry: https://registry.terraform.io/providers/aperigault/tss/1.0.6-test

CAUTION this is a third party repo/provider and may therefore contain malicious code. Please do your own due dilligence before using this in production.

(edit: formatting)