BVR Project Yaml Convention
The Work
Work in Progress
This is a WIP, please be aware.
Continuing from our work yesterday, here is the yaml standard we've reached:
About 4 min
Charles Schwab
Manager, Software Development & Engineering
International Gaming Technology
Senior Site Reliability Engineer
Fire, Well & Tree
Self Employed Freelancer
Sundaram
Senior Developer
BVR Project Architectual Revisions
The Work
Here we've defined the core work below. We've found we cannot implement this with autogen RAG chat alone, as our data doesn't contextualize well in its current design. Additionally the latest module doesn't support the latest enpoints.
About 1 min
Designing the BVR Creation Process from Requirements
WIP
this article is a Work In Progres(WIP). It'll change at my discretion.
- Part I Specification
- Part II Requirements
About 8 min
Enhancing Small Business Entrepreneurship with AI-Powered Business Analysis
Part I specification... that was part 1, this is part 2.
Business Need Statement
Executive Summary:
In an increasingly competitive business landscape, the lack of precise and thorough analysis prior to launching a venture often leads to failure, wasted resources, and missed opportunities. Our proposed solution, inspired yet significantly expanded from the existing model of DimeADozen.ai, aims to leverage the power of Generative AI (GenAI) to provide aspiring entrepreneurs with a comprehensive, multifaceted evaluation of their business ideas. This digital platform, through its GenAI agents, aims to simulate expertise across various domains essential for business success, thus aiding in a data-driven decision-making process.
About 2 min
Using Generative AI to Test Business Viability
Spec / Reference
Gen Specification Model
instruction:
context: Automatic Context Embedding
query: <query>
About 19 min
Examining Technical Processes for GCP
In your role as an architect, you'll be involved in numerous technical procedures, some of which were covered in earlier chapters, like continuous integration/continuous delivery (CI/CD) and post-mortem analysis. This chapter will delve deeper into these and other processes like software development lifecycle management, testing and validation, and business continuity and disaster recovery planning. Our aim is to present a comprehensive understanding of these technical processes, with an emphasis on their connection to business goals. For a more technical exploration, including the use of tools like Jenkins in CI/CD, please refer to the subsequent discussions.
About 25 min
Analyzing Technical Processes for GCP
Architects are involved in many different types of technical processes:
- Continuos Deployment
- Continuous Delivery
- Post-mortem Analysis
- Development Lifecycle Planning
- Testing
- Validation
- Business continuity
- Disaster Recovery(DR)
About 8 min
Architecting for Reliability
A reliable system is one people can get to now. Reliability is the probability a system can be reached and used without failure and Availability is a measure of how available a system is to be used within a given period of time.
Cloud Operations Suite
About 18 min
Architecting GCP Solutions for Security and Legal Compliance
Identity and Access Management
Identity and Access Management or IAM is a service which lets you specify which users can perform which actions in the cloud. IAM includes the following objects:
- Identities and Groups
- Resources
- Permissions
- Roles
- Policies
About 16 min
Architecting GCP Network Solutions
OSI Model Layers
- Physical, the actual metal, wires, electrons and plastic ethernet plugs. You'll find wifi's radio frequency here because radio is physical phenomenon. In Quantum networking this layer are the entangled particles and the equipment uses to read and write to them plus the equipment used to connect to that. Voltage is sometimes the physical layer in Ethernet Over Power. With tin cans on a string, this layer is the cans, string and the vocal vibrations traveling through them.
- Data Link, ARP, Mac Addresses, Collision avoidance. This is broken into two mini-layers, the first is media access control(MAC) and the second is Logical Link Control(LLC). The second acts as a negotiator between the MAC layer and the third 'Network' layer.
- Network, this is where IP Addresses live. Keep in mind these network layers are the layers of a packet sent over the network. This is the base layer for packets. A packet is data encapsulated in a route with source and destination addresses.
- Transport. The protocol that makes this process work known by all networking devices speak is Transmission Control Protocol(TCP) or User Datagram Protocol(UDP). The Protocol identifier stored in a packet lives in this layer.
- Session, this layer manages handshakes. An SMTP connection timeout would exist on this layer. TLS handshakes happen here. An https packet is fully encrypted, so a request to a server asking for a url cannot be understood unless it is decrypted, then it can be seen. Inside layer 4 lives an encrypted layer 5 envelope in the case oF HTTPS connections. Layer 5 is the encrypted data, while layer 6 is the decrypted data.
- Presentation, A GET / request is in this layer. Mappings of network resources to application resources in the OS kernel happen at layer 6.
- Application, This is the later applications connect to in order to do networking. A webbrowser fetches web pages from this layer. This layer one might consider a data format. A TXT file vs a Json file. Mime types exist at this Layer. Layer 7 in the packet is the raw data unenveloped by network dressing that tells the network about it.
About 12 min