I write better code everyday because yesterday code always looks bad haha.

Probably a mathematician or physicist somewhere.

I hate reading the code I wrote two days ago.

I tend to add is to booleans toreally differentiate between a method name and a status.

def open_file_dialog(self):
    self.dialog_file_is_open = True
    pass

That way, it’s easier for my dumb brain to spot which is which at a glance.

Have you tried to install Ubuntu recently? It is as straight forward as it is.

It is not a complicated process no matter how you look at it.

The process to install Ubuntu vs Windows is pretty much the same.

Create a user, choose a timezone, connect to Wi-Fi or LAN and wait for setup to finish. It is not complicated by any mean.

As I mentioned, most people never install an OS in their life, so they don’t know how to create a boot drive and install an OS.

So the issue isn’t that installing Linux is complicated, it’s that installing an OS on an empty drive is not a thing that the vast majority of pc users has done or will ever do.

It is easier more than ever to install linux today.

The issue boils down to the fact that the number of people that never installed an OS is pretty high.

Most people buy their laptop and roll with the OS installed. Microsoft paid a lot to be the default choice and we have the market we have today.

But if you check your email and browse internet, any OS will work.

The strength and weakness of Linux, is that there is many ways to skin a cat. But it can get confusing really fast, even if you are tech savvy.

Habits die hard and Microsoft and Apple were pretty good at capturing the market.

I agree, but we should always compare to what is better and strive for that. Otherwise we get the situation today where the argument to take a product over another is that it’s less bad than the old one

It’s not because you compare Teams to something worse that Teams isn’t terrible.

Yeah I was confused because you are right, merge is usually refered as the git merge and then git commit.

It makes sense. Thanks for the clarification

Thanks for the example. Rebase use is clearer now.

I have the bad habit of leaving checkpoints everywhere because of merge squash that I am trying to fix. I think that forcing myself to rebase would help get rid of that habit. And the good thing is that I am the sole FW dev at work, so I can do whatever I want with the repos.

How would rebasing my own branch work? Do I rebase the main into my branch, or make a copy of the main branch and then rebase? I have trouble grasping how that would work.

Thanks for the explanation. It makes sense. To my untrained eyes, it feels like both merge and rebase have their use. I will try to keep that in mind.

When rebasing, it applies the changes without the commit history?

Does that mean that when you fast forward your main/dev branch and commit, you then add a single commit that encompasses every changes that were rebase?

I know this is a meme post, but can someone succinctly explain rebase vs merge?

I am an amateur trying to learn my tool.

To me, RGB is like a cheap car with a bad paint job and too many neon. If I could put my computer in a closet, I would.

Vim is unintuitive. If you are a new linux CLI user and follow some tutorials that tells you to run vim, modify something then save and exit, it can be daunting.

Funny because HR doesn’t know either and its their job. In the US, you just need to slap engineer at the end and you are golden.

I think the esp32 maximum throughput is 700 kbps, so you might be able to get a better performance.

I don’t have much experience with the esp32, but the first thing I would do is just a spoof program that sends simulated inputs, and see how’s the latency without any other functionalities.

That will give you a good idea if the problem is your code or the stack (its not infaillible though).

Lots of people think that computers are magic box. And now a diffuse entity in the cloud talk to them? Big heads will gobble that shit up.