• 3 Posts
  • 86 Comments
Joined 2 years ago
cake
Cake day: August 26th, 2023

help-circle
  • 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…






  • 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 @[email protected] 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.


  • The main angle is not to ‘poisen’ the training set. it is to waste time, energy and resources. the site loads deliberately slow and produces garbage, which has to be filtered out.

    as i said: not a silver bullet. but at least some threads where tied up collecting garbage painfully slow. as the data is useless, whatever their cleanup process is, has more to do. or it might even be tricked into discarding the whole website, as the signal to noise ratio is bad.

    so i would still say the author achieved his goal.