DEV Community: Anders Hornor

Vulnerabilities: Filling a Sieve with Sand

Anders Hornor — Wed, 18 Dec 2019 01:52:55 +0000

Maybe you have a github and you get messages about it or maybe you write libraries that I get messages about, but I'm assuming at some point you've experienced a development somewhere that's either highlighted or caused an issue with some program you've written. Well why does this happen so consistently and what can I do about it?

Vulnerability vs Risk

Vulnerability is seen as an exploitable aspect of the program you've written. Risk is a potentially exploitable aspect if something changes. Like wiring for those light strips on planes that direct you to the exits that's functionality is contingent on air pressure is a risk factor but not an exploit. Wiring that controls those lights that direct you to the exits on planes that if you mess with in a particular way gives you control of the doors is an exploit.

Why Do they Exist Though?

Well people can only assume so much about how things can be misused. People cant see the future. come on.
Also each layer of abstraction that is the conglomeration of multifarious conditionals that coalesce into a program each assume specific input/s. As programs and all their dependencies develop their individual outputs change. When any output changes the quality of is functionality changes as well. In certain instances this change leads to exploitable deficiencies.

What Can I Do THough!?

Nothing you're fucked! Just kidding. Forethought is Key ie planning. Developing plans should be based in evidence. Knowing of "pinch points" or places with dynamics that have historically caused issues can help you highlight your potential threats. I feel like this is part of best practices really or at least justification for why certain best practices are what they are.
Keep up to date. Tests heavily. Release slowly. Eat regularly. It all helps.

That's all I got. Get out and make something. This one is nothing to write home about. Till next time.

Building a PC - What not to do.

Anders Hornor — Wed, 11 Dec 2019 05:53:57 +0000

So my birthday is around the corner...I guess I'm still justifying the purchase but I bought a PC like 5 days ago, but on the cheap because it came in pieces. More like there was a sale on PC parts on Amazon and my buddy made a pc so remembering all the days as a kid pining for a wicked fast thread-ripping gaming pc I bought a bunch of pieces for my first ever battlestation. Now running windows 7 because I had it...My most recent mistake I will say. It had no opportunity costs though. I had an unopened ultimate version sitting on a shelf.... I wonder why XD...

Anyway. I made some other mistakes along the way so here we gooOoooOOOO!!

BULLET LIST OF WHAT NOT TO DO:

1.Don't trust Amazon shipping times. Be patient or buy it elsewhere if it's not too expensive.

2.Read a bit about putting together a PC before you put it together.

3.Doublecheck compatibility on site like this

4.Spend time clearing a space to work in.

5.Move all animals to other spaces.

6.Read the basic info about your Motherboard and follow all instructions included.

7.Fuck it you know what just lay all the different instructions that come in each part box out and double check the specifics for each part.
-each part most likely comes with a generic set-of-instructions-for-installation specific to other compatible parts (think power supply instructions) lay them all out next to each other and look for the instructions specific to the parts you have. This way you'll be certain your connections and installation is correct if issues arise elsewhere.

8.When you get uncharacteristically angry after you didn't lock down your cpu before realizing you would have to take out your motherboard to install the aftermarket heatsink for your cpu and end up dropping your cpu on the ground and bend some pins and get lint in it, eat some food, you're really hungry.

9.Put the CPU in first the right time.

10.read I/O installation instructions carefully multiple times. Get it right the first time because it's how you turn the damn thing on most likely. It's a bitch when you don't know what else could be the issue.

Be careful with your ATX connections. You can ruin it all real quick. Kind of like dropping a CPU.

12.Take your damn time.

These became suggestions but yeah I dropped my cpu, didn't connect my I/O properly, and had issues connecting the right cpu power. It all worked out in the end but Be careful. This shits expensive.

Till next time!

Bash History Contd. You can load an old bash history!

Anders Hornor — Wed, 04 Dec 2019 04:31:38 +0000

It's True You can load an old bash History!
See Last Weeks Post For More on Bash History

So this could be easily adapted into a script that should in essence move through your entire History and add each old history to a new super long history. But anyway here's how to load an old bash history.

