Posts

APIs

Definition An API definition can be written from two perspectives (and the code for it could be too). An API is an interface used to access some of a platform's services. It can be created by the creator of the application, who wants their tool to easily be implemented by others, or it could be written by a programmer, hoping to make use of the functionality found in another program. Using an API has several benefits: Able to use the target program's services You don't have to rewrite the code, saving time and energy while moving up timelines Able to easily swap out the target program for another, if needed without having to rewrite too much code. Examples When one website talks to another website, an API is used. An example of this is when a news webpage include a comment section that's linked to Facebook; that's an API. Or your favorite online recipe that has a link to it's pinterest post, that's an API.  Another example is a game devel

Nullable

There is a parameter/value type that allows you to set a field to null. It's appropriately called "Nullable<T>". This comes in handy when designing a method to handle an incoming parameter as null. With some added logic, this could another way of effectively overloading a method or simply handling a null input parameter. This technique was especially useful when writing endpoints to an API controller.

Big List of Software Dev Tools

I created this list for quick and easy reference. This list includes tools I've been exposed to and is not exhaustive. I plan on adding more information on each item over time. - Visual Studios (Text Editor, Advanced IDE) - Blazor - Razor - Azure Cloud (WebHosting) - Postman (Test Tool,  read more ) - Fork (Repository) - TortoiseSVN (Repository) - GitHUB (Online Repository) - Visual Studio - MS SQL Server Management Studio

Postman

Image
Postman is a testing tool for developing APIs. I have a small amount of experience with this one, but came to love it very quickly while creating requests to send to an API I've been working on. The UI is intuitive, clean, and easy to use. From the request page, you're offered a selection of HTTP services, such as "Get," "Post," "Put," Delete," and more. You're able to select the Parameters ("Params"), Authorization, Headers, Body, Pre-Request Script, Tests, and Settings tabs to further configure your test request.  My favorite feature to date is in the Body tab. You can add an existing form to send, x-www-form-urlencoded, Raw, Binary, or GraphQL. When you select one of these types, such as Raw, a type box appears below and a drop down menu that allows you to select your type of text (text, javascript, json, html, or xml). Cool, right?! At the bottom of the application is a window with the returned response from the teste

C# - "This" Keyword

The this keyword is used fairly often, especially in class constructors and can also be found in class methods to explicitly specify that the following variable is a member of it's class. This basic example shows the use of the this keyword to explicitly call the class members and not the passed parameters within the scope of the constructor: class Car {     private int horsepower;     private string color;          public foo(int horsepower, string color)     {         this.horsepower = horsepower { get; }         this.color = color { get; }     } }  Notice the this keyword in the foo() method. If this was not used, we would have code that looked like this: class Car {     private int horsepower;     private string color;          public foo(int horsepower, string color)     {         horsepower = horsepower { get; }         color = color { get; }     } }  What do you think the difference will be when you instantiated a

Abbreviations

This page will contain a basic dictionary of abbreviations that I've been learning over my career and adding to this list 1 by 1. API: Application Programming Interface json: javascript object notation RTF: Rich Text Format TIFF: Tagged Image File Format XML: Extensible Markup Language dll: dynamic link library

Introduction

Image
Hello! And welcome to my CS blog! My name is, well, let's go with Undercover! I'm an electrical engineer, sort of... I got my degree in EE almost 3 years ago, but I've hardly been able to make much use of it! Since graduation, I've spent 2 years as a engineer for a USB test lab, more understanding and running tests than development, and 8 months at a missiles development company, and about a month at SoftSource Consulting LLC. During college, I took almost 4 years of internships, most of which focused on computer science and writing scripts in Python, which are not at all what I expected going into my EE career from day 1 of college. ( I LOVE this movie by the way ) I'm now head deep in software engineering without a strong software/cs background. I've done lots of learning on my own, but frequently find myself completely unaware of concepts that come up almost daily at work, concepts that may or may not have been taught in an undergrad degree (ex. SQL