ronperrella.com - IT Observations and Insights

Success! Domain ronperrella.com was analyzed on !

DomainsData.org: IT Observations and Insights

Title:

IT Observations and Insights
Age:

14 years old
Alexa Rank:
Total Sites Linking In (Alexa):

0
Domain's IP Country:

United States
Status Code:

OK
IP Address:

192.185.32.226
Description:
Keywords:

ronperrella.com Whois Information:

1.

Domain Name:

ronperrella.com
2.

Domain Age:

14 years old
3.

Name Server 1:

ns91.hostgator.com
4.

Name Server 2:

ns92.hostgator.com
5.

Created:

Saturday 01. June 2002
6.

Expires:

Thursday 01. June 2017
7.

Domain Registrar:

godaddy.com, LLC

Website Important Html Tags:

TAG
TEXT
b
parse var
li
Describe the data file layout and structure
li
Describe why the structure is what it is
li
Describe legal values
li
Describe what changes are allowed
li
Describe the history of changes
li
Describe what program uses this data file
li
Describe assumptions about the data file
li
Include the checksum or digital signature for the file
li
Separate out clumps of records for readability
li
Comment out records with problems
li
Describe what version of the data schema is in use
div
Here is a short list of things that can
div
Just by looking at it, can you tell what the fields are? I hear some of you (really, I can mindread) saying "just look at the source code". Well, maybe you don't have the source. Maybe you don't know how to program in
div
There are data formats which include commenting ability, such as:
div
And, given that you might be using this file during testing, you might need to remove data. Commenting out that data AND providing a reason why might be a good idea.
div
Now, I will caution you that excessive commenting can cause the datafile to become unreadable (to humans - the computer doesn't care!) Use your own judgment.
div
Also, it is possible to go overboard (like any other human endeavor). For example, you can certainly use it for meta-data. But after while, you might find it easier just to include the meta data as data in the data file, rather than a comment. The comment is a good starting point, perhaps while you're still working out the schema.
div
As I learn about Docker, containerization, and micro-services, I can't help but think we've been down (part of) this road before. Without a doubt, there's a lot of innovation in Docker, so don't misunderstand me. However, I want to acknowledge the good parts of what I experienced long ago in my limited experience on IBM mainframes and perhaps there are some lessons to be learned here as well.
div
What else did the mainframe get right? Well, like modern containerization, it shares the operating system image among many VMs. This reduces the resource (memory) burden of having thousands of VMs. In addition, it uses a single tasking model (non-multithreaded) which is easy to program and has low overhead (a bit like NodeJS). Finally, it was programmed heavily using a scripting language for productivity. REXX was also the extension language for XEDIT (the text editor) and was used for everyday scripting (like AWK or PERL). REXX has a compiler if you need more speed as well.
div
Where did the mainframe go wrong? Not too many places. The service machine concept provides a nice isolated program. I don't know if you can scale them horizontally and I'm uncertain about the mechanisms for sharing across a network (mainframes talked both SNA and TCP/IP when I used them.) I do recall they had a mechanism for networking but I can't remember how it worked. This is pre-SSH so TN3270 was the primary way to connect as a user. Programs could talk over a different set of protocols. I also don't think the concept of service discovery was well established.
div
I have vastly simplified how things work and I'm sure I've gotten more than a few things wrong. Feel free to leave me comments and I'll be glad to make corrections.
div
This is an excellent podcast series I've been listening to for years. Great for roadtrips and vacations too.
h1
IT Observations and Insights
h2
Pages
h2
Fossil SCM for introductory programming courses
h2
Links
h2
Blog Archive
h2
Support Wikipedia
h2
Disclaimer
h3
Introduction
h3
Kinds of things you could write as comments
h3
Formats which allow comments
h3
Simple installation and no dependencies
h3
Simple consistent syntax
h3
Distributed Version Control System (DVCS)
h3
Built-in Trouble Tickets and Wiki
h3
Single file repository
h3
Adequate Performance
h3
Why not use Git?
h3
Conclusion

ronperrella.com IP Information:

1.

Ip Address:

192.185.32.226
2.

Country:

United States
3.

Status Code:

OK
4.

Region Name:

Texas
5.

City Name:

Houston
6.

Zip Code:

77092
7.

Speed test:

47.1 ms

ronperrella.com Alexa Information:

5 Websites linking to ronperrella.com:

Websites related to ronperrella.com:

Top Keywords from Search Engines:

Site Screenshots:

Screenshot created on

This is a screenshot of ronperrella.com, created on
Click on thumb to enlarge the screenshot.

Google Ranking Screenshots:

Screenshot created on

This is a Google Top 10 results' screenshot for keyword IT Observations and created on .
The position for keyword IT Observations and is: Not in top 10
Google Ranking Position checked from US (United States of America) Ip Address on .
Click on thumb to enlarge the screenshot.