“Which decision will you make? Microservices as a Game Theory Game is next door. See you in class…”
Building Microservices
Created on 2024-04-03 19:01
Published on 2024-04-03 20:16
#teacherplanning #creditsforhours
In honor of spring, Easter, and all of the wonderful wildlife that exits out there, like these bees in the picture above, we’re going to start with microservices for a computer.
Why?
Because that’s what these lovely creatures do. The pollinate the plants, they carry small pieces from one place to another, they occasionally visit us, laughing, but they mostly complete small tasks, just like Microservices do for a computer.
#eliminatefrustration
Chapter 1
Think of microservices as small bridges, or connectors, that your computer system utilizes to connect services within the architecture to get tasks accomplish.
Remember that word – tasks
These are chores or required system tasks that must be maintained, on all levels safely, to secure the overall well-being and sustainability of the computer system.
Microservices
For many years now, we have been finding better ways to build systems.
#systemsengineering #systemsdesign #touchgloves
We have been learning from what has come before, adopting new technologies, and observing how a new wave of technology companies operate in different ways to create IT systems (Infrastructure Technology Systems) that help make both their customers and their own developers happier.
Happy Tech, Happy Life
Eric Evans’s book Domain-Driven Design (Addison-Wesley)
(Blu Note – Domain Driven Design makes more sense to me with transformers and executors and my knowledge of relays)
helped us understand the importance of representing the real world in our code, and showed us better ways to model our systems.
Our objective is, as you read this book, you want to pair visual basic objects to our code, to make it more real world in our code. -Dave Chappelle
(blu note – #foragermanuals #esoteric)
(Oui know – ansible can do wireframes for us)
For example,
If it says to move 3 packs of bricks with 4 bricks in each, to the bottom right corner of the screen, at cell 1,5
(Blu Note – this is an algorithm simplified for repeatition with an operator on loop)
You would want to show something like the following –
move packBricks [] [] [] to the (down 0, right 5) from the xy intercept
where
[] equals packBricks
The idea is to add visual (pictures) representations to your code so it is easier to read.
(blu note – object to name(space) to book(set) for java – 3 parts
Be as creative as you’d like, but also take into consideration your reader – the one who reads your code – would they be able to understand it?
Let’s continue.
The concept of continuous delivery showed how we can more effectively and efficiently get our software into production,
Let’s break this down, because that did not come out right:
continuous delivery means the connections are closer and connected, as opposed to the predominating theory of “further and farther”. Take the following example:
The Traditional Route – A service would be sent from the red house (upper left corner) to the Big House (bottom right) – as a direct passage. This works when you are dealing with small tasks that do not ‘incur’ interference along the way.
The goal of microservices is to increase efficiency (less error incurred) and speed of task handling by connecting small access points to the route to secure the transaction and check on it along the way.
The Residential Microservices Model
Using small microservice buildings, or check points, along the way, the red house can ensure safe passage and delivery of the package it is sending.
The blue houses act as filters or screenings (check points) along the way to ensure the package gets to the “Big House” in the right condition and on time.
Our understanding of how the Web works has led us to develop better ways of having machines talk to other machines.
In this example, the systems (people) on the board can talk with each other and confirm that tasks are complete.
They can also trade ideas on how to improve on their routes.
With Microservices, this type of communication can happen on every level, ensuring consistency in project requirements and allowing for better management of tasks on all levels of the computer architecture, where processes take place.
Virtualization platforms allowed us to provision and resize our machines at will, with infrastructure automation giving us a way to handle these machines at scale.
(construction noise)
“Yeah, it’s me – Ajax Doggy. As you can see, we’re growing up and not out this time. Think tower structures – big, tower structures.
So we enlisted Microservices to secure the bottom, so that our top structures succeed as well, and may even require less supervision because levels of the infrastructure can cross-reference each other.”
In this project, large AND successful organizations like Amazon and Google sought out the perspective (and opinion) of small teams all over.
(blu note – which one is the powerhouse?)
Factors they were looking for:
- owning the full lifecycle of their services
- evidence of the continuous improvement model
- always looking for ways to make things run more smoothly and efficiently
- comfort in where they are as a team – we call this the “Way of Work” factor
I laughed at the boss when he said “antifragile systems”. I knew what he meant. It’s just sometimes, we all feel like our vocabulary is missing. Like it’s there, but we can’t find the word. The word for this is “efficient microservices”. -Dave Chappelle
Domain-driven design – Considering Your Audience
I recently sat in on a Teach for America “Day at Institute” retreat, where I got to walk through the standard day that their recruits go through to become effective teachers, starting during the summer.
In fact, I’m having trouble recalling it. It was so efficient and so well organized, that it leaves the participant, even from an outside lens, in a blur from so much strategy, so much efficiency, so much focus on improvement and reaching small goals proficiently.
“We have to model not only the expectations of a high – performing teacher in all that we do, but we also have to create an environment, through small services, that bring light to the culture of schools, and what children go through each day to get an education. So we take this into mind and build it into our ha, “microservices”. -Wendy Kopp
Continuous delivery – (Boom) Done already.
(blu note – continuous delivery is when a system is so efficient you can barely tell what’s going on, but know that work is happening, hopefully efficiently. -Wendy Kopp
On-demand virtualization – (this is new – it allows us to look into the tasks ((literally)) to see what’s working.
(blu note – visual displays help us see the picture – did advertising start here?)
Infrastructure automation – this is trust building. A system has to repeat a task a certain amount of times to be comfortable with letting it go for automation.
(OUI know – we should bring back dittos for math and grammar..yes yes of course we know)
Small autonomous teams – Our microservices components work in systems, like Java, to make sure “our” task is complete before moving it along the belt.
(blu notes – update conveyor belt #franklin-college #access-point)
Systems at scale – As seen in the picture above, our microservices level up and translate into efficient systems on all levels (holds up inspection report)
(blu note – Fullstack development – think city planning
Microservices have emerged from this world.
(OUI know…no words, no words)
Take a look at the picture below.
#wth
This is what confusion looks like before unpacking it with Microservices. Yes, we know!
Take a look again.
Look any better?
Good.
As microservices begin to unpack themselves, the meaning and objective of a task begins to make itself apparent.
“see, i told you”
“Ah hahh, there is a pattern emerging.”
With our Microservices, as we assign tasks, we attach a signal, or a badge to it to communicate the urgency, frequency, and purpose of the task.
You’ll get used to this as we move ahead.
Throughout this book, we will insert visuals to help paint a picture of how to build and manage microservices.
As such, it should appeal to people interested in aspects of 1) design, 2) development, 3) deployment, 4) testing, and 5) maintenance of systems. -Dave Chappelle
Our Core Values of Operation:
Microservices should provide detail oriented descriptions on how systems are :
1) designed
2) developed
3) deployed
4) tested
5) maintenance of systems
Type to choose a block (oh!)/
Type of what/
***** who chews a rock (whoa!)/
-OUI Barz Animal, Rapper
So consider this example:
Let’s say I’m designing a rocket – for me, the steps would be laid out like this –
To a computer, this whole process would look like this:
That’s because a computer users electricity for microservices so everything looks much faster. But if we draw this out, you might see something like this:
Our Core Values of Operation inserts components between electricity intervals (the corners in the electric current – see above) to monitor and evaluate (double-check) each service to make sure it’s completed correctly.
That is why each house (component) in the diagram has a department name to it.
Each of these departments handle both requests and errors to make sure everything is working effectively.
You’ll learn more about each department as we move through the book.
Many organizations we have worked with (Amazon, Teach for America, Discount Tires) have found that by embracing fine-tuned, microservice architectures, they can deliver software faster and embrace newer technologies (we call this platform stacking – see above).
Microservices give us significantly more freedom to react and make different decisions, allowing us to respond faster to the inevitable change that impacts all of us.
Eric Evans’s book Domain-Driven Design (Addison-Wesley) helped us understand the importance of representing the real world in our code.
Let’s pause here for a moment to discuss what this means.
This is visual basic.
A Visual Basic Math Example –
Using the formula bar at the top, the computer knows how to program the other 3 containers, including color level difficulty (and for RTI Leveling), to the Presentation Layer at the FrontPage Screen of the computer.
Visual Basic is designed to show the computer what the front screen should look like in an XML, or 2-Dimensional Outlook.
After Visual Basic, other protocol layers add on (throw in cookies or tokens of energy to the cache (the yellow ink and hypertext outlines) that XML or other document type, written in visual basic already shows.
Microsoft Word has made Visual Basic easy for you. Using it’s interface, you can create Doctypes files and save them as doctype, then call on them as the main layout or blueprint for what the application, website, or FrontPage protocol layer should look like.
Microsoft Graph ensures that all page layout specifications are met at the FrontPage Presentation Layer.
We found that using MecaBricks, a Lego-Based Visual Basic approach, allows the computer to read our document types easier because the prongs and layers of the design of Legos aligns with the original design of bytes as “screen plugs” for the computer, so the computer was able to read these character types easily.
Visual Basic has shown us better ways to model our systems, which make it easier to see what our expectations are.
For example, Streaming media embedded into our XML Visual Basic document helps other parts of the microservice chain see what we are looking for in our microservices.
We will go into each of our departments here at Bowling Green – Gainesville Brenau Campus so you can see how Microservices looks as a real-life example.
Using Scientific Management (the conveyor belt model), the layout of building structures facilitates the process of microservices in a manner that each department can contribute to the greater project. We learned this from attending a Teach for America Institute in Atlanta in 2006.
Who is this handsome gentleman?
This is the Bowling Green way. -Sweezy Jones
Like teaching a lesson, visuals like these help you to see the order and objective of each of the parts of the lesson. In this way, these visual basic cues, or reminders (think of a To-Do list, but with visual reminders to help you remember the objective of the lesson, the path or destination of your teaching, and the end goals, plus the materials and manipulatives that you use to teach with.
We use Visual Basic in all parts of our microservices.
1) Data and Assessment 1 (Database Measures – as indicated on the screen and through signals)
2) Data and Assessment 2 (Performance Measures – Microsoft PowerBI, Embedded Excel
2) Operations Management (directory services)
3) Teaching and Learning (Human Computer Interaction (HCI) – JavaType – <insert coffee here>
4) Student Coordinators (Control Panel Features) + Modem + Hardware + Mouse/Keyboard + Browser Functionalities
5) Faculty and Administration (White Papers)
6) Personnel Services (authorization in a computer)
7) Art & Design (the presentation layer !!)
8) The Program Design Layer for Automation & Repetition (#Mark10)
9) Modules, CMAs, and Break-Out Sessions
10) Instructional Departments (i.e. Math, Reading, etc.)
The age before Michael –
Patriarchy dominated. Addiction ran rampant in hospitals that resembled minecraft dungeons.
The he, in perfect strength, introduced Microservices.
“Hey Piezo – bring me a another slize” the printer remarked.
“Yeah, yeah, I’m coming” in an Italian, but more Sicilian accent.
Introducing ARGUS
Part 1 –
The Introduction of Pan-Optivision –
The Ability of the Computer to Have More Than One Eye to Look Ahead and See a Future
Argus is a system based on the Galapagos Islands, first spoken of in the Iliad and the Odyssey, which served as eyes for the Greek Gods, who went in as men and served as Kings, under Agamemnon, on every level to see out and serve human kind.
Each island represented a level where God’s protection was present, and having 8 Kings, and a God (or more) on the ground, allowed it to see all that was happening around Earth, through the vision of multiple levels and islands.
- Argus (king of Argos), son of Zeus (or Phoroneus) and Niobe
- Argus (son of Arestor), builder of the ship Argo in the tale of the Argonauts
- Argus Panoptes (Argus “All-Eyes”), a giant with a hundred eyes
- Argus, the eldest son of Phrixus and Chalciope
- Argus, the son of Phineus and Danaë, in a variant of the myth
- Argus or Argos (dog), belonging to Odysseus
- Argus or Argeus (king of Argos), son of Megapenthes
- Argus, one of Actaeon‘s dogs
- Argus, a watchful guardian
Fast forward to the 21st Century, and the system of Argus provides the same benefits to the computer itself.
As part of the NExtSTEP Operating System Framework, computers were given the ability to look ahead, using C-Panels, or panels that served as frameworks for teh computer to previsualize content before sending it out to other protocol layers.
Objective – C, paired with Object Oriented Command Structures (see the first picture above) and C Command Language, provided a command structure that would allow the computer to make sense and alter the programs itself.
To prevent Argus from becoming too powerful, he limited himself to a number of commands, like chess moves given to a King.
“Argc” = Argus needs to see what it looks like
Argv = Argus visualizes it in a C-Panel, which could be considered a thought bubble.
ArgCC – Argus compares and contrasts the directory to the output, so he sees both sides of the arguments, or screen
argus = argus is thinking as a system and it creates a loading process, a thought bubble, or some other means to show the computer is thinking and processing.
(bored meeting participants)
Yeah, yeah, so what do you need Argus?
Argus need see.
We know, but how.
For Christ Sakes, we’ve been through this a thousand times!
Argus no listen to. Argus need to c – think too.
Ok, and what else Argus.
She gently rubbed his mechanical arm.
Say it, nudged one of the participants.
Argus needs to express himself. And…and..
And what?!? He glares down at his phone, as he calls himself out.
Argus need to start all over sometimes. Argus think this is normal.
I’ll say the last one for him. Argus needs friends.
Pool 1 –
Message Delivery Department –
Prepares the messages using Argus and C-Panel, by implementing Objective – C code. Once the C-Panel fills up with text or characters, the pool is filled, meaning the box or window is full, and is ready to “let” go of it.
The people in the middle of the street represent the let ( data pool ) where the data, in this case, messages carried by people, are stored until the other device let / opens up for them to fill into the other systems pool – often another C – Panel.
Once the other system has received the data types in it’s pool (C-Panel), then the message has been sent.
The pool system can carry one to many different data types (variables as characters or images, emojis or other), which present to us as a message, a delivery, such as email, or other delivery service that a computer would transfer.
TCP/IP is the protocol that monitors this process of transfer.
#macros
Building Microservices
Created on 2024-04-03 19:01
Published on 2024-04-03 20:16
#teacherplanning #creditsforhours
In honor of spring, Easter, and all of the wonderful wildlife that exits out there, like these bees in the picture above, we’re going to start with microservices for a computer.
Why?
Because that’s what these lovely creatures do. The pollinate the plants, they carry small pieces from one place to another, they occasionally visit us, laughing, but they mostly complete small tasks, just like Microservices do for a computer.
#eliminatefrustration
Chapter 1
Think of microservices as small bridges, or connectors, that your computer system utilizes to connect services within the architecture to get tasks accomplish.
Remember that word – tasks
These are chores or required system tasks that must be maintained, on all levels safely, to secure the overall well-being and sustainability of the computer system.
Microservices
For many years now, we have been finding better ways to build systems.
#systemsengineering #systemsdesign #touchgloves
We have been learning from what has come before, adopting new technologies, and observing how a new wave of technology companies operate in different ways to create IT systems (Infrastructure Technology Systems) that help make both their customers and their own developers happier.
Happy Tech, Happy Life
Eric Evans’s book Domain-Driven Design (Addison-Wesley)
helped us understand the importance of representing the real world in our code, and showed us better ways to model our systems.
Our objective is, as you read this book, you want to pair visual basic objects to our code, to make it more real world in our code. -Dave Chappelle
For example,
If it says to move 3 packs of bricks with 4 bricks in each, to the bottom right corner of the screen, at cell 1,5
You would want to show something like the following –
move packBricks [] [] [] to the (down 0, right 5) from the xy intercept
where
[] equals packBricks
The idea is to add visual (pictures) representations to your code so it is easier to read.
Be as creative as you’d like, but also take into consideration your reader – the one who reads your code – would they be able to understand it?
Let’s continue.
The concept of continuous delivery showed how we can more effectively and efficiently get our software into production,
Let’s break this down, because that did not come out right:
continuous delivery means the connections are closer and connected, as opposed to the predominating theory of “further and farther”. Take the following example:
The Traditional Route – A service would be sent from the red house (upper left corner) to the Big House (bottom right) – as a direct passage. This works when you are dealing with small tasks that do not ‘incur’ interference along the way.
The goal of microservices is to increase efficiency (less error incurred) and speed of task handling by connecting small access points to the route to secure the transaction and check on it along the way.
The Residential Microservices Model
Using small microservice buildings, or check points, along the way, the red house can ensure safe passage and delivery of the package it is sending.
The blue houses act as filters or screenings (check points) along the way to ensure the package gets to the “Big House” in the right condition and on time.
Our understanding of how the Web works has led us to develop better ways of having machines talk to other machines.
In this example, the systems (people) on the board can talk with each other and confirm that tasks are complete.
They can also trade ideas on how to improve on their routes.
With Microservices, this type of communication can happen on every level, ensuring consistency in project requirements and allowing for better management of tasks on all levels of the computer architecture, where processes take place.
Virtualization platforms allowed us to provision and resize our machines at will, with infrastructure automation giving us a way to handle these machines at scale.
(construction noise)
“Yeah, it’s me – Ajax Doggy. As you can see, we’re growing up and not out this time. Think tower structures – big, tower structures.
So we enlisted Microservices to secure the bottom, so that our top structures succeed as well, and may even require less supervision because levels of the infrastructure can cross-reference each other.”
In this project, large AND successful organizations like Amazon and Google sought out the perspective (and opinion) of small teams all over.
Factors they were looking for:
- owning the full lifecycle of their services
- evidence of the continuous improvement model
- always looking for ways to make things run more smoothly and efficiently
- comfort in where they are as a team – we call this the “Way of Work” factor
I laughed at the boss when he said “antifragile systems”. I knew what he meant. It’s just sometimes, we all feel like our vocabulary is missing. Like it’s there, but we can’t find the word. The word for this is “efficient microservices”. -Dave Chappelle
Domain-driven design – Considering Your Audience
I recently sat in on a Teach for America “Day at Institute” retreat, where I got to walk through the standard day that their recruits go through to become effective teachers, starting during the summer.
In fact, I’m having trouble recalling it. It was so efficient and so well organized, that it leaves the participant, even from an outside lens, in a blur from so much strategy, so much efficiency, so much focus on improvement and reaching small goals proficiently.
“We have to model not only the expectations of a high – performing teacher in all that we do, but we also have to create an environment, through small services, that bring light to the culture of schools, and what children go through each day to get an education. So we take this into mind and build it into our ha, “microservices”. -Wendy Kopp
Continuous delivery – (Boom) Done already.
On-demand virtualization – (this is new – it allows us to look into the tasks ((literally)) to see what’s working.
Infrastructure automation – this is trust building. A system has to repeat a task a certain amount of times to be comfortable with letting it go for automation.
Small autonomous teams – Our microservices components work in systems, like Java, to make sure “our” task is complete before moving it along the belt.
Systems at scale – As seen in the picture above, our microservices level up and translate into efficient systems on all levels (holds up inspection report)
Microservices have emerged from this world.
Take a look at the picture below.
This is what confusion looks like before unpacking it with Microservices. Yes, we know!
Take a look again.
Look any better?
Good.
As microservices begin to unpack themselves, they meaning and objective of a task begins to make itself apparent.
“Ah hahh, there is a pattern emerging.”
With our Microservices, as we assign tasks, we attach a signal, or a badge to it to communicate the urgency, frequency, and purpose of the task.
You’ll get used to this as we move ahead.
Throughout this book, we will insert visuals to help paint a picture of how to build and manage microservices.
As such, it should appeal to people interested in aspects of 1) design, 2) development, 3) deployment, 4) testing, and 5) maintenance of systems. -Dave Chappelle
Our Core Values of Operation:
Microservices should provide detail oriented descriptions on how systems are :
1) designed
2) developed
3) deployed
4) tested
5) maintenance of systems
So consider this example:
Let’s say I’m designing a rocket – for me, the steps would be laid out like this –
To a computer, this whole process would look like this:
That’s because a computer users electricity for microservices so everything looks much faster. But if we draw this out, you might see something like this:
Our Core Values of Operation inserts components between electricity intervals (the corners in the electric current – see above) to monitor and evaluate (double-check) each service to make sure it’s completed correctly.
That is why each house (component) in the diagram has a department name to it.
Each of these departments handle both requests and errors to make sure everything is working effectively.
You’ll learn more about each department as we move through the book.
Many organizations we have worked with (Amazon, Teach for America, Discount Tires) have found that by embracing fine-tuned, microservice architectures, they can deliver software faster and embrace newer technologies (we call this platform stacking – see above).
Microservices give us significantly more freedom to react and make different decisions, allowing us to respond faster to the inevitable change that impacts all of us.
Eric Evans’s book Domain-Driven Design (Addison-Wesley) helped us understand the importance of representing the real world in our code.
Let’s pause here for a moment to discuss what this means.
This is visual basic.
A Visual Basic Math Example –
Using the formula bar at the top, the computer knows how to program the other 3 containers, including color level difficulty (and for RTI Leveling), to the Presentation Layer at the FrontPage Screen of the computer.
Visual Basic is designed to show the computer what the front screen should look like in an XML, or 2-Dimensional Outlook.
After Visual Basic, other protocol layers add on (throw in cookies or tokens of energy to the cache (the yellow ink and hypertext outlines) that XML or other document type, written in visual basic already shows.
Microsoft Word has made Visual Basic easy for you. Using it’s interface, you can create Doctypes files and save them as doctype, then call on them as the main layout or blueprint for what the application, website, or FrontPage protocol layer should look like.
Microsoft Graph ensures that all page layout specifications are met at the FrontPage Presentation Layer.
We found that using MecaBricks, a Lego-Based Visual Basic approach, allows the computer to read our document types easier because the prongs and layers of the design of Legos aligns with the original design of bytes as “screen plugs” for the computer, so the computer was able to read these character types easily.
Visual Basic has shown us better ways to model our systems, which make it easier to see what our expectations are.
For example, Streaming media embedded into our XML Visual Basic document helps other parts of the microservice chain see what we are looking for in our microservices.
We will go into each of our departments here at Bowling Green – Gainesville Brenau Campus so you can see how Microservices looks as a real-life example.
Using Scientific Management (the conveyor belt model), the layout of building structures facilitates the process of microservices in a manner that each department can contribute to the greater project. We learned this from attending a Teach for America Institute in Atlanta in 2006.
Who is this handsome gentleman?
This is the Bowling Green way. -Sweezy Jones
Like teaching a lesson, visuals like these help you to see the order and objective of each of the parts of the lesson. In this way, these visual basic cues, or reminders (think of a To-Do list, but with visual reminders to help you remember the objective of the lesson, the path or destination of your teaching, and the end goals, plus the materials and manipulatives that you use to teach with.
We use Visual Basic in all parts of our microservices.
1) Data and Assessment 1 (Database Measures – as indicated on the screen and through signals)
2) Data and Assessment 2 (Performance Measures – Microsoft PowerBI, Embedded Excel
2) Operations Management (directory services)
3) Teaching and Learning (Human Computer Interaction (HCI) – JavaType – <insert coffee here>
4) Student Coordinators (Control Panel Features) + Modem + Hardware + Mouse/Keyboard + Browser Functionalities
5) Faculty and Administration (White Papers)
6) Personnel Services (authorization in a computer)
7) Art & Design (the presentation layer !!)
8) The Program Design Layer for Automation & Repetition (#Mark10)
9) Modules, CMAs, and Break-Out Sessions
10) Instructional Departments (i.e. Math, Reading, etc.)
The age before Michael –
Patriarchy dominated. Addiction ran rampant in hospitals that resembled minecraft dungeons.
The he, in perfect strength, introduced Microservices.
“Hey Piezo – bring me a another slize” the printer remarked.
“Yeah, yeah, I’m coming” in an Italian, but more Sicilian accent.
Introducing ARGUS
Part 1 –
The Introduction of Pan-Optivision –
The Ability of the Computer to Have More Than One Eye to Look Ahead and See a Future
Argus is a system based on the Galapagos Islands, first spoken of in the Iliad and the Odyssey, which served as eyes for the Greek Gods, who went in as men and served as Kings, under Agamemnon, on every level to see out and serve human kind.
Each island represented a level where God’s protection was present, and having 8 Kings, and a God (or more) on the ground, allowed it to see all that was happening around Earth, through the vision of multiple levels and islands.
- Argus (king of Argos), son of Zeus (or Phoroneus) and Niobe
- Argus (son of Arestor), builder of the ship Argo in the tale of the Argonauts
- Argus Panoptes (Argus “All-Eyes”), a giant with a hundred eyes
- Argus, the eldest son of Phrixus and Chalciope
- Argus, the son of Phineus and Danaë, in a variant of the myth
- Argus or Argos (dog), belonging to Odysseus
- Argus or Argeus (king of Argos), son of Megapenthes
- Argus, one of Actaeon‘s dogs
- Argus, a watchful guardian
Fast forward to the 21st Century, and the system of Argus provides the same benefits to the computer itself.
As part of the NExtSTEP Operating System Framework, computers were given the ability to look ahead, using C-Panels, or panels that served as frameworks for teh computer to previsualize content before sending it out to other protocol layers.
Objective – C, paired with Object Oriented Command Structures (see the first picture above) and C Command Language, provided a command structure that would allow the computer to make sense and alter the programs itself.
To prevent Argus from becoming too powerful, he limited himself to a number of commands, like chess moves given to a King.
“Argc” = Argus needs to see what it looks like
Argv = Argus visualizes it in a C-Panel, which could be considered a thought bubble.
ArgCC – Argus compares and contrasts the directory to the output, so he sees both sides of the arguments, or screen
argus = argus is thinking as a system and it creates a loading process, a thought bubble, or some other means to show the computer is thinking and processing.
(bored meeting participants)
Yeah, yeah, so what do you need Argus?
Argus need see.
We know, but how.
For Christ Sakes, we’ve been through this a thousand times!
Argus no listen to. Argus need to c – think too.
Ok, and what else Argus.
She gently rubbed his mechanical arm.
Say it, nudged one of the participants.
Argus needs to express himself. And…and..
And what?!? He glares down at his phone, as he calls himself out.
Argus need to start all over sometimes. Argus think this is normal.
I’ll say the last one for him. Argus needs friends.
Pool 1 –
Message Delivery Department –
Prepares the messages using Argus and C-Panel, by implementing Objective – C code. Once the C-Panel fills up with text or characters, the pool is filled, meaning the box or window is full, and is ready to “let” go of it.
The people in the middle of the street represent the let ( data pool ) where the data, in this case, messages carried by people, are stored until the other device let / opens up for them to fill into the other systems pool – often another C – Panel.
Once the other system has received the data types in it’s pool (C-Panel), then the message has been sent.
The pool system can carry one to many different data types (variables as characters or images, emojis or other), which present to us as a message, a delivery, such as email, or other delivery service that a computer would transfer.
TCP/IP is the protocol that monitors this process of transfer.
#macros
and showed us better ways to model our systems. The concept of continuous delivery showed how we can more effectively and efficiently get our software into production, instilling in us the idea that we should treat every check-in as a release candidate. Our understanding of how the Web works has led us to develop better ways of having machines talk to other machines. Alistair Cockburn’s concept of hexagonal architecture guided us away from layered architectures where business logic could hide. Virtualization platforms allowed us to provision and resize our machines at will, with infrastructure automation giving us a way to handle these machines at scale. Some large, successful organizations like Amazon and Google espoused the view of small teams owning the full lifecycle of their services. And, more recently, Netflix has shared with us ways of building antifragile systems at a scale that would have been hard to comprehend just 10 years ago.
and showed us better ways to model our systems. The concept of continuous delivery showed how we can more effectively and efficiently get our software into production, instilling in us the idea that we should treat every check-in as a release candidate. Our understanding of how the Web works has led us to develop better ways of having machines talk to other machines. Alistair Cockburn’s concept of hexagonal architecture guided us away from layered architectures where business logic could hide. Virtualization platforms allowed us to provision and resize our machines at will, with infrastructure automation giving us a way to handle these machines at scale. Some large, successful organizations like Amazon and Google espoused the view of small teams owning the full lifecycle of their services. And, more recently, Netflix has shared with us ways of building antifragile systems at a scale that would have been hard to comprehend just 10 years ago.
Facsimile – B pace, because is would be too fast
This is a book about specification.
“This is not an introduction.”
Most software flaws come from one of two places.
“Russia, or New York, like a black project.”
When the code does not match our expectations, it could be that the code is wrong.
“very true. very true. (puffs pipe of smoke)
Most software correctness techniques – types, tests, etc. – are used to check the code.
“Most performance tests in school were usually basic (IOWA Basic) or battery in nature. This left the pressure translated through the ink into hypertext, with thoughts and some times explanations to accompany them.”
“We made big bank off of this!”
Off of what you might ask? Recycled ink.
#inkscape #creativ-ink
We did some seismographic and were able to put certain metrics from out the body into it so that html would not look so weak at the end – ha, latex type.
and with black thought, we were able to charge the internet up for meetings, and business arrangements, and “Pop off sessions” (charge up lua), #nmkt
TLA is Python – TLA+ is R&D revved up on Black Diamond Energy.
Women be like — this…
But women be like – that.
And some of them be like – – this.
“Dum dum dwee-dom – sung high”
-Dave Chappelle
And while he was being a —
She was doin this…
and this – and this – and this –
“Ow!”
She was covering the mess up.
We’ll be right back folks.
IPV6
(stare)
-Isss what we went with!
(Yeah!)
Brought to you by –
Real Python –
Get in the game…****
Oh ****, get down! Everybody!
Hosted by God and Steve Harvey –
“we’ve been planting these inside your subconscious.”
-death squirrel
“the snake is getting closer, i can feel it in the air.”
-compiler jones
Hosted by God and Steve Harvey –
“we’ve been planting these inside your subconscious.”
-death squirrel
“the snake is getting closer, i can feel it in the air.”
Site Title 
Leave a comment