Yeah but that time is long gone. Finance is throwing number in air of growth and profitability that must be met no matter what, and IT have to battle between what is effective, what the company tell them to do and what the users want, and in many case, the IT has a misplaced elitist attitude, like every user should know the infrastructure by heart and fix their problem themselves.

If a company uses other Microsoft products, chance are that Teams is bundled with whatever license they have. So for IT, it’s one less service to manage.

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.

“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.

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

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”.

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.

Through the different replies, I reflected on what I know and what I do for work and I feel like my skillset is more akin to a generalist/integrator, which is needed. But I also feel like everyone in my domain does that. Which might or might not be true.

I guess knowing our strengths and weaknesses is also a skill in itself and a little bit of self doubt here and there can help us grow and direct our knowledge in a certain direction.

Thanks for the insight.

I work in a small start-up where I am the only one doing what I do, so my epiphanies come from the struggles I have.

Other people I work with often have a blank look in their eyes when I try to explain some issues or what the code does because they don’t have the skillset to comprehend what I am doing. So this isn’t a path for me (yet, hopefully we can grow enough where we need more people in my field).

But I appreciate your experience. I will certainly think about a way to play in the innards of my language so that I can understand it better.

Thanks for the insight. I guess one thing that causes my imposter syndrome is that I want to know how everything works in details.

I agree that for other people, what I know seems like magic to them. It’s easy to look at what we don’t know, but we don’t take the time to appreciate how far we’ve come. We should do that more often.

The blogposts are the example I had because this is usually where I find my solutions.

I do understand that I don’t need an in depth knowledge of everything about my language, but I sometime feel like I should know more. But again, this is the imposter syndrome talking.

I am thinking about blogging once my kids are older and I have more time because I am grateful when someone else does and I want to contribute as well.

5 years professionally and I can find jobs, so yeah I must do something decent. But that imposter syndrome is strong these las weeks

I think I’ll never not make & &&, | || or = == operators mistakes. It’s so easy to go over it fast and not notice the mistakes.

I like developing MCU firmwares because there is limited amout of resources and you usually have direct control of what is running when.

I feel the better than many, but mediocre in my soul. I mean, I get paid to code, so I certainly have a good enough knowledge to do so. But I have the tendancy to undersell myself.

I think that one of my issue is that I’d like to be more knowledgeable to the smaller bits and bytes of C, but I don’t have the time at work to go deeper and I don’t have any free time because I have young kids.

My issue is with the imposter syndrome i’d say.

I don’t know asm on the tip of the fingers because today’s mcu are pretty full of features that makes it not useful most of the time, but if I need to whip up something in asm for whatever reason, I know the basics and how to search for documentation to help me.

I try to follow MISRA C guidelines because it’s pretty easy to follow and it gives tool to reduce mistakes.

I have enough experience to avoid many common pitfalls such as overflows, but for whatever reason, it always feel like I don’t know enough when I come across a tutorial or a post with a deep dive in a specific part of an embedded project or on the C language.

When I read these tutorials/posts, I understand what is being done, but I could not come to these conclusions myself, if that makes sense.

We managed before remote start, we still can manage now.

What will happen is that more manufacturers will follow suit, until it becomes the norm and every manufacturer does it.

So be ready to be inconvenienced or be ready to pay.

To moment we stop acting like these things are necessary in the real sense of the term is the moment we can find workarounds. Because we know damn well that this practice won’t be legislated.

I sympathize with everyone that lives in cold climates because I do too and it fucking sucks having to heat the freezing car, but be ready to live without the feature because it will definitely be behind a paywall soon enough.