3. Can be used in proprietary works
The license policy allow you to use this piece of code even inside commercial (not open source) 
projects. So you can use this software without giving away your own (precious?) source code.

Introducing the SQL Server 2022 blog series 

What is Authorization? Authorization Series - Pt 1 

The 2018 Succinctly Series Awards are coming! 

Video Series: Modernizing .NET Apps for Developers 

It can be useful to create console apps to support backend processes such as data anonymisation or batch processing. This post demonstrates how to develop console apps in .NET, including support for built-in help, arguments, configuration, logging, dependency injection, and more. 

Ever wondered how JWT came to be and what problems it was designed to tackle? Are you curious about the plethora of algorithms available for signing and encrypting JWTs? Or are you interested in getting up-to-speed with JWTs as soon as possible? Then this handbook is for you. 

A component licensed under LGPL can be used by closed source, proprietary software, both internally used and distributed, for free, with no effects on the software using the component. LGPL is not “contagious” in the same way as GPL, so it only affects the component under LGPL. As long as you’re only using official distributions of the component, it is free to use and free to redistribute. The only requirement is that you include a notice in your “about” page or similar that the component is used. 

Basic Things

After working on the initial stages of several largish projects, I accumulated a list of things that share the following three properties:

• they are irrelevant while the project is small,
• they are a productivity multiplier when the project is large,
• they are much harder to introduce down the line.