louiskottmann

And you immediately lose the ability to do `crontab -l` on any server to know its scheduled tasks.

Now you get to look around the myriad of places where you can put systemd files, and figure out which ones are base services and which ones are custom, with no general convention to go about it. Nope.

History repeats itself : it ends in blood. Always does.

As the concentration of power happens, the people who concentrate it become bigger and bigger targets.

There is no alternative to wealth distribution.

This is borderline adversarial propaganda.

While the incident did happen, a lot of actions were taken and most of the data was recovered. OVH now also keeps backups even for clients that don't pay for it.

I was hit by that datacenter catastrophe and got my data back almost immediately, in a new VM.

I've been using them for years with little issue (no more than happened on my AWS or Azure accounts, I would say less because it's less of a mess in general).

Stop spreading false rumors.

That's my take as well, I find fixing poor/overengineered LLM code taxing.

The linked article does not speak of tests, it speaks of a team that failed to properly review an LLM refactor then proceeds to blame the tooling.

LLMs are good at writing tests in my experience.

The trick is in the mud between what's yours and what's theirs. The induced doubt is lucrative.

I find the thought daunting but the reality surprisingly easy.

You just keep up as you go, as long as you keep things close to the framework it's fine.

I've been a Rails DevOps and nowadays a web one-man-show with it for over 10 years and I'd do it again.

Not many frameworks have been thriving that long, and there's good reason.

It packs everything, is tidy and productive, with a pleasant language to read and write.

In the latest Stackoverflow survey, it's back at the "top 5 of desired stacks to use for next project" over a decade after its inception !

Give it a try.

You could get rich by solving ARC 2 tasks yourself instead of forwarding the work to an LLM, given a client willing to pay LLM rate.

People will find a way to not need as much RAM, and thus the devices that require it.

Same way the price of groceries going up means people buy only what they need and ditch the superfluous.

First of all, ruby-lsp does a great job at this, and the recent Herb helps with frontend templates.

This is enough to navigate between controllers, models and libs, unless you're trying hard to be clever which you shouldn't.

Then, in Rails, things have a canonical place in the codebase, that is consistent between codebases.

This is in contrast to languages and frameworks where every codebase is setup differently, but the static typing helps find code wherever it's hidden without pain, and thus without need for cleanup and thoughtful design.

To each their own, I prefer power for me, and pain for whoever drifts from the convention.

This is so obviously right.

I may add that investors are mostly US-centric, and so will the bubble-bursting chaos that ensues.

That's indeed a good example of prior full trusting of the browser by the server.

I appreciate that, but in the case of TLS or CSRF tokens the server is not blindly trusting the browser in the way Sec-Fetch-Site makes it.

This is a massive change for cache in webapp templates as it makes their rendering more stable and thus more cacheable.

A key component here is that we are trusting the user's browser to not be tampered with, as it is the browser that sets the Sec-Fetch-Site header and guarantees it has not been tampered with.

I wonder if that's a new thing ? Do we already rely on browsers being correct in their implementation for something equally fundamental ?

This is my take as well. I've never come accross a JS project where the built-in datastructures were exclusively used.

One package for lists, one for sorting, and down the rabbit hole you go.

As history showed us numerous times, it doesn't even have to be the best to win. It rarely is, really. See the most pervasive programming languages for that.

Gitlab has had that for a while, and it's very useful as in-between through dot targets.

i.e:

.scoped-env: &scoped-env

   key1: value1

   ...

Then further down you can reuse *scoped-env wherever you need.

You can also have anchors on individual lines and compose them. It's useful.

The author suggests using ad-hoc syntax, or meta-keys. Gitlab supports that [1] and I use them as well.

Different but also combinable uses, for various people. Nothing wrong with it.

1: https://docs.gitlab.com/ci/yaml/#extends

There a lots of gamers. Games like Baldur's Gate & Expedition 33, which satisfies your criteria, far surpassed those numbers already.

I know people who rewatch the same TV series every year and go to the same vacation every year.

Fear of change is deep.

I suspect it's a learning thing.

Which is a shame really because if you want something simple, learning Service, Ingress and Deployment is really not that hard and rewards years of benefits.

Plenty of PaaS who will run your cluster for cheap so you don't have to maintain it yourself, like OVH.

It really is an imaginary issue with terrible solutions.

That is stretching the subject beyond reasonable. Proprietary software as a general endeavor is not an invalid business and nobody is saying that here.

LibreOffice is close enough to Microsoft's offering that surely it makes sense accross the many EU states to stop spending millions on it, and spend a few to close the gap, saving even more millions in the future.

Chosing to pay millions when it is not necessary is definitely not a valid choice. It is at best stupidity, at worse corruption.

In my experience in the public sector in France, I have seen these decisions taken to advance someone's career.

For example, a first year free means a purchase person will get their promotion on incredible YoY progress.

There's frequent discussions about how sonnet-3.5 is in the same ballpark or even outperforms sonnet-3.7 and 4.0, for example.

Indeed, and with the technology plateau-ing, being 6-12 months late with less debt is just long term thinking.

Also, Europe being in the race is a big deal for consumers.

Heavy user and I moved to Atuin because of the shell history scoping issue with regular bash history.

No matter my config it would always glitch. Atuin is backed by a global sqlite db: problem solved. And unlimited history.

I don't use sync though, commands sent to 3rd party servers are a no-go.

I think the upside is that we stop spending limited human time on mundane/easy things and focus on higher-value pursuit.

Because you can no longer be a cheap artist, because you can no longer help students on easy problems en masse, because family businesses no longer need a webmaster.

That's a step in the right direction, maybe even towards UBI.

On growth, I disagree that we reached the plateau already. We won't fundamentally change things but larger context windows, speed, compute and cost? Obviously.

That in itself is a major evolution.

It looks like it is fading out of hype maybe, but that's just like all things. LLMs aren't going anywhere, just like Rails got version 8 out and it's better than ever.

It's not allowed, but you'd have to sue if you uncover one such questionnaire, which is a hassle.

So instead, lying on your answer is not sue-able. Which makes including such questions ineffective.

SEEKING WORK | Paris, France & OSlo, Norway | REMOTE

15 years of experience in tech, developing in all major paradigms, strong expertise in DevOps engineering, as a technical lead, a recruiter, good experience with CTO and COO positions.

I also work with another expert DevOps when my clients needs requires it.

- Do you want DevOps practices with a hands-on, pragmatic approach?

- Need realistic workflows for your developers to quicken release cycles, improve quality, tighten security?

- Wonder how to setup a technical team that delivers, from technology choices to recruiting the team, managing the tooling, and making that team time-resilient so you don't have to do it over and over again?

Let's talk!

Contact: louis@k-hops.fr

I would honestly rather not make any user's Chrome experience better than Firefox given the curtent marketshares. It would not feel ethical to me to partake in helping Google seize more power on browsers.

The big difference in my opinion is that your ad-hoc servers using static binaries, with all the outside stuff specific to your organization, are non-standard.

For some miraculous reason K8S is ubiquitous and everybody uses it. Standardization is a boon.

People complain about git using similar arguments, and yet having a vast majority of the tech world on it is a boon for tooling.

Both those technologies are excellent but take some time to master (you don't have to be an expert though).

I can get on a project using git, kubernetes and say RoR and understand it very quickly without help. It is well bounded. It takes a git account and a kubeconfig. All set.

A custom python codebase deployed on custom servers running in big enterprise-y network, not so much.