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.
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.)
"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?
> 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?
Yes, I switched to TiddlyWiki a year ago, and haven't regretted it. I tried Evernote, Notion, Org-mode, Dynalist, Zettlr -- and looked at Dendron, Roam, Obsidian and so on.
I think what separates TiddlyWiki and Org-mode from the rest is that they are easily "hackable" and have more powerful syntax, but are also more demanding on the user.
You can modify the UI and add features inside TiddlyWiki itself, using only TiddlyWiki syntax and Javascript. Like if you want backlinks to be displayed at the bottom of every note in a certain way, you can do that.
Markdown is a very limited language when you think about it. (Most of these tools would be better off using AsciiDoc.) TiddlyWiki's WikiText has macros and widgets that let you do things Markdown never will, and your "notes" can become interactive and dynamic.
TiddlyWiki allows you to create a very sophisticated, tailored system for managing lots of different things. But when you begin, it's a pretty steep learning curve, and you'll need to put in more work than when starting with Obsidian, of course.
The more code is used, the more bugs are found. So new code is expected to contain more unknown bugs than old, well-used code. But this is a function of usage, not of time itself.
Yep, me too! There is actually a link between high GI and sleepyness; orexin. It's a chemical messenger in the brain, and if you have very little of it, you have narcolepsy. If you have been injected or sprayed with a lot of it, you stay alert without sleep. Oh, and glucose inhibits orexin production!
My personal theory is that I have inherited a low base level of orexin, which makes me react with sleepyness to carbohydrates. I have no idea if this is accurate, though.
God has always wanted humans to "be perfect", if by that we mean without sin. We have always failed at this, and God has always gotten angry. This starts in Eden, and even Jesus told us to "be perfect" (e.g. see Sermon on the Mount), and was really upset at sinners _who did not want to change their ways_.
Romans 3: "... for all have sinned and fall short of the glory of God." Yeah, it's humanly impossible not to sin.
It is crucial to Christianity that humans are saved "freely by his grace through the redemption that is in Christ Jesus" (Rom 3), "and this is not from yourselves, it is the gift of God" (Eph 2).
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.