i take you have never heard of the V-model. basically you climb the waterfall back up to verify everything. most things that fly within the atmosphere are done that way. pretty sure NASA would do the same.
i take you have never heard of the V-model. basically you climb the waterfall back up to verify everything. most things that fly within the atmosphere are done that way. pretty sure NASA would do the same.
that article is horrible to read! every paragraph starts with quotation, but then never closes it😵
this is obviously talking about their web app, which most people will be using. In this special instance, it was clearly not the LLM itself censoring the Tiananmen Square, but a layer on top.
i have not bothered downloading and asking deepseek about Tiananmen Square. so i cannot know what the model would have generated. however, it is possible that certain biasses are trained into any model.
i am pretty sure, this blog is aimed at the average user. while i wouldn’t trust any LLM company with my data, i certainly wouldn’t want the chinese government to have them. anyone that knows how to use (ollama)[https://github.com/ollama/ollama] should know these telemetry data don’t apply to running locally. but for sure, pointing it out in the blog would help.
as @damnthefilibuster@lemmy.world already mentioned: GitLab CI
Jenkins is a CI application from before CI was cool. GitLab CI is integrated and can trigger on certain events. Additionally you mentioned, that you want to publish on a public repo anyway.
You are probably are comfortable with containers. So GitLab CI should be easy for you to learn - as it pretty much starts up a container to do certain tasks. I’ve seen suggestions for Kubernetes, which for sure is the more mature solution. But i would question, whether you need the added functionality and complexity of K8s for a home setup.
To gain access to your local network, you can use the runner for a secure connection (as described by damnthefilibuster). or you could SSH into the machine, as long as you have it in a DMZ. Drawback is that you have to be more sure about your network infrastructure. Benefit is that it is a more general approach. Obviously you need to store all certs, keys and preferably even addresses in secrets, not the .gitlab-ci.yml
.
As you can see from this thread, there are many ways which lead to rome. My advice is to start with something simple and lightweight, which you understand. adding complexity down the road is easier, than removing it.
It really seems like we are looking at two sides of the same coin.
The coin has already ben tossed. Let’s see on which side it will land - I certainly hope it is the one you described.
I hear you. During the reddit exodus i left without having an alternative and stumbled upon lemmy much later. So i am fine going back to not having social media. However, a social network only survives if there is enough content. And if we are honest, lemmy barely has enough content.
Ill give you an example: I like climbing and there is !climbing@lemmy.ml with roughly 2 posts a month and !climbing@sh.itjust.works with less. I am happy to see something about my hobby twice a month. But all my friends still are on reddit, because two posts a month are not enough to them.
If you click on my profile, you will find 4 posts. I am a natural lurker, like most people on the internet, i read, vote and maybe comment. These posts, i made them because i wanted to add some content to this platform. While facebook is federated, there will be much more content. We can see theirs, they can see ours. Sounds like a win-win, right? But it may also make lemmings dependent on facebook content. If there is always more than enough content to endlessly scroll, I don’t need to upload my stuff to the network. However, if facebook pulls the plug after a long time, that leaves barely any content here and lemmy is basically dead.
I would probably still be around: Angrily clicking on some link about random big corpo, once a month smiling because someone shared a picture doing the same hobby as i. But for sure there are still people on old XMPP instances, while motivated dev’s reinvented XMPP: Matrix
from https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html :
In 2013, Google realised that most XMPP interactions were between Google Talk users anyway. They didn’t care about respecting a protocol they were not 100% in control. So they pulled the plug and announced they would not be federated anymore.
Basically keep people from using all the other platforms. Then stop supporting them. Similar like .docx never quite works in the open document editors. At least i refuse to believe that OSS devs are less skilled and motivated.
I agree with you, that even the devil would run away from localised scripts.
Just pointing out that even if everyone is using English, there will be differences. These differences can make it hard enough - no need for more stuff on top.
Even if everyone is using English, there will be cultural differences. I used to work at a company which had a lot of indian externals working on their code base. Whenever I had to work on a mainly Indian developed project i had to get used to how they wrote things. Usually things where named a bit different. Not by much, but enough tho throw me off a couple of times before i got used to it.
IMPORTANT: I am not shitting on how they used English, merely pointing out that they used it differently from how i would have expected.
You guys are funny. If you don’t want to see ads, use adblock. Now SO is a free platform for people that want to contribute.
as someone who has made it through multiple ‘agile transformations’ in large companies: that’s how it usually goes.
however, that is the problem with people being stuck in their way and people afraid of loosing their jobs. PO is usually filled with the previous teamlead (lower management, maybe in charge of 20 ppl). PM & Sales have to start delivering unfinished Products! how else are you going to get customer feedback while you can still cheaply change things? A lot of the middle management has to take something they would perceive as a ‘demotion’ or find new jobs entirely - who would have guessed that with an entirely new model you cannot map each piece 1:1…
Given these and many more problems i have seen many weird things: circles within circles within circles, many tiny waterfalls… some purists would call SAFE a perversion of agile.
the point is: if you want to go agile, you have to change (who would have thought that slapping a different sticker won’t do it?). the change has to start from the top. many companies try to do an ‘agile experiment’: the whole company is still doing what they do. however, one team does agile now - while still having to deliver in and for the old system…