For all comments saying that it is a standard and shouldn't be changed, I think the standard is that the first "menu" is the important one, no matter how it's called, so for this reason it should really be changed.
Imagine if you move the file menu to the middle. Will you still be quickly able to find it "because it's a standard" or instead click the new first menu (and then spend several minutes trying to find where the "New window" option is)?
Why would you add a new first menu? And what about the first one being important motivates changing the name?
There should be a positive case for any change. Some reason the new name is better, more useful, more intuitive. But I haven't seen anyone describe this yet, here or in the blog.
But...there is a solution that works (although it may be a bit confusing at first).
A toggle with two buttons, dark and light. Both cannot be pressed at the same time, but both can be unpressed at the same time. That's the auto mode, and the ui can be tweaked to show a little label in between or below.
In auto, none of the buttons is pressed (and preferable a small label that says auto is shown). Pressing dark/light will force that mode, enable that button and remove the auto label.
In dark/light mode, you can press the other button to enable the other state. Or you can press the current button to disable it, and switch to auto. This last one is the confusing-at-first interaction, but makes sense if you think about it (it's like saying: I want dark / I want light / I don't care)
If you have to preface an idea about its potential confusing nature, that should be a warning that it might not best serve your users.
In my opinion, the existing UI widget that solves this problem best is a plain old group of radio buttons (auto, light, dark). Two checkboxes that interact with each other and also a sometimes-hidden label is something new for users to learn and also more complex to implement and maintain.
Usually the but me a coffee button is there because there are people that asks for it. Like, they do want to give you something, and often they ask you for a way to do so.
That button is for them, for those who want that button, if you don't just ignore it! Nothing bad will happen and the author is (usually) not expecting anything.
Mi primer lenguaje de programación fue Logo (el de la tortuga) en español. Estuvo bien para aprender, y puede que ahí sí tenga algo de sentido, permite que los niños entiendan mejor lo que están haciendo, incluso si el inglés les cuesta.
Para ámbitos más profesionales coincido con el resto de comentarios: un único idioma (y el inglés ganó la batalla) es preferible.
If we follow the same logic.
If today is may 2026, and you want to do something "next September", are you referring to september 2027? After all, months are also grouped in years.
The fact that "next [X]day" skips the one on the current week is arbitrary, and probably more confusing than if it didn't. If people you are talking to understands that, go on, but otherwise keep in mind that "next [X]day" is confusing and you should clarify or say it differently
Similar with salary. If you want a raise, you need to ask for it. It's sad, but that's what it is. (I'm aware of some companies that do raise the salary annually, and there is also the performance benefit if you have it, but I don't think that's common).
That, and the "you need to change companies frequently (at most one each year)" are the two things I always say to people on a computer science career.
> Letting an LLM write for you is like paying somebody to work out for you.
This. This is the big distinction. If you like something and/or want to improve it, you do it yourself. If not, you pay someone else to do it. And I think that's ok.
But I guess some people either choose a wrong job or had no other option. I'm happy to not be in that group.
As a forced mac user at work (always used windows or Linux) the number of modifier keys is really confusing. On pc you use control almost for anything, alt for very special cases (when usually control is already taken) and the windows/meta key for os-related things.
On mac a lot of shortcuts use command, but some use control, and there are a bunch that use option without a real reason why, my memory really suffers from this.
The only common thing between the two is that the fn key is only used for the special modifiers under F1-F12.
I was given a magic keyboard, and my plan was to replace it with a standard one, but then I found about the keys mapping from Karabiner, and the fn key is exactly at the control position...so I started remapping.
Now, I can do almost everything with fn+key. Fn+c=command+c, fn+s=control+s and so on.
Imagine if you move the file menu to the middle. Will you still be quickly able to find it "because it's a standard" or instead click the new first menu (and then spend several minutes trying to find where the "New window" option is)?