209 karma · joined November 8, 2022
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.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.
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.
I guess similar results might be possible with other accounting tool but Ledger perfectly meets my requirements. Also, it integrates pretty well with Emacs and I get to check my reports from there.
One other option is to use https://github.com/danburzo/percollate to convert a webpage to a nice document directly. I use both tools depending on my needs.
What is the rollback they are talking about? Is it in terms of something new in google chrome?
From what I can tell, they are looking for certain amount of ads 'injection' to come from chrome. What does that really mean? Does chrome really control the ads injected into the search results from google? I had assumed that was directly from google. Or maybe something happened in the recent chrome update that reduced the number of direct queries heading to google?
Also what's with the suggestion to increase the search box vertical space to increase in a search tab to make search prominent? That sounds pretty interesting to me.
* Learn how to make bombs (as mentioned in the article)
* Get away with committing crimes?
Are moderating these topics related to morality? - People in the gov who want to monitor the general populace for dissent
- Power hungry individuals and governments
- Governments wanting to learn about their foreign adversaries/allies
- People in the gov who want to monitor other gov agents for whatever reason
- Corporations wanting to learn about their adversaries
- Corporations wanting to maximize their profits
- Corporations wanting to learn about their users for whatever reasons
- And so on and on.
On the side of limiting access to user data - - People wanting privacy
Don't want to sound too pessimistic but I can't help it.I'd rather have them charge the $5 than be guilted into paying the $5 dollars as a 'tip'. Just makes the costs of these purchases more apparent.
Anyway, kind of feels like the eventual outcome of Capitalism. You have a lack of supply to meet the growing demands of the cyber-criminals and fellow entrepreneurs rising up to close that void. Given the amount of money involved, not likely to ever stop. Not trying to give them any ideas but I'm wondering if there will be (or already is) venture capitalists investing in them. They most likely already have a 'Hacker News' to keep up with all the latest developments.
According to the FBI, financial losses from cryptocurrency investment scams dwarfed losses for all other types of cybercrime in 2022, rising from $907 million in 2021 to $2.57 billion last year.
https://arstechnica.com/information-technology/2023/06/fbi-warns-of-increasing-use-of-ai-generated-deepfakes-in-sextortion-schemes/That graph places software engineers in the top-right quadrant, suggesting that they are predictable and "grammatical". However, I believe there should be a distinction between writing code and engineering. I would not classify software engineering as entirely predictable. For instance, while you could use a script to handle emojis with ChatGPT's help, it would be challenging to use the same strategy for a solution involving large systems that have multiple failure points and span multiple regions. Moreover, even if such a system were successful, multiple redundancies would need to be in place to prevent large-scale disruptions caused by downstream failures.
On the other hand, the chart places executives and investors on the 'safer' side. However, I think that with the real-time information available to AI, investing as a 'job' could be at a higher risk of being replaced. The same could be true for many executive positions (assuming that we are comparing merit-based positions to those based on nepotism).
>> The communists. Didn't work out well.
Just wondering why you would think your comment adds any additional context to the original post? Is that a snide at communism just because you dislike it? Or are you saying that communism is the only way to solve the problems of wealth disparity and that it has failed in the past and we can never have any semblance of equality in the world?
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.