Let's start 2023 !

WHO THE FUCK imagined that having language like YAML is a good idea ??

Fuck you and your spaces. No editor produce any decent errors messages except "Your spaces are wrong".

When you edit an Azure debops pipeline, it's just 5 min ti do thing, 35 minuites to figure ou where to add/remove spaces.

NO, I WILL NOT read 25 pages of documentation to add a single step into pipeline.

Fuck YAML !

covid is making life hard again. I can't just stop in the middle of a research project because I can't access the robots anymore. *makes angry noises* I already canceled a human study because of covid, so this feels super unfair.

but you know what pisses me off even more? the govt complaining about numbers being high but not doing jackshit about active disinfection of air and public spaces (China did that, btw) or providing cheap disposable masks for people.

Also, I'm not as much afraid of getting covid as I am afraid of giving it to the head of the department who is a 70+ yrs old genius in his own right.
Fuck.
Fuck.
Fuck.

... This is shit.

Why tf would you use spaces instead of tabs?

I didn’t even know that was a thing people do.

I just found out that I should be using 4 spaces and not a tab for indentation, MY WHOLE LIFE IS A LIE.

god... why is the stupid "tAbS oR sPaCeS?" still around, it's like some stupid ass HR person got it long ago and it's never gone away. nobody has used tabs to write or format code since like the 1950s when there were mechanical fucking typewriters! and if you use them today in your editor, you're WRONG

I will die on this hill.

Do not offer anyone to help them with their scripts, ever.
I had to do something as there were things like "cd $DIR; rm *". No checks if the folder got changed, no qutoes to prevent breaking on spaces. A problem waiting to happen. And it did. We don't know what the script deleted in the wrong folder to this day.
The scripts have no functions, some files have over 50% duplicate code. I was an idiot and thought running it through shellcheck and doing basic prevention of them shooting their own foot would be enough.
And there is no way to convince the guy to start writing the code properly. Should have kept my mouth shut.

Gotta love it when you try out a different VS Code extension for a specific language and then on each autoformat, more and more spaces get inserted.
IT LIVES!

JetBrains Fleet sucks!

It's absolutely gorgeous but it sucks, technically. I mean did nobody try to edit a YAML file with 2 spaces indent in there during development??

I wasn't even able to open a fucking project with it one time. And why in gods name does it go full macos with it's design?

Loving their IDEs, but da fuck's going on with this?

Wasted a day as Shitlock Holmes with the build chain.

It would not reproduce the firmware hexfile that had been checked in. Reverse engineering that along with the mapfile to find out the cause, it was a const string that was guarded by an ifdef from another file that was auto-generated as prebuild step via a script that fetched some version control info.

Or, it would have been if the installation instructions had been correct and someone had described that no spaces in the absolute path name of the project are allowed. Otherwise, that shit just failed silently.

I then had to reverse engineer the intended workflow from the commit history in the version control to figure out that the last dev obviously hadn't quite understood the project specific workflow and how the version control interacts with these build scripts.

At least, I finally did get a matching hexfile.

Is it just me or is GitHub Copilot having a stroke the last couple of days?
Usually it's amazing but lately it's been getting variable names, indentation, parentheses and more wrong.
It just wrote a line that is indented with 446 spaces xD
If this is some A/B testing, I want to join the other group pls.

I prefer three spaces-wide indentation in my code. This is unconventional to say the least, as many people prefer four or two spaces width.

This is why I use tabs — every developer that works in my company can do two clicks in their IDE to set the indentation they like, and I realize I must not force it my way with three spaces. Indeed, one of my colleagues prefer four spaces, and it took them less than a minute to set this up and not to worry about it ever again. To me, this sounds like a good alternative over arguing and finding a compromise that "everyone in the team are okay with".

This way, every developer who comes to my company at any time ever wouldn't have to get used to the indentation width standard that is different from what they're already comfortable with.

I want to live in the world where "convert indent" button in IDEs that replaces spaces with another spaces is dusty and abandoned. I met those who use four spaces, the most popular standard, who also thought everybody who disagrees with "The Standard" should change their ways. This makes me sad.

Ever encountered merge conflicts because of spaces and indentations :-|

Which movie or TV show do you think has caused the most damage and confusion about how programming actually works?

For me it's Silicon Valley with their "Tabs VS Spaces" scene where the dev who advocates spaces actually hits the spacebar key 4 times manually.

(In reality no does that - everyone just hits the tab key and most Editors convert the tab into 2 or 4 spaces bars on your setting. In fact a vast majority of github repos use spaces - despite some of their devs now thinking "I use tabs")

I wish there was more dedicated, physical spaces that were tailored to programmers in particular. I know there’s a lot of collectives out there, but it’s hard to implicitly discourage startup fiend management from taking it over it seems like. We should organize more around a common craft. Free mason type shit.

The debate between using tabs or spaces for indentation in code is a long-standing argument among software developers. Those who prefer using tabs argue that it takes up less space and is more efficient, while those who prefer spaces argue that it allows for more consistency and easier readability.

Many developers have strong opinions on this issue and believe that their preferred method is the only correct one. Some even go as far as to say that using the wrong method can negatively impact their ability to work with the code.

Regardless of which side of the debate someone falls on, it's a common source of frustration and humor among developers. The argument often devolves into jokes and sarcastic comments, with both sides poking fun at the other's preferred method.

Despite the often lighthearted nature of the debate, it highlights the importance of code readability and maintainability, as well as the differences in personal preferences and workflows that can arise within the tech community.

Tabs vs Spaces