This content originally appeared on DEV Community and was authored by Jorden Williams
What is "Full Bands"? Well, it's a phrase to show support for your fellow developers. "Full Bands" is telling them that you hope their data is so perfectly aligned, that all of the bandwidth is being utilized and they have no wasted checks.
Now, I know for most people this won't a lot of sense. So, a quick explanation.
Full Bands == Tight Lines | Full Bands === Tight Lines
Tight lines is a phrase for the fishers. This is their way of saying, good luck. A tight line means there is a fish on it. Full bands is intended to be the software side of it.
When we write code, we are writing a series of checks and calls to manipulate data.
*find data*
*get value*
*modify data*
*use data*
Rinse and repeat. A little better example:
#include <stdio.h>
void main(int argc, char* argv[]){
int a = 0; // create a variable with init value of 0
printf("%d", a);
return 0;
}
Printf() is making the call to find a, return its value, and then display it to the console.
The steps involved are that the program stores a variable with a given value at a specific memory address. When the data is accessed by the program, the CPU makes a read call to that address, but it is not only getting that address. It's calling the whole block address (0x8000 versus 0x80001234). So as the CPU "reads" the data, any other data that is in that block is being loaded and "read".
What does all of this have to do with full bandwidths?
Full bandwidth means any and all data from the block that is read, is used and you are not wasting cycles going through the block address. This is why OOP happened.
Object Oriented Programing allows the developer to put all of the data together in a single Object. This Object (struct/class/typedef) now contains all of the data it needs to have. When you make a call to that Object, the CPU "reads" the data based on the definition, and provides it to the program. Is it making sense now?
One more for good measure:
// what makes up a person?
class Person{
string name;
int age;
// int addrNum;
// string addrStreetName;
// string town;
// However, the address can be its own object
Address homeAddr;
}
class Address {
int addrNum;
string addreStreetName;
string town;
string state; // province
string country;
int zipcode;
}
That's two (2) block calls when calling one (1) Person object. Does it make sense to say "full bands"? Let me know what you think about "full bands".
Link to the video that got me thinking this way. Link to the slides. Additional presentations from the event can also be found at the repo, 2014-2023.
This content originally appeared on DEV Community and was authored by Jorden Williams
Jorden Williams | Sciencx (2024-09-08T17:18:15+00:00) Full Bands?. Retrieved from https://www.scien.cx/2024/09/08/full-bands/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.