Lots of people care because it creates e-waste.
If the culture changes so that all consumers act like that and forces the companies to change their production cycle, that would be a big boon for the environment.
Lots of people care because it creates e-waste.
If the culture changes so that all consumers act like that and forces the companies to change their production cycle, that would be a big boon for the environment.
I kinda disagree with you. Why would it be different from now? We know that people will die.
I’ve had good friends pass away at different times, and it hurts but eventually, I move on.
My only exception, with the knowledge I have today, is that I wouldn’t have any kids. That attachment is straight up reptilian brain and that would be way too hard. Otherwise, it would be okay.
There was a garbage article floating around that allegedly, Diddy has kept videos of all his parties and has dirt on a lot of rich and powerful people.
This is probably bullshit but one man can dream. That would be like fullfilling a kink.
It’s like recreating the vacuum of space with words.
PR talk needs to die a fiery death.
You got some serious reading comprehension issues. I am talking about you.
“akchually, there wasn’t enough racist comments”. One racist comment is too much.
The issue isn’t you doing your hobby projects however you want, it’s people being paid and produce LLM generated code.
And the biggest issue is managers/c-suites thinking that LLMs can replace senior devs.
And the biggest biggest issue is that the LLMs in their current mainstream form are terribly bad for the environment.
It’s rarely the case. You rarely work in vacuum where your work only affects what you do at the moment. There is always a downstream or upstream dependency/requirement that needs to be met that you have to take into account in your development.
You have to avoid the problem that might come later that you are aware of. If it’s not possible, you have to mitigate the impact of the future problems.
It’s not possible to know of all the problems that might/will happen, but with a little work before a project, a lot of issues can be avoided/mitigated.
I wouldn’t want civil engineers thinking like that, because our infrastructure would be a lot worse than it is today.
There is no issue here from Bitwarden POV, except the pushback they receive now.
Bitwarden got VC funding and the bell is ringing to bring the cows back in to be milked dry.
They are testing the water to see how people react, scale back a bit through whatever lies/PR, and will just wait for the right time to shove more shit.
This is a pattern we’ve seen over and over again.
That VC money was the start of the end. No reassurance can be trusted the moment a company accepts VC funding. It’s only a matter of time until Bitwarden makes their next enshittification move.
The direction that the company is taking. Clearly that Bitwarden feels like other open source projects are diverting revenue from them.
That’s a small step towards enshittification. They close this part of the software, then another part until slowly it is closed source.
We’ve seen this move over and over.
Stopping your business with Bitwarden over that issue sends a message that many customers don’t find this acceptable. If enough people stop using their service, they have a chance to backtrack. But even then, if they’ve done it once, they’ll try it again.
Your current price is 10$/year now. But the moment a company tries to cull any open source of their project is the moment they try to cash it in.
Do you have good resources to read on risc-v. I hear about it a lot, but haven’t found meaningful resources (to me) on it.
Thanks
Using Windows is terrible right now, but we’ve spent so much time using it that we developped workarounds and knowledge of the OS.
When you switch to Linux, it’s a different OS altogether, and that’s not counting the different flavors.
So yeah, all that to say that the pain and friction pass quite rapidly and you are left with an uncluttered OS (until you fill it up with useless crap).
Corpos have worked so hard at making the UX “seamless” that people aren’t used to fiddling with the computer anymore.
Yeah, that’s probably more the issue. We’ve seen too many times throwaway code become production code because “it works already, we need to move forward”.
Thanks for your input.
I think I would like to follow all these people and their work on C, and their in depth knowledge. But free time is sparse, and I don’t have the mental energy when I do have some time.
As for my work, I work in a startup where I am the only one doing what I do. However, I have a lot of leeway in how I code, so I am always somewhat read on best practices. So I can’t really refer to a senior dev, but I can self-teach.
I think I coded enough that a lot of what I do is a reflex, and I often can approximate a first solution,but I have doubts all the time on how I implement new features. That makes it so that I am a slower coder and I really struggle to do fast prototyping.
I am aware enough of what I do well, and what I struggle, so there’s that.
They can see how it’s done and code their own thing. They don’t have to cut and paste the code, just know how its done.
The dream of being the first to do it and corner the market for more of that sweet growth.
At least, we know emotionally that it will get better with the second one haha, even if the day to day is rought.
With the first one, it felt like we would never get to the other side of it. But we did and we will for the second one.
I am eager to learn new things, so having so little free time is definitely tough. And the lack of sleep/energy makes it even harder.
Thanks for the encouragement, it’s nice to be acknowledged by someone else that went through the same thing. We often forget that we are not alone and a lot of people got through it before us.
I work in a startup, so I’d say that almost every day, I learn something new. So I don’t really need to look in-between tasks because a lot of tasks bring new challenges.
When I worked in corpos, my job was restricted to the same tasks and specific knowledge. Now it’s the opposite where I need to learn what I need to create a feature or fix an issue.
I guess that lately, a lot of new things have popped up and I need to absorb a lot of information to implement the features I need. And that is probably what is triggering the imposter syndrome.
Thanks for the insight, it is appreciated.
Money happened.