BadPirate

Name	Examples	Pay	Description
MANGA	Microsoft, Apple, Netflix, Google, Amazon	10	Top pay and benefits, user facing products, well known brands
Enterprise	Microsoft, Oracle, Salesforce, SAP, IBM	8	Software for buisness, solid pay and benefits
AAA Games	Tencent, Ubisoft, EA, Blizzard, Epic	7	Lots of eng wants to be game dev, so there is less demand, AAA Games often have long hours and less benefits
Startup	OpenAI, Stripe, Paypal, and others before they got big	5	Smaller company that hasn't proven themselves to the market yet but has seed capital and funding. Normally the benefits and pay are worse and they "make up" for it with stock options that could be worth a lot of money but rarely payout anything
Contract	Independent	4	Get on websites like fiv

	{
	"visitorId": "XVQAhCuHIopQPcx8f5qI",
	"requestId": "1662337931051.IdEq99",
	"browserDetails": {
	"browserName": "Chrome",
	"browserMajorVersion": "104",
	"browserFullVersion": "104.0.0",
	"os": "Windows",
	"osVersion": "10",
	"device": "Other",

	//
	// FoundationNetworking+AsyncAwait.swift
	//
	//
	// Created by BadPirate on 7/10/24.
	//

	/// Currently, Foundation that is used for servers (Like Vapor) has split out URLSession into FoundationNetworking, while it has support for async / await
	/// Generally, FoundationNetworking URLSession doesn't support the async/await helpers (like `data()` and `bytes()`) This extension will allow you to
	/// Use these as normal if FoundationNetworking is present, by providing an implementation.

	Copy the following file into `AGENT.md` and then execute the steps:

	```
	# Agent Instructions

	Intelligent agents will reference this file once at the start of a session if given as context and follow the instructions:

	1. Review #README.md, the README should describe the functionality of #codebase adequately, if there are _major_ differences between the functionality of codebase and the README.md make update to README, if there is no README, then create one describing the project.
	2. Review #CONTRIBUTING.md, and then #codebase, including any lint rules or developmement patterns established. Update (if there are major differences) or create CONTRIBUTING with a development style guide and rules common to this file
	3. For every commit or change you make to the file, before making the change make sure that it follows the rules in CONTRIBUTING document