gbalduzzi

I like that sub-commands usually have a different --help output

git --help

git add --help

The former returns general information about the whole git executable, while the latter returns specific details about the add command.

It also gives an immediate intuition of entering a whole different flow that can not be composed with other flows, something that you don't have with --args There is a hierarchy between commands and options that is not expressed when both use the -- syntax

> Teams is a very generic product name. Microsoft can live with the consequences of that.

Quite the contrary, Microsoft earns free advertisement from this. The problem is for the people that misunderstand the heading, not for Microsoft

Ok, you would understand it correctly even the Zoom example. So?

Heading should be optimized for the most possible amount of people, there is a clear possibility that a lot of people misunderstand the title, so why not simply edit it? In that case neither you nor anyone else would understand something wrong

I found this interesting article.

Nothing particularly new, just a bit more detailed on explaining why all websites at the top of google searches look the same

What kind of newsletters are you subscribed to

I don't think this relates to Apple case.

Apple doesn't allow other stores to exist on their ecosystem. That's a problematic monopoly, because competitors can not exists.

That's different from what you are saying: other companies are allowed to create smart thermostat and compete against Nest

Google storage for a personal account is 15gb if I'm not mistaked, why would you need 1tb?

Isn't Ilya removed from the new, current board?

Chess AI is not machine learning as in "it watched thousand of games and extracted some patterns to be good".

It basically explores all possible moves and all possible countermoves and selects the best one. Of course it is extremely well engineered and optimized, but this is the main concept.

As a consequence, it does not to be "trained" on a dataset with odds to play without a piece.

You still have to calculate the distance between a date on the DB and a date on the client, the timezone difficult issues are not sidestepped at all

Well, being the middle man is kinda the manager job. The situation you describe happens when the manager does a poor job and is both submissive to the business requests and unable to comprehend technical issues.

Ideally having a competent person acting as the middle man for most daily operations is desirable though

The article does explain the comparison, and it doesn't mean that it's fun.

These are the actual comparisons:

> You interact with people from all corners of the world.

> You complete tasks on different online platforms (Slack, GitHub, VS Code, Google Docs, etc.).

> You have a list of your main quests to complete (you can find them in your journ… Kanban board!)

> There are also side-quests to take care of (“Hey Damian, could you take a look at this bug?”).

> Sometimes you can gang up with your teammates to slay a big beast (“Hey, I have this nasty bug that I have been working on for the past few days. I know you have better knowledge of this particular part of the repository, could we jump on a pair programming session?”).

> And you get to level up once in a while!

That is just an expression of the LaTex problem though.

People (as in, the majority of people) will not be comfortable using a tool that is so unintuitive and hard to use that you need to use an AI to help you in writing.

Writing a document is not supposed to be hard and require assistance to do.

But until you don't know something, you can't use it and, most importantly, you can't understand that you need it.

Like, how can you understand the tradeoffs between react, svelte or vanilla js until you have a basic knowledge of them?

The whole thread is about web development though, React Native is not web development. It's app development in React/JS, there are similarities but it's definitely not web development

If a user is using your web application normally and ends up with an error, it is an application error. Be it a 401, 403, validation error, 500, 429, whatever, it is not an actual user fault but it is a problem within the application.

Once you have this realization, what's the advantage of showing the proper error code to the user? Whatever it is, it's not in his power to fix it

Well, instead of writing this for every button in your web app:

<button class="bg-indigo-600 px-4 py-3 text-center text-sm font-semibold inline-block text-white cursor-pointer uppercase transition duration-200 ease-in-out rounded-md hover:bg-indigo-700 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-indigo-600 focus-visible:ring-offset-2 active:scale-95"> Button </button>

You can write this:

<button class="btn btn-primary"> Button </button>

The utility is pretty clear to me

There simply is no incentive whatsoever of using them correctly. I try to use them correctly but aside from the time spent in deciding what each element should be there were no differences at all

I completely agree that here are lots of great developers without a public figure.

However, having one gives the interviewer some additional insights about you. While no candidate should be discarded for not having public code, I don't think dismissing it completely without even looking at it is correct, because you are discarding a great source of information about a candidate.

Note that the insight could even be negative (such as a candidate applying to a senior position with sub-par public code recently written)

You can also pay way less for engineers outside of the bay area

It avoids having companies (mastercard / visa) as digital currency middleman, taking a cut for every money you move.

I think it's not about going completely classless, but about having sane defaults and only use classes for specific components and/or elements that really need a custom style.

The more traditional CSS libraries provide ton of classes, and your html is filled with classes for the basic styling.

Jira is awfully slow though, saying "it could be faster" is an understatement.

The "better Jira" that I dream of is simply Jira but faster and with a better UI, I don't have issues with the underlying process

> Even when you do all your analytics inhouse with self-hosted matomo, if you want to use a cookie, you need consent is what the lawyers say unanimously

If you use a cookie for Matomo tracking than yes, you need consent. You are using a cookie for a non essential service (analytics), so you need to ask consent.

But you can use Matomo as cookieless: https://matomo.org/cookie-consent-banners/

If matomo gathers data without a cookie, you can still use technical / essential cookies without consent.

As an example Github.com, owned by Microsoft, does not have a cookie consent popup and sets at least 5 cookies as soon as you open it:

- color mode (dark / light)

- user timezone

- whether the user is logged or guest

- a session cookie

- _octo, that I don't understand.

It's even more simple, the people who like a more modern UI don't like (and therefore don't use) Hackernews and its UI

I would hate and never use an utility app that requires me to constantly physically connect my devices in order to keep data in sync.

To avoid the problematic and frequent situation described in the comment I was replying to

The ticket should be assigned to a specific name, so that it can not be sold on a secondary market.

The Ticketing service itself should provide a channel to sell a ticket at its original price if someone wants it.

In Italy that's the method since a similar fiasco happened years ago and it works pretty well

The request type is just an example, of course, building up from the example in the comment I was replying to.

Can you provide an example of two primary button stacked near each other in a good design?

It's not about which action is highlighted and which action is not, it's about not having two primary action near one-another which goes against any UI/UX theory and best practice

No, it's about picking the option more coherent with UI and design best practices.