thisisthenewme

mese scorsodiscuss

i feel like ai would be very beneficial here. use ai to create massive amount of fake facebook accounts with fake picture and fake friends. meta wants all the data so we give them more than they would ever care about. make it impossible for them to really know real from fake.

thisisthenewme

mese scorsodiscuss

When a researcher discovers that smoking is damaging to the lungs, do they need to provide a solution that allows people to smoke without damaging their lungs? Would their inability to provide a solution take anything away from the research?

thisisthenewme

2 mesi fadiscuss

potentially to stop bad actors from poisoning datasets by just adding the filter to real pictures?

thisisthenewme

2 mesi fadiscuss

I have a new personal policy of avoiding any products that advertise to me blatantly. Yes, use these trucks, force me to watch the ads and help me avoid these products forever.

thisisthenewme

2 mesi fadiscuss

As a developer, I kind of feel like this all smells like job security.

After using LLMs for a while, I have to admit it's pretty nice, and I like using it. I've been vibecoding a few apps, and it's a good dopamine hit to immediately see your ideas come to life. However, based on my experience, it will bite you if you trust it blindly. Even in my vibecoded projects, it keeps adding "features" without me asking for them. Since they're just pet projects, I don’t really care as long as the end result is what I'm expecting, but I don’t think companies will be as flexible. I also don't think customers would like it if features changed or got added with every new fix or update.

So this could go in a bunch of different directions from here, but to summarize the current situation:

    A lot of companies are heading in this direction.
    Without proper engineering, AI will easily write more code and potentially change the application unintentionally.
    We will have fewer junior engineers entering the market because of fear around AI and reduced hiring.
    AI usage will hit a critical point where it is making massive amounts of changes, and the people "prompting" it might start getting overwhelmed.
    We will end up with more features that people have to keep in their heads. I don’t think we can trust LLMs 100%, and because of that, developers will still need to know exactly what the application does.
    Eventually, there will be a lot of bugs, and developers will complain that we need additional human resources.
    Hiring starts again.

I think, right now, the toughest position is for new developers, and the best position is for people already in the market.

thisisthenewme

3 mesi fadiscuss

Migrated from archlinux to nixos. I don't think I can use anything else now...

I have a CI at home that builds my nixos config on a weekly basis with the latest flake. The artifacts are pushed to atticd. With this setup, when I actually need to update my machines, its almost instantaneous.

thisisthenewme

5 mesi fadiscuss

My unproven theory is that agent skills are just a good way to 'acquire' unspoken domain rules. A lot of things that developers do are just in their heads, and using 'skills' forces them to write these down. Then you feed this back to the LLM company for them to train on.

thisisthenewme

7 mesi fadiscuss

I guess it's pretty much impossible to stop these companies from gathering data, there's too much money in it, it's too easy to implement, and there's no cohesive force to stop them. I'm wondering whether a crowdfunded effort to feed fake data into these systems would work so we overwhelm them and make their plans a bit more difficult.

thisisthenewme

2 anni fadiscuss

I feel like AI is already changing how we work and live - I've been using it myself for a lot of my development work. Though, what I'm really concerned about is what happens when it gets smart enough to do pretty much everything better (or even close) than humans can. We're talking about a huge shift where first knowledge workers get automated, then physical work too. The thing is, our whole society is built around people working to earn money, so what happens when AI can do most jobs? It's not just about losing jobs - it's about how people will pay for basic stuff like food and housing, and what they'll do with their lives when work isn't really a thing anymore. Or do people feel like there will be jobs safe from AI? (hopefully also fulfilling)

Some folks say we could fix this with universal basic income, where everyone gets enough money to live on, but I'm not optimistic that it'll be an easy transition. Plus, there's this possibility that whoever controls these 'AGI' systems basically controls everything. We definitely need to figure this stuff out before it hits us, because once these changes start happening, they're probably going to happen really fast. It's kind of like we're building this awesome but potentially dangerous new technology without really thinking through how it's going to affect regular people's lives. I feel like we need a parachute before we attempt a skydive. Some people feel pretty safe about their jobs and think they can't be replaced. I don't think that will be the case. Even if AI doesn't take your job, you now have a lot more unemployed people competing for the same job that is safe from AI.

thisisthenewme

4 anni fadiscuss

This seems a bit scary because of its potential impact on me as a Software Developer. On the other hand, I'm also very excited to use this in personal projects and for learning. At least at its current state, however, it doesn't seem all that trustworthy. I was trying to see if it can give me good answers to queries that I've been unable to find with Google. For instance for query "How can I generate a kubernetes token that can be used to access a cluster?", it replied with answer for kubeadmin which is reasonable because I didn't give any context. I'm using k3s so I needed an approach that worked with it. I followed up with "Is there a specific command to do the above in k3s?". It responded to that with the following.

  Yes, k3s is a lightweight Kubernetes distribution that includes a utility called k3s-kubeconfig that can be used to generate Kubernetes tokens. k3s-kubeconfig is a command-line tool that is included with k3s, and it provides various subcommands for generating and managing Kubernetes tokens and configuration files.

  To generate a Kubernetes token with k3s-kubeconfig, you can use the token generate subcommand. This subcommand allows you to specify the token's expiration time, as well as the authentication groups and usernames that it should be associated with.

  Here is an example of how to use the k3s-kubeconfig command to generate a Kubernetes token:

  k3s-kubeconfig token generate \
  --ttl 24h \
  --groups system:bootstrappers:kubeadm:default-node-token \
  --username kubelet-bootstrap

  In this example, we use the k3s-kubeconfig token generate subcommand to generate a new Kubernetes token. We specify a time-to-live (TTL) of 24 hours using the --ttl flag, and we associate the token with the system:bootstrappers:kubeadm:default-node-token authentication group and the kubelet-bootstrap username.

  Please note that this is just an example, and you may need to adjust the k3s-kubeconfig command and its flags according to your specific k3s setup and configuration. For more information, you can refer to the k3s-kubeconfig documentation or consult a k3s expert.

I was initially impressed because after all my Google searches, I had never learned that there was a `k3s-kubeconfig` tool. That excitement quickly turned into amusement because turns out the tool doesn't exist.

comments