plugins VS awesome

Plugins

You can ease your pain by using plugins. Some are already built for the most common problems (check them out in the official Serverless Plugins Github repo), but there are always some project-specific issues that plugins can help you resolve. Fortunately, writing a plugin for the Serverless Framework is easier than you might think.

Before getting started, you need to install the plugin. This is hosted on the Serverless Plugins registry, so you can install this via the plugin install command which is introduced since v1.22.0.

service: functions useDotenv: true provider: name: openwhisk functions: autoai: handler: handler.autoai parameters: api_key: ${env:api_key} events: - http: POST /autoai # extend the framework using plugins listed here: # https://github.com/serverless/plugins plugins: - serverless-openwhisk - serverless-dotenv-plugin

The plugins are built by the Serverless community. Anyone can create a plugin. The Serverless Framework company lists plugins, but only a subset are "approved." This means we should be cognizant of what we are using.

In the days before "google it" was a synonym for "find it", we had different curated link sites, and even pyhsical magazines with hand-curated lists of links that people interested in a certain topic might find interesting. This still exists today in some forms, for example the "awesome lists" that you see for some programming topics, for example https://github.com/sindresorhus/awesome .

Just like there was a time when 90%-99% of all email traffic was viagra spam, I imagine in the future most of the internet by volume will be AI-generated trash, and those in the know will still circulate lists of where the other 1% can be found.

An even brighter scenario is that someone, maybe a kid tinkering in their garage, figures out how to make a search engine that finds the good stuff, doesn't immediately die to AI bot farms' SEO efforts, and is financially viable.

2. Awesome Lists

Software Engineering Blogs

He appears to be the original creator of the “Awesome X” repo: https://github.com/sindresorhus/awesome

Awesome React

I'm just going to leave this here: awesome git repo

You don't need any particular requirement to consult issues section on GitHub. If you need a place to follow along this post, my chosen repository for today's blog post is Awesome.

I have an awesome list GitHub repository that needs a few icons & a banner made. I was wondering if any students in graphic design would be willing to commission a few for me? I'm willing to pay either hourly, or by the project and can pay cash or venmo. Note that the art will end up as CC0, so you'd essentially be waiving any right to the artwork.

yah, come to think of it in the curated space, this reminds me of that awesome X family of github pages. Looks like someone compiled a bunch of them here https://github.com/sindresorhus/awesome#databases. I have found those to be highly valuable treasure troves pregnant with rich and relevant information.

10. Awesome