When I need to quickly understand what a license means, I look it up on: TL;DR Legal
Here's the TL;DR of the MIT license: https://tldrlegal.com/license/mit-license
It breaks it down so at a glance it's easy to understand what you are allowed to do, not allowed to do, and how attribution works.
I'm a big advocate of open-source software, and believe that open-sourcing your work is an important way to give back to those that follow in your footsteps, an act of corporate stewardship.
Because I love open-source so much I used to use a lot of plugins and libraries and free-to-use snippets in my work, but after having worked for a number of companies who later sold their product (or themselves) to another company I've had to retroactively sign releases claiming that 100% of the work I did on the project was legal and all code is 'owned' by myself and the original company, and that I would personally take legal liability after making this statement so if there ever was a dispute about ownership of the code.
After signing those a few times I prefer to do clean-room implementations of ideas, and work mostly with my own code. I still believe in open-source, but for me the licenses make it tricky to work with a lot of OSS code.
For my own releases, I have been using MIT because it seems very liberal. In the future I might go full 'Public Domain' for stuff I release just so there's no possible confusion.