So first off as opposed to last time when we were working with the .bash_profile file this time were working with the .bashrc file.

`.bashrc.`

So a little aside about this cool file. The .bashrc file is a file your terminal runs before it opens. Due to this fact you can add commands to it that the terminal will run as it opens. So this would be a kind of a hacky way to do this and I know there are more elegant ways to due this. I need to explore bash commands more in general mean shit theres probably a way to do this with straight up bash commands any way. This cooooool .bashrc file can run commands as you open the file. Now that I think of it. I could probably write a command in my .bash_profile that does this...

Anyway .bashrc runs commands as the terminal opens so there's definitely a little loop in there that would make a super history. Set the HISTFILESIZE and HISTSIZE to super large and then loop throught all the .bash_session/....historynew files and history -a them all. Followed up by a history -r and voila super file throuretically.

Opening A Specific History file.

type- nano ~/.bash_profile -into your terminal
In your .bash_profile file at the very top enter this code

HISTFILE=<history file you want to open thats probable bash_session/.../<somenumbers>.historynew`

reload your terminal

Voila -

Old History!

Till Next week Adventureres!!!!

Terminal History - How to make it work for you.

Anders Hornor — Wed, 27 Nov 2019 04:37:34 +0000

I recently was looking for some old commands I had made in my terminal and was hit hard when I realized I can only scroll so far back into a window. Well after some sleuthing I found out a way to not only look at old commands from long lost windows but also a was to restore old terminal sessions that may have a bash function that does just what you need it to do or something. So the story...
While looking at the oldest entry of my my newly opened terminal window I noticed something interesting. I saw this line of text:

Last login: Tue Nov 26 11:19:59 on ttys004

and it had me curious. If my terminal is taking some time stamp of my previous commands and saving it till that point maybe it has more or others. Well it does.

Terminal History: What is it?

Your terminal saves a history or all the commands committed over a period of time or a bash history. Each history is stored with a collection of other information as a bash session. Each bash session has a timestamp associated with an id and a store of all the commands that were committed during a set period of time. Dope right!

Each session can also be loaded into your bash_profile in essence restoring that session which is also a neat trick. Any way How do I see/ use all this cool shit? Easy peasy.

`history`

With the bash command history typed into your terminal a log of the previous (defaulted to 500) commands typed into your terminal will be displayed.

You can update the length of record in a few easy steps.

First you need to access your Terminal by opening that Search in your applications folder in your Finder File-Manager.

Next type history Voila your terminal history.

lol you typed the same command three times 3 different ways then moved files three times and tried the command a fourth way then went back to the original file ls'ed it then typed the fourth command a fourth time.
Oh you goof you! xP

Now checkout your bash_profile because next you need to edit that file.

nano -w ~/.bash_profile

Now you're cookin with gasoline so be careful I guess. There's a way to undo stuff in here (your bash_profile), but maybe you have some dope custom bash commands that you don't want to mess up or you didn't set up your bash_profile and got ran a command at some point that did and you aren't quite sure what all of the commands are that have been added and the file is full' of comments; it's all ugly and you dont know whats what in this jungle of a file open in your two-sizes-too-small, why-is-it-mustard-colored, terminal, so don't fuck with anything.

or maybe it just says path and has a path and that's about it.

Anyway your bash_profile looks you don't want to break anything you just want to either edit or add the lines(choose your own number; blank is ∞):

HISTSIZE=613511236114111118312
HISTFILESIZE=613511236114111118312

hint: use the control + W command to search in file open in a nano editor

Now you have an awesomely long bash history. If you ever need to find something again well you can. You're welcome. Now when you get all pissed off because you defined a variable in your bash window and can't re-assign it or something (I'm coming up with these on the spot, nothing to go off yet :) don't fret. You can delete your bash history...yes it's possible.

with the quick and dirty command

history -c

and it's gone.

Now for next time, .bash_sessions, restoring past histories, restoring past sessions, and saving the world one command at a time.

for fun check out some files in your /Users/<your-username-here>/.bash_sessions file

It's got everything you need to look deeply into your past. Soooo Deep you can almost touch it!

Middleware...WTF is it?

Anders Hornor — Wed, 27 Nov 2019 04:31:54 +0000

A SMKPCPTBCADeeDive into Middleware indeeeed ... What ever the ferck° that is.

MiddleWare for the 30th time...

So as I began my journey into programming I first came across the idea of middleware when I was learning about Ruby and jumped head first into the world of full stack with Rack. I had no Idea what it was or what it did. I was just downloading , typing, clicking, following along n such. So to add clarity to my understanding I looked into Middleware and came across Introduction To MiddleWare: Web Services, Object Components and Cloud Computingby Letha Hughes Etzkorn.

She began to expand my understanding of this integral technology and summed up the nature of Middleware well when citing major contributors to its establishment in this following quote:

First of all, according to Oracle:

Middleware is the software that connects software components or enterprise applications. Middleware is the software layer that lies between the operating system and the the applications on each side of a distributed computer network. Typically, it supports complex, distributed software applications.

The following definition for Techopedia (2016) is more comprehensive:

Middleware is a software later situated between applications and operating systems. Middleware is typically used in distributed systems where it simplifies software development by doing the following:

-Hides the intricacies of distributed applications.
-Hides the heterogeneity of hardware, operating systems, and protocols
-Provides a set of common services that minimizes duplication of efforts and enhances collaboration between applications

The following definition from Apprenda (2016) is also good to use in the context of this textbook because it clarifies that in todays world, cloud computing is also considered to be part of middleware:

A simple middleware definition: software that connects computers and devices to other applications. It can also be referred to as the slash or connecting point in client/server. Another way to define middleware is to say that it is software that acts as a liaison between applications and networks. The term is often used in the context of cloud computing, such as public or private cloud.
" (4-5, Ektorn, L. H., 2017).

As you can see from this one quote alone middleware is more than just a small cog in the big machine that is any program. It is the fabric that holds an entire program together. It is the software that communicates between all of the different devices that make up a network. It is the language in way of the internet of things. From Intranet to Internet Middleware connects it all.

°If anyone cares to read this footnote I'd be ecstatic if you would so kindly message me about your take on swearing in blog posts. I was considered a sailor of sorts at one point and swore like one before then. I still do but to my bests judgments solely when appropriate. Anyway I'd be much obliged.

Citation:

Etzkorn, L. H. (2017). Introduction to Middleware: Web Services, Object Components, and Cloud Computing. CRC Press. pp. 4–5. ISBN 9781498754101.

More About Node; Router() Is Pretty Dope

Anders Hornor — Wed, 13 Nov 2019 07:55:32 +0000

In an earlier post I talked about why people use Node with express and referenced some web snooping I'd done to make most of my claims. Well now I'm back with a little more meat to fatten my claims as to be honest I feel like Node has not disappointed yet. Maybe I just want to justify my time spent learning it. Anyway, Node's built-in Router Object is pretty great.

Shoutout to Udemy....and Flatiron too I guess ¯_(ツ)_/¯?

Router()™ MakesIt Simpler

One of the first web apps I made was a Ruby on Rails Single Page App(SPA)ˇ. It had a views folder that handled all my pages, then a routes.rb file that outlined all the routes. It was oddly the most frustrating part of setting up ruby apps half of the time. Its convoluted unlike a lot of other aspects of Ruby best practices in my opinion. Anyway the routes were always a hassle to set up and their order was generally an issue and it constantly felt redundant and repetitive. Well Node is less so and arguably "Super Streamlined Sawcesome....Sauce®".

Router turns a convoluted Routing process in Ruby into a one-stop-shop part of the function that processes the request. It turns three steps into one.
Router makes processing parameters a breeze. Routers Class methods include easy to use parameter management functions like express.Router().param() Also, unlike Ruby with the potential for malicious code to be passed through as parameters, Node with express's parameters are fairly secure (dont quote me on that. It's my assumption as of yet).
Router makes Node with express do what it was intended to do. The compartmental yet minimalistic nature of Router lends itself well to a highly scalable efficient Web App.

ˇI will literally reference this as SPA in later blog posts without defining the acronym first. Watch Out! Madman on the loose! Whaaaaaa!

| ヽ(。_°)ノ |!!!!

Building with Node.js; A First Take.

Anders Hornor — Wed, 06 Nov 2019 06:05:39 +0000

Node

Well first and foremost I must preface this post with a disclaimer: I have a lot more to learn about Node.js and Express.js and just JS.

It's Just A Bunch of JS.

Anyway, as I've been working through some basics of setting up a server with Node I've come to realize that it is very much a child of its foreparent JavaScript. I have a lot to learn about JS let me tell you but at the outset I feel like I'm writing JavaScript...Oh wait... I am. So there's that. At the outset of this journey I'm finally realizing that is is just a huge library built on top of JavaScript and.

It Comes With Capacity

So-far everything I've needed has been available with express.js. I imagine there are tons of other libraries/frameworks/packages that are all as if not more powerful that express.js. Gotta get crackin.

Syncs Well With VS Code

Im using VS Code and I am always blown away with the amount of user generated linters and other fun and powerful packages have been built for Node.

Express Is Stupid Simple In A Good Way

Accessing request parameters is as straightforward as it comes. Because the server stores data in JSON format there is no need to convert data after or before each request. This I hear also reduces processing time making for quicker web-apps.

Tried And True

Node.js use is growing and for a good reason. It's very powerful, built on a language most people are familiar with, and straightforward.

Thanks for Reading, Till next time!
Something Juicier

New to Node; Exploring a Favorite

Anders Hornor — Wed, 30 Oct 2019 05:28:24 +0000

Going through the career transition process I was originally overwhelmed with the shear volume of languages the field of computer science has developed over the years. I don't have an exact number, but there are easily over 2000 languages. The possibility exists for nearly infinite languages due to the nature of programming allowing for countless layers of abstraction. Each layer has the capacity for some ungodly number of languages. It's mind numbing nearing existential. Anyway, as I slowly built my way into the world of programming I realized that some languages are more common than others. Initially I learned to build with Ruby on Rails and thought about little else. As I built more I became aware of the regard given Ruby on Rails and wanted work my way into other server-side languages. As I apply for jobs and talk to potential employers I keep hearing about a languages I have little experience with yet. I keep hearing about Node.js. As I've been looking into the language I've become aware of why it is favored.

Node.js is fast

Apparently Node was developed to create fast network type applications and that's what it does. From what I read, Node's main capacity is a high level of scalability. It works well to hold multiple connections that are simultaneously interacting with a server. This seems to be due to Node storing data in a JSON format.

NPM is great!

Nodes built in package manager is highly transparent, accessible, and built. NPM offers quick and easy access to countless libraries of packages that make building easier and more powerful.

Makes Cross-Platform Easy

Nodes plethora of packages have been built up to make cross-platform development a given. Without much work your programs can be built for Linux, MacOS, and Microsoft applications simultaneously.

Simplifies Distributed Workload

The nature of JS programs modularity and Node's capacity for continuous and multifarious communication Node makes working with large projects simpler. Many teams can potentially develop simultaneously with ease.

These four reasons make Node a more than worthwhile language to learn. As I learn more about it I'll be sure to share. I apologize for the contrived and relatively unoriginal post.

Till next week, something more entertaining :P

The Perfect Portfolio: Projects that Please People

Anders Hornor — Wed, 23 Oct 2019 06:29:02 +0000

Another day another dollar... or maybe not if you need a job. I keep reading these weird blogs about portfolio suggestions and then I look at my portfolio and Im like "WTF Anders!?!? Get on a level you lazy shit, build something better." Then I realize all the people making these blogs have been programming for a good 50% of my life. This sends me into a weird place where I think "Yea fuck those guys! They're not my demographic! They're not the other "Me's" in the world! They're looking for some job with seniority so fuck em! I just want to build more while learning more while making a little bit of money! So yes Fuck those other guys who write blogs about building a portfolio for some senior level job. Point to the website you built for the company you're leaving not some dinky thing you did in your spare time... I guess if you're doing the start up thing and are looking for some investors mock-ups are nice, but where are all the suggestions for people trying to break into the Web Dev world? Right here Mutha Sucka!

7 Portfolio Polishing Projects for Promise Seeking Plebs

!: Something You Would Consume

Take a minute and think of something you would use and build that. Fuck all this pigeon-holed bullshit. If you would use it build it, and learn while you do. Reflecting on who you are and what you like will help you hone your own creative spirit and better your ability to communicate what you will add to wherever you're showing your portfolio.

@: A 'TaskLister™'

It's the tried and true method to showing your basic understanding of how to use the basic tools of your trade. Make an app, program, or website that you can add, edit, and delete tasks on. Strut a bit by adding other features. Maybe a priorities feature? Maybe a calendar? Maybe it looks like its from the 80's? ––idk you do you!––

#: A Basic Game

Show off your dopeness by recreating a favorite simple game. You played snake as a kid!? Get it! You used to dominate a minesweeper leaderboard!? Why the fuck not!? You've got feather fingers? Tetris is always a fun functional challenge!

$: An Online Market

Craigslist was built in a day! Very much a lie, but how hard can it be!? In reality you're layering a site in a way that make sense. Users, Users posts, adding posts, editing posts, deleting posts, maybe even purchasing a post!?! The list goes on. All the features that are a part of an online market are the building blocks of 90% (maybe more!?(definitely not less)) of every website ever.

%: Is That A Project Board I See?

Get in the Create - Edit - Delete - Style mindset with a communal task lister. A Project Board!!! Styling becomes key here so be ready to hone those CSS skills, You're making a Project board! Build a site that lets people track and manage their progress (maybe even a multiple peoples progress) on a project. Functional and promotional!

^: You Say Tomato I Say A Thing-Finder

Build something that interacts with the myriad of API's out on the net that make accessible location data. Why not find the coolest brewery, brew-shop, or pet spa near you!? There are countless API's out there and go develop your own "Blue Steel" with a powerful use of all that Data!

&: SoSocial Media

Nurture your aging wings with a Social media site. Maybe it's a blog, or a picture sharing site, or you want to clone reddit idk dream-it dreamers! A Social media site meets almost all prerequisites for showing off. You've got style, classes, components, data-storage, data processing, users, posts, chat, comments and feeds all in one place. "It's like the new age TaskLister™" - The Zuuck, aka MKZB.

Just Do It!

Anything you build can be great it just takes time, commitment and maybe some trust in yourself. If you think it would be fun to use build it. No matter what you're building you're going to be displaying your skills. It's more than your styling or structure it's you sharing yourself through your code.

Till next time!
Maybe back to Sets?

Networking: Building Relationships Through Reciprocity

Anders Hornor — Wed, 16 Oct 2019 05:41:46 +0000

Networking is more than just Connecting

If you're a forever learner like me you can't stop looking for new and inspiring technologies, philosophies, theories, and when it really comes down to it people. The people we meet throughout our life are the most powerful tool every individual has to be great and keep learning and progressing. The people around us act as the sounding boards and filters through which we create understanding of the world by validating or not individuals' expressions of understanding of the world. In this way the people around us are the truest of teachers as they act to solidify the nuggets of learning found in every experience one encounters. Due to the importance of those around us to situate all that is learnt I want to take a chance to talk about a recent insight that was shared with me as I work to hone my network and networking skills.

The Nugget

I have been working through a career transition and have had ample opportunity and good reason to network. Through my exploration of the Software Development and Engineering community in the Greater Seattle Area I was introduced to a new friend through the power of a LinkedIn People search at a specific company. This new friend spent a solid hour chatting with me about their own journey into Software Development and their current pursuits at a company they are rather comfortable at. Not only was their graciousness with their time relieving and empowering they were able to share with me some of the nuggets passed on to them through their own Networking Journey. My new friend shared with me their opportunities to build relationships around the world that has lead them to a deep and extensive network of some thousands of people. They followed up a seemingly boastful comment with the nugget that they haven't been doing it to find the next best job perse but instead to explore the community they have become a part of; and in doing so help nurture that community into one they want to be more a part of. This struck me as I had never thought of networking in such a way. I had thought of organizing my room or my desktop or my desk in such a way, "building the environment I want to live in" kind of thing, but never had I thought of professional relationships in such a way.

Build It For Them For You

What does it mean to nurture a community though. My new friend outlined their method to successfully networking a network of success.

Look for "Companies" not "Jobs"

When building your network first look for companies that: as an employee you will want to be successful in; as a consumer you will feel happy consuming; and as an owner you will feel proud managing.

Reach out!

Once you find somewhere great find out who makes it great. Reach out to the new and old employees, managers, and contractors that have built the companies you stand behind. By exploring who makes greatness you yourself will get insight into how to make greatness. Also there is no way to build into and add something great without connecting with those that have built it.

Inquire about the Company and not the Job

Look into the company and not the job. Doing so will elucidate how you can best benefit the company and community you can stand behind.

When it's Apples and Oranges talk to your Oranges

When the nature of your greatness will not build well into the greatness of the company that you stand behind think of those whose greatness will. By transitively building greatness you will not only benefit from what is built but also you will help build a community that requires acknowledgement of the support others give to build it. Without acknowledging those that have helped build a community the community will develop away from what has made it great to that point. Not only do communities you build in away rely on you to exist, people love to be helped and are more willing to help when they have been helped. By leading by example in a way you will show others how to show thanks and perpetuate the greatness that you have induced.

Thanks!

Till Next time! Maybe back to Set objects? Maybe some fun with styling? I always can learn more about css flex-box, grids, and div shaping. Maybe some dynamic styling is in order? Anyway tune in next week for another installment of Web Development with Ders –– The One-Stop-Shop for Everything....Ders

VS Code ShortCuts and Tricks

Anders Hornor — Wed, 09 Oct 2019 05:20:46 +0000

A brief overview of the shortcuts and tricks built into VS Code that have made my life easier.

Original Computerists: What d' I Gotta be to be O.C.

The original computers and computerists would know little of the thing we call a moust today. Before the modern day touch screen display we've all become so comfortable with today there was a thing called the trackpad, before that a little nub in the middle of your keyboard. Before that? A ball lodged into a stationary ergonomic block on your desk and Before that was the mouse made famous by not working on reflective flat surfaces. Before all that was the mouse that was distantly related to braces in its ability to store bits of things you've been eating for weeks. Before that a wooden block with two wheels on its bottom and a red button on top. Before that the one that catches food but as a military secret. Before that though!? Nothing. The original computerists were masters of the keyboard never lifting their hands off the desk. Computers are built around commands and mouses are really just tools that through a few hardwired levels of abstraction send out the commands that computers crave. As such everything you do on a computer should be doable from the keyboard. To my knowledge this isn't so much the case anymore but I'm no keyboard Wizard. I do know though that when grinding out some wicked functions, using the keyboard shortcuts and commands to their fullest makes life easier.

I use the text editor Visual Studio Code developed by Microsoft. Because Microsoft people do a lot with computers (some of the original computerists) and as such they built some handy shortcuts into their text editor.
Link to Install

*Disclaimer* I use a mac so for anyone running a Windows or Linux OS use the ctrl key in place of the ⌘. Also I get it O.C. has already been coined.

First Things First - Files From the Command Line

So I believe this tidbit is included in some aspect of the setup of VS Code but VS code has some easily implemented bash commands. Instead of having to set up a bash/shell command to open files in VS code yourself, using the ⇧⌘P then typing shell command into the search bar and selecting the first suggestion will add the command to your bash commands. Now typing code from any file or directory in the terminal will open that file or directory in VS code.

Now that VS code is easily accessible here are in-editor commands.
Cheat Sheets:
– Mac – Windows – Linux –

Shortcuts: Slices of Success

Quick Keyboard Reference List

⌘: command key
⌥: alt key
⌃: control key
⇧: shift key
←→↑↓: arrow keys
esc: escape key

General

Quick Search/Open File: ⌘P
Jump to Matching Bracket: ⇧⌘/
Show General Search: ⇧⌘F
Yes there is a Zen Mode: ⌘KZ (esc to exit)

Line Traversal: Live-Coding Keyboard Wizardry

Move Line Up/Down: ⌥↑ / ⌥↓
Go-to Beginning/End: fn← / fn→ or ⌘↑ / ⌘↓
Delete Line: ⇧⌘K
Go-to Line: ⌃G
Go-to File (aka "Quick Search/Open File): ⌘P
Go-to Symbol: ⇧⌘O
Show All Symbols: ⌘T

Integrated Terminal: The All-in-One-Place Place

Show Terminal: ^`
New Terminal: ^⇧`

That's it That's all...For Now

I can see your gears working...ok maybe not but all of these awesome built in shortcuts and commands will at least get you admission the WagHertz School of Keyboard Whizkidery. From there you have to... you know ... kill a guy – maybe a few – to make it to the top, but at least this'll get you there.

Till Next Time!

To thaat point, Good Luck!

JavaScript Set Objects - Episode II - Gettin' Jiggy Wit' it

Anders Hornor — Wed, 02 Oct 2019 03:56:36 +0000

In my first blog of this series I introduced the Set object. I outlined an instance in which the use of a Set object and its uniqueness check simplified an already overly complex function by making a placeholder hash and two iterative methods unnecessary. In this blog I will to cover some more methods built into the JS Set Objects and where they are useful.

`Set.prototype.add(value)` && `Set.prototype.delete(value)`

Like many other data stores Set objects have basic functions do introduce and remove elements from them. They are identical in use to the similar functions for Arrays and Hashes.

let set1 = new Set("set is so cool!")

  #=> Set(9) {"s","e","t"," ","i","o","c","l","!"}

set1.add("Wat?")

  #=> Set(10) {"s","e","t"," ","i","o","c","l","!","Wat?"}

set1.delete("i")

  #=> Set(9) {"s","e","t"," ","o","c","l","!","Wat?"}

`Set.prototype.has(value)`

Similar to Arrays Set objects have a built in class method that checks for particular values within the Set object. The method returns a boolean value depending on if the value is present(true) or not(false). This is super useful for powerful conditional functions.

if (set1.has("i")) {
  set1.delete("Wat?")
  set1.add("WAT!?")
}

console.log(set1)

  #=> Set(9) {"s","e","t"," ","o","c","l","!","Wat?"}

`Set.prototype.clear()`

As described in my first blog of this series Set objects are akin to a Hash Array hybrid in a way. Unlike either Set objects have an included function that works to empty the elements of the Set.

if (set1.has("Wat?")) {
  set1.clear()
}

  #=> Set(0)

`Set.prototype.entries()`

The Set object's built in class methods also break the Array-Hash paradigm with the Set.prototype.entries()method. This class method returns a SetIterator object that contains all the elements of the original Set object as key-value pairs where each key and value are the element (maybe succinct but definitely confusing examples FTW).

set2 = new Set("set is so cool!")

  #=> Set(9) {"s","e","t"," ","o","c","l","!"}

entries = set2.entries()

console.log(entries)

  #=> SetIterator {"s" => "s", "e" => "e", "t" => "t", " " => " ", "i" => 
  "i", "o" => "o", "c" => "c", "l" => "l", "!" => "!"}

`Set.prototype.values()` &&/|| `Set.prototype.keys()`

Back into the Hash-Array relationship Set objects have a similar function to hashes that returns the values or keys of the Set. Unlike Hashes the Set.prototype.values() and Set.prototype.keys() both return the same SetIterator object containing all of the elements of the original Set even when key-value pairs are present. Whence I am a famous programmer I will return to this post and explain why a SetIterator that is identical to the set its a part of. My inkling is that it has to do with efficiency. SetIterator objects have one class method, SetIterator.prototype.next(). ~My assumption~ is that they take less memory to store because they are similar to linked lists. Anyway, examples:

set2.values()

  #=> SetIterator {"s","e","t"," ","o","c","l","!"}

set2.keys()

  #=> SetIterator {"s","e","t"," ","o","c","l","!"}

let set3 = new Set([{"key": "value"},{"keys": "values"}])

set3.keys()

  #=> SetIterator {{"key": "value"},{"keys": "values"}}

set3.values()

  #=> SetIterator {{"key": "value"},{"keys": "values"}}

Next Time!

That is about it for Set. Thank you for checking out my blog! I plan to revisit this blog in the coming months when I am more knowledgeable about Set and all its wonderful uses. Till next time!