cdaven

> The battery lasts for days as well, which you can't really beat.

The Garmin Instinct 2X's (and 3) battery lasts for 40 days in smartwatch mode, not counting the solar charging.

The Instinct is an "outdoor watch" with a monochrome display, but it has most features the Forerunners have.

Yes, it's still called "ASP.NET Core", even though ".NET Core" was renamed ".NET" from version 5 -- not to be confused with ".NET Framework 5", which was renamed ".NET Core 1.0" before launch.

Don't forget ".NET Standard" that could be used from both .NET Core and .NET Framework, until version 2.1.

First, Angular uses classes, and React supports class-based components.

Then, if you have converted lots of Javascript into Typescript, you have probably found several type-related bugs.

On one hand, this makes you (me) trust Typescript more, and feel safer knowing that your types are correct.

Later, you discover that a few of the declared types are wrong! You also still get "this" wrong in callbacks.

You could say that Typescript lets you try to get your types right, but you have to do the heavy lifting yourself.

Yes, I think Zapier is a B2B version of IFTTT.

> Where do you stop? If you assume Newtonian time, which extends back to minus infinity... well, what caused time to exist at all?

You stop at the uncaused first cause or the unmoved mover, of course.

The principle of sufficient reason states that everything must have a reason or a cause. This is not a principle to lazily toss aside to avoid some more difficult question, it is a foundational idea.

Our understanding of the world (aka science) is largely based on causality, and if things existed without any cause or reason, our understanding of "science" would probably be very different.

(I'm not a physicist, but this is how I understand things.)

For those people unfamiliar with this joke, watch the TV show Seinfeld.

There's also the lamp VINDKAST, which in English is "wind throw" or "flurry".

"The ultimate glue and scripting language" is taking it too far, I think.

I have loved Python too, but fell out of love a long time ago. Julia is much better in many ways, _in my opinion_.

Lua is a language that I have no experience of myself, but which is often embedded in things like this, because the interpreter is very small (if I'm not mistaken), which makes it convenient, and therefore in some ways superior to using either Javascript or Python.

Just saying that there are many opinions and ways to think about this.

When picking a git workflow, you should start with your system's and your team's requirements in mind. Don't just copy git-flow or GitHub's simplified version.

Not every team or system uses pull/merge requests at all. Some do pull requests to the development branch, and to master when releasing a new version.

In some teams, code review is the bottleneck, and a developer may have to create a new branch from a PR to keep developing while waiting for code review, then create a second PR that builds on top of the first.

This last workflow is the main reason why I'm opposed to squashing PRs. It just doesn't work.

Also, squashing my carefully composed commits with individual references to DevOps backlog items is insulting.

Commit messages should describe the change, not the code. This explains why the code was changed from whatever it was before, but not what the code does.

This can be important information e.g. when troubleshooting bugs, since it could explain the developer's thinking. Like in Chesterton's Fence; why on earth would you do something like this?

> Are "high-ranking managers" not classed as "leaders"?

You can be a leader without being a manager, and you can be a manager without being a leader.

> Ideally I'd want the team to be feeling guilty, because I'd argue it's the team as a whole that should have been responsible.

I don't agree at all, and this is probably where we think differently about leadership, and why you don't like the article's conclusions.

When the team fails, it's the leader's fault. When the team succeeds, the leader lets the team have the praise and the glory.

Listen to Jocko Willink's talks about extreme ownership on Youtube. He talks about this.

> Good "leadership" decisions in my opinion are really about good delegation and organisation of a team's resources, you shouldn't really be taking "lead" in any actual decision making

You're not talking about leadership, you're talking about "decision-making high-ranking (?) managers in the business world".

A good leader is someone who you want to follow, because you trust that they will do their best in guiding you (the team) towards your goal.

Wouldn't you rather follow someone who would feel bad/guilty for letting the team down?