The Soul of an Internet Machine Transistor (https://transistor.fm) https://feeds.transistor.fm/the-soul-of-an-internet-machine "The Soul of an Internet Machine". This show explores the intersection of business and technology and the internet. 2020 Fijre Media LLC d0a3bdd4-1828-5c75-a165-e9a295ba3867 no Trailer en Wed, 23 Jul 2025 10:36:12 -0400 Tue, 02 Dec 2025 16:51:15 -0500 https://ChristinaMoore.us/ https://img.transistor.fm/VkScOovQwH20NUJ7qEsqQJQvcGR3ckyFS-JrNj11Yyo/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE1MzQzLzE2MDI2/OTUxNzAtYXJ0d29y/ay5qcGc.jpg The Soul of an Internet Machine https://ChristinaMoore.us/ episodic Christina Mcdonald Moore "The Soul of an Internet Machine". This show explores the intersection of business and technology and the internet. "The Soul of an Internet Machine". technology, internet, the cloud, oracle, apex, business Christina Mcdonald Moore christina@christinamoore.us No No Print That! 2023 2023 7 7 Print That! full 9ef38879-292d-4b02-9094-3da9fa54bfa9 https://share.transistor.fm/s/2a92f369 Engaging a team of software developers requires expertise, patience, and communication between the development team and team that owns and understands needs of the business. There are times that business can operate well with commercial software applications. Some businesses buy multiple tools. At some moment, the leaders within a company acknowledge that their internal or external business workflows are inefficient, or inaccurate, or incompatible with their other technology.  

Is there something about your business that sets you apart from the other businesses? What is your competitive advantage? What are the messages you are sending to your clients? Invoicing represents a classic example of this topic. 

What is an invoice? First definition: It is a document that communicates what a client owes a vendor.

During this episode we will explore how an Oracle database can produce a document and we will explore some of the ways that organizations use and design invoices. 

]]> Engaging a team of software developers requires expertise, patience, and communication between the development team and team that owns and understands needs of the business. There are times that business can operate well with commercial software applications. Some businesses buy multiple tools. At some moment, the leaders within a company acknowledge that their internal or external business workflows are inefficient, or inaccurate, or incompatible with their other technology.  

Is there something about your business that sets you apart from the other businesses? What is your competitive advantage? What are the messages you are sending to your clients? Invoicing represents a classic example of this topic. 

What is an invoice? First definition: It is a document that communicates what a client owes a vendor.

During this episode we will explore how an Oracle database can produce a document and we will explore some of the ways that organizations use and design invoices. 

]]> Fri, 03 Mar 2023 07:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2478 Engaging a team of software developers requires expertise, patience, and communication between the development team and team that owns and understands needs of the business. There are times that business can operate well with commercial software applications. Some businesses buy multiple tools. At some moment, the leaders within a company acknowledge that their internal or external business workflows are inefficient, or inaccurate, or incompatible with their other technology.  

Is there something about your business that sets you apart from the other businesses? What is your competitive advantage? What are the messages you are sending to your clients? Invoicing represents a classic example of this topic. 

What is an invoice? First definition: It is a document that communicates what a client owes a vendor.

During this episode we will explore how an Oracle database can produce a document and we will explore some of the ways that organizations use and design invoices. 

]]> technology, internet, the cloud, oracle, apex, business No A Heavy Lift 2023 2023 6 6 A Heavy Lift full e83c027d-7489-4a8b-8de5-cfe8a25e729a https://share.transistor.fm/s/c035e527 Construction contractors and many other trades love to see scope changes and project expansion. Project expansion and scope changes increase revenue and often increase the size of a team. Sometimes the need for more done at a faster rate comes introduces risk to a project. Using modern software development techniques whereby the team work in 2-4 week sprints, we often see issues long before we must deal with them. How does one solve problems that remain at the horizon? I argue that a mature team works towards the unknown together acknowledging the squishy-bits. We should stand together, client and developer, embracing the challenges – studying them. 

]]> Construction contractors and many other trades love to see scope changes and project expansion. Project expansion and scope changes increase revenue and often increase the size of a team. Sometimes the need for more done at a faster rate comes introduces risk to a project. Using modern software development techniques whereby the team work in 2-4 week sprints, we often see issues long before we must deal with them. How does one solve problems that remain at the horizon? I argue that a mature team works towards the unknown together acknowledging the squishy-bits. We should stand together, client and developer, embracing the challenges – studying them. 

]]> Fri, 17 Feb 2023 06:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2555 Let’s examine two questions common to software development projects. First, Can complementary tasks create adversarial competition? Second, when to bring more programmers on to a team. The answers depend on the mission and an assessment of what causes delays. As the team narrows the focus, we “begin with the end in mind” discovering objectives of the applications. Let’s examine two questions common to software development projects. First, Can complementary tasks create adversarial competition? Second, when to bring more programmers on to a team. The answers depend on the mission and an assessment of what causes del technology, internet, the cloud, oracle, apex, business No The Color of Language 2023 2023 5 5 The Color of Language full af2ccc7f-ece0-4ae5-8f4f-1b26ac11b6cc https://share.transistor.fm/s/cee15372 When we start a new software project we “swing with a big hammer”, standing up structures and framework quickly. What we build resembled the both the native Oracle APEX environment plus the client’s colors, logos, and fonts. Through this initial framework, we, the development team, offered a vision. From here a shared vision developed through shared work. We also needed to accommodate the multiple languages of French, Dutch, and the English that the developers depended on. We need to comply with European data privacy laws which are stricter than those in the United States. Building a robust application that accommodates the nuanced complexities that our client will require to differentiate and support their business practices, we design speed and resilience into our system. Designing for speed, also means avoiding techniques that rob us of speed.
Speed within a database environment involves honor a series of rules called “Data Normalization”. A discussion about data normalization typically involves slides discussing abstract rules about optimizing complex data within a database environment. Edgar “Ted” Codd, born in 1923, invented the relational model for database management. He worked for IBM. He received the Turing Award in 1981. Dr. Cobb developed the relational model for databases in 1969. Sixty years later, his initial work expanded. The initial data normalization steps I learned have expanded and some nomenclature changed.
The amazing thing to me is that people being invented relational databases. And people invented programming languages. Today, we argue about these topics forgetting the humanity underpinning these technologies. 
My favorite college professor, John Jungck, stood before his Bio 101 course each year to give a lecture called: “There are No Facts”. Unlike modern disputes about facts, he forced no political agenda. He challenged each in the audience to approach science and technology with an open mind. We must eschew assumptions. “Oh, you think two plus two equals four?” Then he reaches under the lectern. He pours two liters of clear water-like fluid into a container with two liters of clear water-like fluid. The total was a bit less than the expected four liters. A bit of chemistry happened given that one of the fluids was not water. Bluntly put, he performed a parlor trick for us. As an illustration, it works. He encouraged student to be curious, skeptical, and carry a bit of doubt when people get dogmatic about anything.
All of this technology we use to build and support software applications results from inventions and ideas that came the mind of people. People like you and like me. We invented it all. 
When honoring the process of normalizing data, we gain speed and maximize performance within relational databases. I do promise, we are talking about how to manage multiple spoken languages within a database. 
In Episode 2 “Data Tables”, I mentioned that my colleague Dirk provided us with 132 data table definitions filling over 5000 lines of text. I discussed the importance of a unique primary key for each row, or record, of data. One row of data contained the data profile for precisely one subject. One example was the customer table. The customer table has a primary key called the customer_pk. All of the data within that row must related to that exact customer. If it doesn’t related to or describe an element of the client’s profile, then it does not belong. 
That statement of “fact”, which I surrounded with quotes, complies with the First Normal Form of data. Thank you Doctor Cobb. You documented this idea and stamped it with a name in 1970.
When a data row has a singular primary key, as our customer table does with the customer_pk, then it meets the standards for the Second Normal Form. Well done us. This seems obvious to software developers. It seems so obvious to some that we forget the intelligence and humanity behind this concept. 
Database tables relate to each other. We do not store each and every invoice within the customer table. Instead, we create a table that stores the invoice data. In that table, we’ll have a unique primary key called invoice_pk (meeting both the first and second normal forms – well done us). In the second position of that invoice table, we keep the foreign key for the customer table. That foreign key, our team calls customer_fk. I look at that knowing instantly that invoices relate to customers and the customer foreign key connects to the customer primary key. We break the data into logical and non-duplicating elements. 
For example, some may opt to put a customer’s address in the customer table. Here’s the street name, the municipality name, the state or province, and the postal code. Suddenly, we find a customer with two addresses. Or maybe one address is for mailing and the other is for shipping. Maybe one address is the physical address, etc. We have all experienced this complexity. When I order from an online vendor, I have one postal code for our physical address and a separate postal code for our mailing address. When I want items shipped to our home, I use the postal code for a municipality that is 50 kilometers east of us. The credit card statement goes to a different postal code which carries a different municipality name. Neither of these agree with the emergency services (or 911/999) address for our farm. That is a third address. Yes, all of these three addresses land on our 40 hectare property clinging to the side of the world’s oldest mountain range. 
To manage complexity of addresses, we ought to have a table for addresses. The first column is reserved for the address primary key (yes, of course it is called address_pk). The second column is then the customer foreign key (customer_fk). 
These relationships and efforts to segregate data into a parent/child relationship satisfies the third normal form. Customer is a parent to both address and invoices. In human-speak, one customer may have zero, one, or more addresses. One customer may have zero, one, or more invoices. The parent table may have zero, one, or more related child rows of data in other tables. 
I have always had difficulty in telling a story about the 4th normal form of relational data. It is a subtle shift in perception of data duplication. In the prior forms, we strove to eliminate the duplication of data within a row. In short, the normalization process discourages us from having fields such as Address 1 and Address 2 and Address 3 and Address 4 in our tables. We should pull that mess out to create an address table, then simplify the customer table. We want to remove these duplicate-like fields of Address 1, Address 2, Address 3. It makes our lives easier. Picture a customer with only 1 address. Can you picture how to handle a customer with four addresses? How do we handle that?
In the 4th Normal Form, we strive to reduce redundancy between rows of data. In the Second normal form, we don’t want to keep adding fields to accommodate new and more address for a customer. That’s inefficient and difficult to write. It brings more problems than it solves, Dr Cobb was right. 
In the 4th Normal Form, we reduce the number of rows by creating related tables. Imagine that each contact at a customer also included the customers address, the customer’s primary phone number, and such. In this example, five rows of contact data would have the same Customer Name. Five rows would have the same address. Five rows would have the same phone numbers. This can result in table having compound keys. The most important data fields are duplicated. When searching for the contacts for Acme Company, I get five rows with the name Acme Company. I see five rows with the same phone number and five rows with the same address. Imagine that two of my contact people have the surname Gonzales. What if a father-son duo work there. We suddenly have Pablo Go...

]]> When we start a new software project we “swing with a big hammer”, standing up structures and framework quickly. What we build resembled the both the native Oracle APEX environment plus the client’s colors, logos, and fonts. Through this initial framework, we, the development team, offered a vision. From here a shared vision developed through shared work. We also needed to accommodate the multiple languages of French, Dutch, and the English that the developers depended on. We need to comply with European data privacy laws which are stricter than those in the United States. Building a robust application that accommodates the nuanced complexities that our client will require to differentiate and support their business practices, we design speed and resilience into our system. Designing for speed, also means avoiding techniques that rob us of speed.
Speed within a database environment involves honor a series of rules called “Data Normalization”. A discussion about data normalization typically involves slides discussing abstract rules about optimizing complex data within a database environment. Edgar “Ted” Codd, born in 1923, invented the relational model for database management. He worked for IBM. He received the Turing Award in 1981. Dr. Cobb developed the relational model for databases in 1969. Sixty years later, his initial work expanded. The initial data normalization steps I learned have expanded and some nomenclature changed.
The amazing thing to me is that people being invented relational databases. And people invented programming languages. Today, we argue about these topics forgetting the humanity underpinning these technologies. 
My favorite college professor, John Jungck, stood before his Bio 101 course each year to give a lecture called: “There are No Facts”. Unlike modern disputes about facts, he forced no political agenda. He challenged each in the audience to approach science and technology with an open mind. We must eschew assumptions. “Oh, you think two plus two equals four?” Then he reaches under the lectern. He pours two liters of clear water-like fluid into a container with two liters of clear water-like fluid. The total was a bit less than the expected four liters. A bit of chemistry happened given that one of the fluids was not water. Bluntly put, he performed a parlor trick for us. As an illustration, it works. He encouraged student to be curious, skeptical, and carry a bit of doubt when people get dogmatic about anything.
All of this technology we use to build and support software applications results from inventions and ideas that came the mind of people. People like you and like me. We invented it all. 
When honoring the process of normalizing data, we gain speed and maximize performance within relational databases. I do promise, we are talking about how to manage multiple spoken languages within a database. 
In Episode 2 “Data Tables”, I mentioned that my colleague Dirk provided us with 132 data table definitions filling over 5000 lines of text. I discussed the importance of a unique primary key for each row, or record, of data. One row of data contained the data profile for precisely one subject. One example was the customer table. The customer table has a primary key called the customer_pk. All of the data within that row must related to that exact customer. If it doesn’t related to or describe an element of the client’s profile, then it does not belong. 
That statement of “fact”, which I surrounded with quotes, complies with the First Normal Form of data. Thank you Doctor Cobb. You documented this idea and stamped it with a name in 1970.
When a data row has a singular primary key, as our customer table does with the customer_pk, then it meets the standards for the Second Normal Form. Well done us. This seems obvious to software developers. It seems so obvious to some that we forget the intelligence and humanity behind this concept. 
Database tables relate to each other. We do not store each and every invoice within the customer table. Instead, we create a table that stores the invoice data. In that table, we’ll have a unique primary key called invoice_pk (meeting both the first and second normal forms – well done us). In the second position of that invoice table, we keep the foreign key for the customer table. That foreign key, our team calls customer_fk. I look at that knowing instantly that invoices relate to customers and the customer foreign key connects to the customer primary key. We break the data into logical and non-duplicating elements. 
For example, some may opt to put a customer’s address in the customer table. Here’s the street name, the municipality name, the state or province, and the postal code. Suddenly, we find a customer with two addresses. Or maybe one address is for mailing and the other is for shipping. Maybe one address is the physical address, etc. We have all experienced this complexity. When I order from an online vendor, I have one postal code for our physical address and a separate postal code for our mailing address. When I want items shipped to our home, I use the postal code for a municipality that is 50 kilometers east of us. The credit card statement goes to a different postal code which carries a different municipality name. Neither of these agree with the emergency services (or 911/999) address for our farm. That is a third address. Yes, all of these three addresses land on our 40 hectare property clinging to the side of the world’s oldest mountain range. 
To manage complexity of addresses, we ought to have a table for addresses. The first column is reserved for the address primary key (yes, of course it is called address_pk). The second column is then the customer foreign key (customer_fk). 
These relationships and efforts to segregate data into a parent/child relationship satisfies the third normal form. Customer is a parent to both address and invoices. In human-speak, one customer may have zero, one, or more addresses. One customer may have zero, one, or more invoices. The parent table may have zero, one, or more related child rows of data in other tables. 
I have always had difficulty in telling a story about the 4th normal form of relational data. It is a subtle shift in perception of data duplication. In the prior forms, we strove to eliminate the duplication of data within a row. In short, the normalization process discourages us from having fields such as Address 1 and Address 2 and Address 3 and Address 4 in our tables. We should pull that mess out to create an address table, then simplify the customer table. We want to remove these duplicate-like fields of Address 1, Address 2, Address 3. It makes our lives easier. Picture a customer with only 1 address. Can you picture how to handle a customer with four addresses? How do we handle that?
In the 4th Normal Form, we strive to reduce redundancy between rows of data. In the Second normal form, we don’t want to keep adding fields to accommodate new and more address for a customer. That’s inefficient and difficult to write. It brings more problems than it solves, Dr Cobb was right. 
In the 4th Normal Form, we reduce the number of rows by creating related tables. Imagine that each contact at a customer also included the customers address, the customer’s primary phone number, and such. In this example, five rows of contact data would have the same Customer Name. Five rows would have the same address. Five rows would have the same phone numbers. This can result in table having compound keys. The most important data fields are duplicated. When searching for the contacts for Acme Company, I get five rows with the name Acme Company. I see five rows with the same phone number and five rows with the same address. Imagine that two of my contact people have the surname Gonzales. What if a father-son duo work there. We suddenly have Pablo Go...

]]> Fri, 03 Feb 2023 06:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2042 The inventions, designs, and concepts developed during the 1970s guide modern software development practices. They work. They are efficient. In the 21st Century, our software must support multiple cultures, multiple languages and bring a degree of flexibility the early pioneers did not design into their practices. How do we accommodate both? During the episode, we explored the impact of assumptions we make. We explored historical assumptions and guidance about how data ought to be structured then I presented exceptions to these “rules”. When developing complex systems, we must find ways through complex challenges. The inventions, designs, and concepts developed during the 1970s guide modern software development practices. They work. They are efficient. In the 21st Century, our software must support multiple cultures, multiple languages and bring a degree of flexibi technology, internet, the cloud, oracle, apex, business No Middleware 2023 2023 4 4 Middleware full 36343206-5ec3-4ad0-839d-46a5f9b8ddb1 https://share.transistor.fm/s/5bdb3f72 The first time I heard the phrase middleware, I was writing software for FedEx with a terrific team of Oracle developers in the late 1990s. I had to ask for a definition. In short, middleware is software that run between two things. Middleware is software that is invisible to the user. Middleware is software but seems to fall outside the accepted definitions of an application or app. It is software’s own software-based infrastructure. Does that make any sense? Probably not.
I wrote my first lines of code on a PDP-11 microcomputer from Digital Electronics Corporation (DEC) during high school. I attended a school in a wealthy area surrounded by the massively burgeoning IT industry.  In my high school, four years before the IBM-PC came to the market, I learned BASIC. The name literally meant “Beginner’s All-purpose Symbolic Instruction Code”, and no does not relate to the American slang basic, which seems to be a bit of an insult. 

10 BEGIN 

20 PRINT “HELLO WORLD”

30 END


Hard to imagine how these building blocks gave us the world of modern digital commerce. Those roots go back even farther. That trip requires tipping our hat in honor of Ada Lovelace, Alen Turing.
My educational progression followed the global development of software and software tools. In 1982, heading to university, I bought an IBM-PC for $2,500. That was the discount a university professor got. Adjusted for 2022 dollars, the cost would approximate $7,500. 
As a college first year, I thought I would study computer science. Regrettably, my university’s systems were older than my high school’s systems. No way was I going to learn how to program in assembly language on a huge mainframe computer. Mainframes, in 1982, were already doomed, so I thought. I never wanted to write an operating system, which was one of the capstone assignments. 
I finally took CS-111 as an independent study. In a class by myself, I read Cooper and Clancy’s “Oh Pascal” learning the software language Pascal. That book remains on the shelf behind me in my office today. 
At the age of 28, I had already been a contributing author and technical editor for books about computer programming. Two evenings a week, I stood in front of a group of adults teaching programming skills at a community college. One high school elective and single independent study course for one semester started me on my career. While an autodidact, nearly all I learned fell beyond the reach of classrooms. School never came easily to me, likely because of my learning differences. 
I watch colleagues like Dimitri in awe. In direct comparison, I see that I fraud and the idiot, even today. We’re all like that though, aren’t we? We get good at something, or we get recognition then we tell ourselves: No, I don’t deserve this. From my perspective, he is better skilled that I, smarter than I. I admire he jumps between programming languages and environments.
I mentioned Pascal on purpose, not just as the rambling digression (I do love my digressions though). The programming language I use for work today had been built from Pascal. Oracle, when needing to create a procedural programming language borrowed heavily from Pascal. Pascal is an imperative and procedural programming language, a natural progression for me from BASIC. The language had been designed by Niklaus Wirth. Mr. Wirth, who is 88 years old in 2022, won the Turing Prize in 1984, roughly the same year I learned Pascal. 
Stevie and I write code in Oracle’s PL/SQL language. The language derived from an earlier structured procedural language called Pascal, that I learned at university after learning BASIC in high school. We declare variables at the top of a subroutine. We write code in logical subroutines called procedures or functions. These get compiled by Oracle into the database as something that is no longer intelligible to human readers. These routines / subroutines form building blocks within the database to perform tasks, typically with data. One might need a routine that calculates the total value of an invoice. That routine must spin through each line of data for an invoice. The routine identifies the quantity of items ordered. It then multiplies quantity by the unit price to generate the value of that invoice line. Then we tally the total of the invoice lines to get the invoice total. We, the developers, must control this process precisely, due to the variations needed. When do you round the numbers to two decimal places? When do you calculate the taxes? How do you handle items that are not taxed. How to you calculate discounts? Each of these steps must follow the client’s instructions and we must do it precisely. The process and math must be consistent and transparent. Someone will run a calculator through the numbers to confirm the math. Later, an auditor will verify every bit of it. Nothing can be hidden. 
That’s the land of managing the boring business data: customer contacts, invoice information, inspection data, reporting, document management, bank balances, reservations, etc. My world.
Our software depends on a user running the application within a browser. The user updates a customer’s profile or generates a service order. Those tasks such as presenting the data entry web pages to the user’s browser is accomplished by Oracle APEX. I do not have to write the JavaScript and HTML and CSS required to make an application operate within a browser. 98% web-based applications rely on JavaScript. 100% of web-based applications depend on HTML and CSS. We tell the browser to paint a region blue by setting the region’s color property to blue. We do not tell the browser how to do the painting. We only specify the color. We don’t tell a browser how to draw a line, we specify the thickness and style of the line. I won’t present a sample of object-oriented code to read. It doesn’t read well, maybe it is hard to hear: onclick= “void(0);”
When I look at our applications written in Oracle APEX, the apps can look different on the different browsers. Occasionally, in Firefox, I see fonts with serif instead of the sans-serif font specified by our team. These variations are reminders of a key difference between procedural languages and object-oriented languages. With object-oriented languages, such as JavaScript, the browser decides how to execute a process. The browser’s own personality expresses itself a bit. 

One might argue that the process of formatting and presenting data to users via a browser could be called “edge-ware”. Browsers and JavaScript is software sitting at the edge of an application. Edge-ware, a term absolutely nobody uses, sits at the edge of a software application formatting and presenting our pages to the user. Ok, if you do an internet search on Edge-ware, you will find a village in New Zealand and a couple of companies. Let’s also quietly acknowledge that JavaScript is used on servers too. That is a more recent development. 
The user logs into our Oracle APEX application via browser. The data travels back and forth between the user and the Oracle server via the internet. For illustrative purposes, the Oracle Server sits in the middle of the internet, the “Cloud”. Users sit at the edge of the cloud with their phones, tablets, laptops, and desktop computers. And let’s add cars, refrigerators, doorbell cameras, modern televisions – these all sit at the edge of the cloud with you the user.  
The spirit of “edge-ware” tells a story. 
If we have lovely object-oriented software running on the client-side, or edge, of our applications. And we have lovely software written in a procedural language compiled within the Oracle database, then how does the client/edge talk to the server and the database? Say “Hello” to middleware.

Middleware is like a Babelfish (for fans of Hitchhiker’s Guide books)...

]]> The first time I heard the phrase middleware, I was writing software for FedEx with a terrific team of Oracle developers in the late 1990s. I had to ask for a definition. In short, middleware is software that run between two things. Middleware is software that is invisible to the user. Middleware is software but seems to fall outside the accepted definitions of an application or app. It is software’s own software-based infrastructure. Does that make any sense? Probably not.
I wrote my first lines of code on a PDP-11 microcomputer from Digital Electronics Corporation (DEC) during high school. I attended a school in a wealthy area surrounded by the massively burgeoning IT industry.  In my high school, four years before the IBM-PC came to the market, I learned BASIC. The name literally meant “Beginner’s All-purpose Symbolic Instruction Code”, and no does not relate to the American slang basic, which seems to be a bit of an insult. 

10 BEGIN 

20 PRINT “HELLO WORLD”

30 END


Hard to imagine how these building blocks gave us the world of modern digital commerce. Those roots go back even farther. That trip requires tipping our hat in honor of Ada Lovelace, Alen Turing.
My educational progression followed the global development of software and software tools. In 1982, heading to university, I bought an IBM-PC for $2,500. That was the discount a university professor got. Adjusted for 2022 dollars, the cost would approximate $7,500. 
As a college first year, I thought I would study computer science. Regrettably, my university’s systems were older than my high school’s systems. No way was I going to learn how to program in assembly language on a huge mainframe computer. Mainframes, in 1982, were already doomed, so I thought. I never wanted to write an operating system, which was one of the capstone assignments. 
I finally took CS-111 as an independent study. In a class by myself, I read Cooper and Clancy’s “Oh Pascal” learning the software language Pascal. That book remains on the shelf behind me in my office today. 
At the age of 28, I had already been a contributing author and technical editor for books about computer programming. Two evenings a week, I stood in front of a group of adults teaching programming skills at a community college. One high school elective and single independent study course for one semester started me on my career. While an autodidact, nearly all I learned fell beyond the reach of classrooms. School never came easily to me, likely because of my learning differences. 
I watch colleagues like Dimitri in awe. In direct comparison, I see that I fraud and the idiot, even today. We’re all like that though, aren’t we? We get good at something, or we get recognition then we tell ourselves: No, I don’t deserve this. From my perspective, he is better skilled that I, smarter than I. I admire he jumps between programming languages and environments.
I mentioned Pascal on purpose, not just as the rambling digression (I do love my digressions though). The programming language I use for work today had been built from Pascal. Oracle, when needing to create a procedural programming language borrowed heavily from Pascal. Pascal is an imperative and procedural programming language, a natural progression for me from BASIC. The language had been designed by Niklaus Wirth. Mr. Wirth, who is 88 years old in 2022, won the Turing Prize in 1984, roughly the same year I learned Pascal. 
Stevie and I write code in Oracle’s PL/SQL language. The language derived from an earlier structured procedural language called Pascal, that I learned at university after learning BASIC in high school. We declare variables at the top of a subroutine. We write code in logical subroutines called procedures or functions. These get compiled by Oracle into the database as something that is no longer intelligible to human readers. These routines / subroutines form building blocks within the database to perform tasks, typically with data. One might need a routine that calculates the total value of an invoice. That routine must spin through each line of data for an invoice. The routine identifies the quantity of items ordered. It then multiplies quantity by the unit price to generate the value of that invoice line. Then we tally the total of the invoice lines to get the invoice total. We, the developers, must control this process precisely, due to the variations needed. When do you round the numbers to two decimal places? When do you calculate the taxes? How do you handle items that are not taxed. How to you calculate discounts? Each of these steps must follow the client’s instructions and we must do it precisely. The process and math must be consistent and transparent. Someone will run a calculator through the numbers to confirm the math. Later, an auditor will verify every bit of it. Nothing can be hidden. 
That’s the land of managing the boring business data: customer contacts, invoice information, inspection data, reporting, document management, bank balances, reservations, etc. My world.
Our software depends on a user running the application within a browser. The user updates a customer’s profile or generates a service order. Those tasks such as presenting the data entry web pages to the user’s browser is accomplished by Oracle APEX. I do not have to write the JavaScript and HTML and CSS required to make an application operate within a browser. 98% web-based applications rely on JavaScript. 100% of web-based applications depend on HTML and CSS. We tell the browser to paint a region blue by setting the region’s color property to blue. We do not tell the browser how to do the painting. We only specify the color. We don’t tell a browser how to draw a line, we specify the thickness and style of the line. I won’t present a sample of object-oriented code to read. It doesn’t read well, maybe it is hard to hear: onclick= “void(0);”
When I look at our applications written in Oracle APEX, the apps can look different on the different browsers. Occasionally, in Firefox, I see fonts with serif instead of the sans-serif font specified by our team. These variations are reminders of a key difference between procedural languages and object-oriented languages. With object-oriented languages, such as JavaScript, the browser decides how to execute a process. The browser’s own personality expresses itself a bit. 

One might argue that the process of formatting and presenting data to users via a browser could be called “edge-ware”. Browsers and JavaScript is software sitting at the edge of an application. Edge-ware, a term absolutely nobody uses, sits at the edge of a software application formatting and presenting our pages to the user. Ok, if you do an internet search on Edge-ware, you will find a village in New Zealand and a couple of companies. Let’s also quietly acknowledge that JavaScript is used on servers too. That is a more recent development. 
The user logs into our Oracle APEX application via browser. The data travels back and forth between the user and the Oracle server via the internet. For illustrative purposes, the Oracle Server sits in the middle of the internet, the “Cloud”. Users sit at the edge of the cloud with their phones, tablets, laptops, and desktop computers. And let’s add cars, refrigerators, doorbell cameras, modern televisions – these all sit at the edge of the cloud with you the user.  
The spirit of “edge-ware” tells a story. 
If we have lovely object-oriented software running on the client-side, or edge, of our applications. And we have lovely software written in a procedural language compiled within the Oracle database, then how does the client/edge talk to the server and the database? Say “Hello” to middleware.

Middleware is like a Babelfish (for fans of Hitchhiker’s Guide books)...

]]> Fri, 20 Jan 2023 06:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2057 Modern software operates within the Cloud or internet. Software requires its own software infrastructure. Some code runs on the Cloud or internet servers. Some code runs within the user’s browser. These languages are different. The back-end software tends to be structured procedural languages. The client-side software tends to be written using object oriented languages. And what runs between the client and the server? Modern software operates within the Cloud or internet. Software requires its own software infrastructure. Some code runs on the Cloud or internet servers. Some code runs within the user’s browser. These languages are different. The back-end software tends technology, internet, the cloud, oracle, apex, business No Framework 2023 2023 3 3 Framework full f588a19c-2bfc-47a8-b9e2-2ec111488cb4 https://share.transistor.fm/s/b327048a I have started so many projects in my life and career. More often, I remember the end of a project. The end of a project means friends disappear. Comfortable familiarity and expertise fades. Sometimes with massive and exhaustive projects, I get sick for a while. When it goes well, I feel snuggly connected to those around me. Leaving Iraq after a year, left me drained, and I failed to keep in tough with others from those days. They also did not keep in touch with me either. That happens after projects end. I did write a colleague from my days at FedEx where we wrote software in Oracle together. This was in the mid to later 1990s. His email had not changed. Our lives had changed during the decades. When revising these teams and times, I find pleasure in the grueling and difficult environment. I find pleasure in remembering the quiet moments and the surprising moments with teammates. 

In the 2023 series of “The Soul of an Internet Machine”, I am making my second attempt at narrating the beginning of a project. As series 1 informs us, projects fail. Teams fail. Things fall apart. The globe faces a pandemic, etc. 

In December of 2021, I tempered my enthusiasm about starting a new project with reminders of past failures

Often during years of looking for projects, I see organizations especially our U.S. government looking for software developers. They hire Fred from here and Bugsy from there. Here is Mickey from another place. The bosses say: We need software, so I’ll hire developers. 

That process often fails. That process certainly costs more money. That process results in immediate, and often systemic problems.

Let us explore this together. Electrotest demonstrated immediately the complexity of their demands plus the scope of the project, possibly lasting years. Electrotest, any client or employer, requires us to build them tools that improve their operations. We are expected to improve revenue, reduce expense, improve consistency, reduce regulatory risk, and make the work environment easier on their staff. When the work environment is easier and logical and rhythmic and symmetrical, then training new folks is easier; error rates decrease; and I’ll argue that job satisfaction improves. 

All too often a bank or a government entity says: Hey, we need to improve our software. The natural result then is hiring programmers. Programmers write software. We want software, therefore we hire programmers. If this is a big project, hire five or ten. If a small project, hire three. The bosses say: we hear Oracle is good. We need Oracle programmers. Or they decide on Microsoft or another brand. 

The first thing the individual programmers do is introduce themselves. The second thing they do is argue. They argue about standardization, about techniques, about which what is better. We invented a genre of television shows predicated on this experience. The brand “Survivor” comes to mind. 

One might approach the challenge in one of two ways. I recommend finding a team that had built their credentials and products working together. They arrive with as the “Pros from Dover” often ready to go. They know how to work together. They know each other’s strengths and weaknesses. They possess team shortcuts; team tools; team standards. Their team’s leadership process had been established long before your project. Furthermore, the team tends to success, or fail, together. Their loyalty often focuses on the team instead of their own individual ambitions. We build together, we succeed together. If one of us faces problems, we turn to each other within the team to provide support, love, time, or training – what ever is required. 

The common choice with many organizations leaps to the conclusion that programmers write software. If you need software, hire programmers. Those assumptions often fail to create an amazing team. Without an amazing cohesive team, you don’t get good software (or a good anything). 

Good code requires good thinking. Good thinking results in good code. You must hire a team that can think well together, communicate well together, and meet your already impossible deadlines and expectations. Any minute that requires resolving disputes or cleaning up messes costs time, energy, money, and often drains emotions unnecessarily.

“Did you do your PSTs?” 
“Are you walking the dog or is that dog still walking you around?” 
“Did you find the long pole in the tent?” 
“I need a rubber-duck.”
“Paint with a little brush”
“Maintain parallel construction”
“Trust the tools”
“Baby Steps”
“Crawl, walk, run”
“Time for a big hammer”
“Begin with the end in mind”
“Semper Gumby”
“Retreat, regroup, return”
“Establish a baseline, change one variable, test, repeat.”
“A then B then C”
“Sometimes good enough is good enough”

These phrases form a team’s shorthand. I don’t know the shorthand that Steven Spielberg’s team has. Certainly, a team’s phrases embody the spirit, ethos, and soul of a team. That’s what builds great software. 
By January 7th or 10th of 2021, we had an operational application running. Technically, we had two applications running. Yet on January 4th, I was still making improvements to the original table structures. I’d make suggestions then beg for approval. That often resulted in difficult phone calls and tension. Dirk and I had never met. We created a demonstration of the worst that happens when you stick two strangers together in a development environment. He was the boss in his mind. I was the boss in my mind. My table designs were better than his. His data table designs came from months of work and numerous meetings with the client for approvals. Dirk and I conflicted continuously. 
APEX stands at the top of software development tools that are considered low-code/no-code. At the simplest, one can select, drag, and drop data field onto web pages. APEX includes user authentication and user authorization processes. The name APEX derives from a concatenation of Application and Express. APEX resides as a native element within Oracle’s database. It turns a classic server-side database application developer like me to a cool, hip, web-based application developer. I am not required to know CSS nor JavaScript. People create complete applications without writing any code in PL/SQL (Oracles procedure programming language). Nor are folks required to write queries with SQL. This is the definition of low-code/no-code. 
That takes an application only so far. When you have scores of tables and data for those tables that each need a quick means of management, drag-and-drop is lovely. It is fast. 
APEX provides standardized and familiar menu systems that resemble the types of menus one sees at on-line shopping sites, banks, and credit cards. I do not have to build that stuff. I don’t care too either. In the early minutes of a project, creating a framework for an application or a suite of interconnected applications ought to be simple, fast, reliable, and consistent. 
Additionally, I do not want to spent time worrying about the responsiveness of an application. It ought to look great and function fine on a mobile phone platform, a tablet, a laptop, and large-sized monitors often found on an office desk. 
Somebody else solved that problem already. I don’t need to replicate that. I certainly don’t want to introduce my own mistakes. As the technology related to presenting an application on a web browser improves, I don’t need to chase those improvements around. HTML version 4, then HTML version 5. CSS progressing through the years, now using variable substitutions. Cool, mature, growing up. Yay. Well done HTML and CSS. 
Oracle’s history spans back to the early 1970s as a relational database tool. There are few c...

]]> I have started so many projects in my life and career. More often, I remember the end of a project. The end of a project means friends disappear. Comfortable familiarity and expertise fades. Sometimes with massive and exhaustive projects, I get sick for a while. When it goes well, I feel snuggly connected to those around me. Leaving Iraq after a year, left me drained, and I failed to keep in tough with others from those days. They also did not keep in touch with me either. That happens after projects end. I did write a colleague from my days at FedEx where we wrote software in Oracle together. This was in the mid to later 1990s. His email had not changed. Our lives had changed during the decades. When revising these teams and times, I find pleasure in the grueling and difficult environment. I find pleasure in remembering the quiet moments and the surprising moments with teammates. 

In the 2023 series of “The Soul of an Internet Machine”, I am making my second attempt at narrating the beginning of a project. As series 1 informs us, projects fail. Teams fail. Things fall apart. The globe faces a pandemic, etc. 

In December of 2021, I tempered my enthusiasm about starting a new project with reminders of past failures

Often during years of looking for projects, I see organizations especially our U.S. government looking for software developers. They hire Fred from here and Bugsy from there. Here is Mickey from another place. The bosses say: We need software, so I’ll hire developers. 

That process often fails. That process certainly costs more money. That process results in immediate, and often systemic problems.

Let us explore this together. Electrotest demonstrated immediately the complexity of their demands plus the scope of the project, possibly lasting years. Electrotest, any client or employer, requires us to build them tools that improve their operations. We are expected to improve revenue, reduce expense, improve consistency, reduce regulatory risk, and make the work environment easier on their staff. When the work environment is easier and logical and rhythmic and symmetrical, then training new folks is easier; error rates decrease; and I’ll argue that job satisfaction improves. 

All too often a bank or a government entity says: Hey, we need to improve our software. The natural result then is hiring programmers. Programmers write software. We want software, therefore we hire programmers. If this is a big project, hire five or ten. If a small project, hire three. The bosses say: we hear Oracle is good. We need Oracle programmers. Or they decide on Microsoft or another brand. 

The first thing the individual programmers do is introduce themselves. The second thing they do is argue. They argue about standardization, about techniques, about which what is better. We invented a genre of television shows predicated on this experience. The brand “Survivor” comes to mind. 

One might approach the challenge in one of two ways. I recommend finding a team that had built their credentials and products working together. They arrive with as the “Pros from Dover” often ready to go. They know how to work together. They know each other’s strengths and weaknesses. They possess team shortcuts; team tools; team standards. Their team’s leadership process had been established long before your project. Furthermore, the team tends to success, or fail, together. Their loyalty often focuses on the team instead of their own individual ambitions. We build together, we succeed together. If one of us faces problems, we turn to each other within the team to provide support, love, time, or training – what ever is required. 

The common choice with many organizations leaps to the conclusion that programmers write software. If you need software, hire programmers. Those assumptions often fail to create an amazing team. Without an amazing cohesive team, you don’t get good software (or a good anything). 

Good code requires good thinking. Good thinking results in good code. You must hire a team that can think well together, communicate well together, and meet your already impossible deadlines and expectations. Any minute that requires resolving disputes or cleaning up messes costs time, energy, money, and often drains emotions unnecessarily.

“Did you do your PSTs?” 
“Are you walking the dog or is that dog still walking you around?” 
“Did you find the long pole in the tent?” 
“I need a rubber-duck.”
“Paint with a little brush”
“Maintain parallel construction”
“Trust the tools”
“Baby Steps”
“Crawl, walk, run”
“Time for a big hammer”
“Begin with the end in mind”
“Semper Gumby”
“Retreat, regroup, return”
“Establish a baseline, change one variable, test, repeat.”
“A then B then C”
“Sometimes good enough is good enough”

These phrases form a team’s shorthand. I don’t know the shorthand that Steven Spielberg’s team has. Certainly, a team’s phrases embody the spirit, ethos, and soul of a team. That’s what builds great software. 
By January 7th or 10th of 2021, we had an operational application running. Technically, we had two applications running. Yet on January 4th, I was still making improvements to the original table structures. I’d make suggestions then beg for approval. That often resulted in difficult phone calls and tension. Dirk and I had never met. We created a demonstration of the worst that happens when you stick two strangers together in a development environment. He was the boss in his mind. I was the boss in my mind. My table designs were better than his. His data table designs came from months of work and numerous meetings with the client for approvals. Dirk and I conflicted continuously. 
APEX stands at the top of software development tools that are considered low-code/no-code. At the simplest, one can select, drag, and drop data field onto web pages. APEX includes user authentication and user authorization processes. The name APEX derives from a concatenation of Application and Express. APEX resides as a native element within Oracle’s database. It turns a classic server-side database application developer like me to a cool, hip, web-based application developer. I am not required to know CSS nor JavaScript. People create complete applications without writing any code in PL/SQL (Oracles procedure programming language). Nor are folks required to write queries with SQL. This is the definition of low-code/no-code. 
That takes an application only so far. When you have scores of tables and data for those tables that each need a quick means of management, drag-and-drop is lovely. It is fast. 
APEX provides standardized and familiar menu systems that resemble the types of menus one sees at on-line shopping sites, banks, and credit cards. I do not have to build that stuff. I don’t care too either. In the early minutes of a project, creating a framework for an application or a suite of interconnected applications ought to be simple, fast, reliable, and consistent. 
Additionally, I do not want to spent time worrying about the responsiveness of an application. It ought to look great and function fine on a mobile phone platform, a tablet, a laptop, and large-sized monitors often found on an office desk. 
Somebody else solved that problem already. I don’t need to replicate that. I certainly don’t want to introduce my own mistakes. As the technology related to presenting an application on a web browser improves, I don’t need to chase those improvements around. HTML version 4, then HTML version 5. CSS progressing through the years, now using variable substitutions. Cool, mature, growing up. Yay. Well done HTML and CSS. 
Oracle’s history spans back to the early 1970s as a relational database tool. There are few c...

]]> Fri, 06 Jan 2023 06:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2149 Success in developing a software application depends entirely on the people. A client can short cut some of the risks by engaging a team that carries experience working together. Some clients hire individual programmers wishing that skills and techniques prove compatible. They think: I need software. I’ll hire programmers. A better practice involves finding a team where the individual possess individual expertise and a history of collaborating successfully. They build software together, support it together, then take on another project. Success in developing a software application depends entirely on the people. A client can short cut some of the risks by engaging a team that carries experience working together. Some clients hire individual programmers wishing that skills and techniques technology, internet, the cloud, oracle, apex, business No Data Tables 2023 2023 2 2 Data Tables full f2b8023f-5d86-454d-a25a-b332a588e734 https://share.transistor.fm/s/a6b7bda4 During the last half-century, we revise the terminology related to the early days of a software design process. Hopefully, when we ignore dogma, the goals are the same. We, the developers, must create tools for clients that work to improve process. Pragmatically, the process is a bit messier than the ideal suggests it should be. Step 2 then Step 4, then maybe circle back to Step 1 or 3. That’s life isn’t it?

Instead of getting client requirements in December as a means of starting the project, I got handed hundreds of data table definitions. With my experience I could read these data tables and read the data presented in other formats and reverse engineer the process. I could do this while simultaneously seeing flaws in the not-a-design. How?

How can I look at hundreds of tables and do this?

Accounting systems, invoice generation, inventory systems have been around for decades. The architecture remains consistent. They are based on analog processes well established by accounting traditions. The buzz words are ERP and CRM: Enterprise Resource Planning and Customer Resource Management (or Contact Resource Management). These systems date to the earliest days of commercial software. The first real test for “computer” systems – I put computer in quotes followed this progression:

1.       Calendar Calculations including celestial positions. These calculations help ocean navigators know their position on the globe. Think: Astrolabe, even Stonehenge. Estimate of eclipses, moon phases, and seasons. 

2.       Census tabulation – That’s where Herman Hollerith made is mark at the turn of the 20th Century. His thing eventually became IBM. 

3.       Ballistic Trajectories – how much energy does it take to launch a thingy from here and land there with precision. Hey, it was World War II, we wanted to hit a few targets. This stuff tied into the post-war Space Race. During the space race, we used early computers to aim a rocket at the Moon.

4.       Accounting.

Our team is expert at seeing data structures and workflows for back-office business functions such as managing funds, managing documents, and managing process. We explore the use and role of a data table in an Oracle relational database. 

My father, when talking about writing said: Maintain Parallel Construction. Parallel construction techniques lend to punchier writing. Picture a dynamic preacher delivering a sermon with rhythm. You can anticipate; the preacher pulls you along – or so I recall, been a while since I stepped into a church for a sermon. 

We create these patterns deep within the buried infrastructure of code for the power it brings later in construction. These techniques improve efficiency. These techniques reduce the risk of errors. You don’t accidently refer to the wrong foreign key, the wrong table.

The early work was good and accurate enough for us to start. We delivered a preliminary model and framework to the client by the first week of January 2022. I might have been rude and horrible, but we delivered a remarkable framework and first pass at the application before the end of the first week of January 2022. 

]]> During the last half-century, we revise the terminology related to the early days of a software design process. Hopefully, when we ignore dogma, the goals are the same. We, the developers, must create tools for clients that work to improve process. Pragmatically, the process is a bit messier than the ideal suggests it should be. Step 2 then Step 4, then maybe circle back to Step 1 or 3. That’s life isn’t it?

Instead of getting client requirements in December as a means of starting the project, I got handed hundreds of data table definitions. With my experience I could read these data tables and read the data presented in other formats and reverse engineer the process. I could do this while simultaneously seeing flaws in the not-a-design. How?

How can I look at hundreds of tables and do this?

Accounting systems, invoice generation, inventory systems have been around for decades. The architecture remains consistent. They are based on analog processes well established by accounting traditions. The buzz words are ERP and CRM: Enterprise Resource Planning and Customer Resource Management (or Contact Resource Management). These systems date to the earliest days of commercial software. The first real test for “computer” systems – I put computer in quotes followed this progression:

1.       Calendar Calculations including celestial positions. These calculations help ocean navigators know their position on the globe. Think: Astrolabe, even Stonehenge. Estimate of eclipses, moon phases, and seasons. 

2.       Census tabulation – That’s where Herman Hollerith made is mark at the turn of the 20th Century. His thing eventually became IBM. 

3.       Ballistic Trajectories – how much energy does it take to launch a thingy from here and land there with precision. Hey, it was World War II, we wanted to hit a few targets. This stuff tied into the post-war Space Race. During the space race, we used early computers to aim a rocket at the Moon.

4.       Accounting.

Our team is expert at seeing data structures and workflows for back-office business functions such as managing funds, managing documents, and managing process. We explore the use and role of a data table in an Oracle relational database. 

My father, when talking about writing said: Maintain Parallel Construction. Parallel construction techniques lend to punchier writing. Picture a dynamic preacher delivering a sermon with rhythm. You can anticipate; the preacher pulls you along – or so I recall, been a while since I stepped into a church for a sermon. 

We create these patterns deep within the buried infrastructure of code for the power it brings later in construction. These techniques improve efficiency. These techniques reduce the risk of errors. You don’t accidently refer to the wrong foreign key, the wrong table.

The early work was good and accurate enough for us to start. We delivered a preliminary model and framework to the client by the first week of January 2022. I might have been rude and horrible, but we delivered a remarkable framework and first pass at the application before the end of the first week of January 2022. 

]]> Fri, 23 Dec 2022 06:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2438 Software development process typically follows a series of steps that start with gathering requirements, developing a technical response, architecture, reviews, then construction. Reality slips in surprises and occasionally messes up the order. Software development process typically follows a series of steps that start with gathering requirements, developing a technical response, architecture, reviews, then construction. Reality slips in surprises and occasionally messes up the order. technology, internet, the cloud, oracle, business, electrotest No Series 2 Introduction - Electrotest 2023 2023 1 1 Series 2 Introduction - Electrotest full a26d2a50-d72e-48d9-8635-2f9afee554d4 https://share.transistor.fm/s/bbe2949b My colleague Stephanie, or Stevie, and I have working together for over six years. We’ve written commercial software that has managed billions in U.S. federal government funds. We’ve written software that helps an airline inspect their ramp operations. In the past, I worked on a team that use software to catch bad guys. The Electrotest project started in December of 2021. The audience for this podcast includes business folks who must manage data, manage software, or manage software development. Additionally, the audience includes technical folk interested in Oracle database application development. 


I blend story-based narrative with some technology and real-world business examples.


We learned of the project during the fall of 2021 as negotiations became an open secret within our team. I designated 06 DEC 2021 as the official start of the project. Reviewing my email one year later, I see that through the middle part of December of 2021, we were transitioning from one European-based client to this new client in Belgium. On 22 December 2021, I have an email with the subject line: een paar issues meaning “a few issues”.  


We spent most of that month finding our footing. We set up the tools needed to share code via GitHub. We established our management process with tickets and workflows. In our first European/Belgium project, we were late to the team. We came in with specific expertise. We communicated only with the existing development team who were located in Slovenia and Belgium. We never met the client. Lovely project. We came in as the “pros from Dover”. 

Through this podcast, I intend to illustrate that: 

  • Writing code is writing.
  • Writing code is elegant.
  • Writing code is story telling.
  • Beautifully written code is beautiful. 
  • Well written code follows a streamline, logical, precise process called thinking.

My father, a novelist, once said: “Writing well requires thinking well”. My corollary to that statement is that: “Good code requires good thinking”. No one can write good code without clarity. 

I derive the same satisfaction from writing code as I do from writing stories. That thought; that vision; that story; that process in my brain needs to be communicated to another. That thought needs to be understood by another. That thought, when communicated, must be logical. My friend and colleague in Belgium seduced me by stating that this project is ours. We will start from scratch, from a white piece of blank paper, from an empty database, from a green field that has never been turned. The statement proved to be a little wrong. Who cares, he proved himself to be mostly correct. Yay! 

We are a couple of North American programmers based on the East Coast. I am in New England. Stevie is in Virginia. Eli, whom you’ll meet later in the series, lives now in Washington State. Our client and project manager live in Belgium. We got hired for this job precisely because we are experts in back-office functions such as invoicing, regulatory affairs, document management and all of the boring things that keeps our global economy rolling along.

Our client is a Belgium firm called Electrotest. This company inspects industrial and residential properties focusing on regulatory compliance and health/safety concerns. These are the guys who inspect lifts/elevators and cranes and smoke detection systems and fuel/petrol stations. If there exists a nexus between safety, health, and human occupation, then Electrotest is likely to inspect it. In some cases, the inspections fall within governmental guidelines. In some cases, the inspections are required by the domestic gas companies of Belgium. In some cases, they provide the home or electrical inspections related to new construction or home sales. 

For listeners in the United States, this process does relate. Nearly all of us have stood in a hotel lift/elevator reading the safety certificate. In the U.S., this certificate tends to be issued by a municipal or local government official. Following new construction or remodeling of a home or office, a local government official tends to inspect and certify plumbing, electrical systems, fire prevent/fire detection systems. In the U.S. these processes are fragmented by municipal, state, and federal regulations. The Kingdom of Belgium has a population of more than 11.5 million people. The New York City metropolitan area has 20 million residents. New York City metropolitan area is about half the size of Belgium at 12000 square kilometers. Belgium is about 30000 square kilometers. The central government of Belgium seems both a bit more centralized than the US, but also complicated by having multiple cultural and language borders which sometimes have their own regulatory scope. For example, rules in Flanders may differ from Wallonia. 

Seriously, who wants simple?

Writing software for Electrotest to perform and report on their inspections is a bit simpler because of the stronger and centralized nature of these health and safety regulations. In my rural Vermont town where we trade eggs for homemade bacon and hang hams in the basement, I do my own electrical work. I’ve redone most of the plumbing in this house. We don’t do inspections here. There are no inspectors. It simply isn’t a thing. But a few kilometers over the line into Massachusetts, the process follows different rules because it is a different state. And we have fifty-four or fifty-five states (or state-like entities). I know, our flag only has 50 stars. There are 4 million American citizen in Puerto Rico who have no rights to vote in our national election, get no representation in our Congress, have no star on our flag, etc. We exceed others with our inconsistencies and shenanigans. 

From their offices near Brussels, Electrotest is able to provide inspection services to individuals (particularen) and corporations throughout Belgium. 

What does Electrotest need?

Bluntly, they need everything we can offer. Their staff appear excellent at their duties. Before we met them, they generated nearly 50,000 invoices per year by hand using Microsoft Excel Spreadsheets. I will say this often during the 2023 series of “The Soul of an Internet Machine”, Excel is the world’s worst database. In fact, it is not a database. Oh, go argue with me. Blah, blah, you can query from column and select stuff, blah, blah. Go ahead, I’ll ignore you. Databases are relational and robust. Database use internal rules to maintain data integrity. Databases manage large, robust, complex data with grace and ease (if you have developers like us who make it graceful and easy). I shall not dive deeper in to their manual and internal system. They made the decision to modernize. We praise that decision. To their credit, they have tried numerous systems both commercial and custom over the years to make some improvements.

Can we automate systems for invoicing and save them money? How do we do that? Is money leaking out of their manual processes? Are they or were they losing money due to process management?

  • Can we automate processes for pricing?
  • Can we automate the processes needed for taking a service order?
  • Can we automate and standardize the process of generating inspection reports?

The first time I saw the CEO of Electrotest get quoted in the press for her endeavors she did not focus on the financial gains. Instead, she revealed several specific climate goals for the software. I never once thought that back-office automation of a national company could or would have a positive impact on climate policies. She made the connection.


In an early release, St...

]]> My colleague Stephanie, or Stevie, and I have working together for over six years. We’ve written commercial software that has managed billions in U.S. federal government funds. We’ve written software that helps an airline inspect their ramp operations. In the past, I worked on a team that use software to catch bad guys. The Electrotest project started in December of 2021. The audience for this podcast includes business folks who must manage data, manage software, or manage software development. Additionally, the audience includes technical folk interested in Oracle database application development. 


I blend story-based narrative with some technology and real-world business examples.


We learned of the project during the fall of 2021 as negotiations became an open secret within our team. I designated 06 DEC 2021 as the official start of the project. Reviewing my email one year later, I see that through the middle part of December of 2021, we were transitioning from one European-based client to this new client in Belgium. On 22 December 2021, I have an email with the subject line: een paar issues meaning “a few issues”.  


We spent most of that month finding our footing. We set up the tools needed to share code via GitHub. We established our management process with tickets and workflows. In our first European/Belgium project, we were late to the team. We came in with specific expertise. We communicated only with the existing development team who were located in Slovenia and Belgium. We never met the client. Lovely project. We came in as the “pros from Dover”. 

Through this podcast, I intend to illustrate that: 

  • Writing code is writing.
  • Writing code is elegant.
  • Writing code is story telling.
  • Beautifully written code is beautiful. 
  • Well written code follows a streamline, logical, precise process called thinking.

My father, a novelist, once said: “Writing well requires thinking well”. My corollary to that statement is that: “Good code requires good thinking”. No one can write good code without clarity. 

I derive the same satisfaction from writing code as I do from writing stories. That thought; that vision; that story; that process in my brain needs to be communicated to another. That thought needs to be understood by another. That thought, when communicated, must be logical. My friend and colleague in Belgium seduced me by stating that this project is ours. We will start from scratch, from a white piece of blank paper, from an empty database, from a green field that has never been turned. The statement proved to be a little wrong. Who cares, he proved himself to be mostly correct. Yay! 

We are a couple of North American programmers based on the East Coast. I am in New England. Stevie is in Virginia. Eli, whom you’ll meet later in the series, lives now in Washington State. Our client and project manager live in Belgium. We got hired for this job precisely because we are experts in back-office functions such as invoicing, regulatory affairs, document management and all of the boring things that keeps our global economy rolling along.

Our client is a Belgium firm called Electrotest. This company inspects industrial and residential properties focusing on regulatory compliance and health/safety concerns. These are the guys who inspect lifts/elevators and cranes and smoke detection systems and fuel/petrol stations. If there exists a nexus between safety, health, and human occupation, then Electrotest is likely to inspect it. In some cases, the inspections fall within governmental guidelines. In some cases, the inspections are required by the domestic gas companies of Belgium. In some cases, they provide the home or electrical inspections related to new construction or home sales. 

For listeners in the United States, this process does relate. Nearly all of us have stood in a hotel lift/elevator reading the safety certificate. In the U.S., this certificate tends to be issued by a municipal or local government official. Following new construction or remodeling of a home or office, a local government official tends to inspect and certify plumbing, electrical systems, fire prevent/fire detection systems. In the U.S. these processes are fragmented by municipal, state, and federal regulations. The Kingdom of Belgium has a population of more than 11.5 million people. The New York City metropolitan area has 20 million residents. New York City metropolitan area is about half the size of Belgium at 12000 square kilometers. Belgium is about 30000 square kilometers. The central government of Belgium seems both a bit more centralized than the US, but also complicated by having multiple cultural and language borders which sometimes have their own regulatory scope. For example, rules in Flanders may differ from Wallonia. 

Seriously, who wants simple?

Writing software for Electrotest to perform and report on their inspections is a bit simpler because of the stronger and centralized nature of these health and safety regulations. In my rural Vermont town where we trade eggs for homemade bacon and hang hams in the basement, I do my own electrical work. I’ve redone most of the plumbing in this house. We don’t do inspections here. There are no inspectors. It simply isn’t a thing. But a few kilometers over the line into Massachusetts, the process follows different rules because it is a different state. And we have fifty-four or fifty-five states (or state-like entities). I know, our flag only has 50 stars. There are 4 million American citizen in Puerto Rico who have no rights to vote in our national election, get no representation in our Congress, have no star on our flag, etc. We exceed others with our inconsistencies and shenanigans. 

From their offices near Brussels, Electrotest is able to provide inspection services to individuals (particularen) and corporations throughout Belgium. 

What does Electrotest need?

Bluntly, they need everything we can offer. Their staff appear excellent at their duties. Before we met them, they generated nearly 50,000 invoices per year by hand using Microsoft Excel Spreadsheets. I will say this often during the 2023 series of “The Soul of an Internet Machine”, Excel is the world’s worst database. In fact, it is not a database. Oh, go argue with me. Blah, blah, you can query from column and select stuff, blah, blah. Go ahead, I’ll ignore you. Databases are relational and robust. Database use internal rules to maintain data integrity. Databases manage large, robust, complex data with grace and ease (if you have developers like us who make it graceful and easy). I shall not dive deeper in to their manual and internal system. They made the decision to modernize. We praise that decision. To their credit, they have tried numerous systems both commercial and custom over the years to make some improvements.

Can we automate systems for invoicing and save them money? How do we do that? Is money leaking out of their manual processes? Are they or were they losing money due to process management?

  • Can we automate processes for pricing?
  • Can we automate the processes needed for taking a service order?
  • Can we automate and standardize the process of generating inspection reports?

The first time I saw the CEO of Electrotest get quoted in the press for her endeavors she did not focus on the financial gains. Instead, she revealed several specific climate goals for the software. I never once thought that back-office automation of a national company could or would have a positive impact on climate policies. She made the connection.


In an early release, St...

]]> Fri, 09 Dec 2022 06:00:00 -0500 Christina Moore Christina Moore 1875 As a modern-day tool-smith, my colleagues and I build the software machines or tools of the modern economy. We developing a applications using tools from Oracle, United Codes, and others. Who is the audience for “The Soul of an Internet Machine”? Let’s start with the curious; curious about technology; curious about history; curious about business processes and entrepreneurship; curious about invention and product development; curious about science. Is that you? Developing software is a human endeavor. Two people talk. Two people share an idea. They build a vision together. They then build towards that vision together. Building is sexy. Building is fun. YouTube is filled with makers making stuff, just like this podcast. As a modern-day tool-smith, my colleagues and I build the software machines or tools of the modern economy. We developing a applications using tools from Oracle, United Codes, and others. Who is the audience for “The Soul of an Internet Machine”? Let’s technology, Oracle, APEX, Electrotest No Echoes of a Lincoln Song 1 1 13 13 Echoes of a Lincoln Song full ccb6241d-8b29-402c-a022-9fac54f519e1 https://share.transistor.fm/s/3b3f6210  Echoes of a Lincoln Song

Listeners I am putting out this story for your enjoyment and dedicating it to two friends: Lynda Copeland and Ginny Lemire. I wrote this piece upon request of my mother in 2003, before I moved back to my native New England and before spent a year in Iraq (2005/2006). It is written about the Town of Lincoln MA, the town of my youth.

Lincoln sits between Lexington and Concord, famous for the battled of the 19th of April 1775. The bloodiest fighting of that day’s battle and the capture of Paul Revere both happened in Lincoln. My mother wanted a little story for a publication she was working on.

Read more: https://ChristinaMoore.us/echoes-of-a-lincoln-song/

]]>  Echoes of a Lincoln Song

Listeners I am putting out this story for your enjoyment and dedicating it to two friends: Lynda Copeland and Ginny Lemire. I wrote this piece upon request of my mother in 2003, before I moved back to my native New England and before spent a year in Iraq (2005/2006). It is written about the Town of Lincoln MA, the town of my youth.

Lincoln sits between Lexington and Concord, famous for the battled of the 19th of April 1775. The bloodiest fighting of that day’s battle and the capture of Paul Revere both happened in Lincoln. My mother wanted a little story for a publication she was working on.

Read more: https://ChristinaMoore.us/echoes-of-a-lincoln-song/

]]> Wed, 03 Feb 2021 07:45:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 620 Childhood echoes in my today’s movements and actions. This lyrical piece explores the forest of my youth and the history of my long-ago home. Written about Lincoln Massachusetts, tucked between Lexington and Concord, once and still surrounded by literary, political, and scientific giants. I seek treasures, find awe, and rustle oak fallen oak leaves. Childhood echoes in my today’s movements and actions. This lyrical piece explores the forest of my youth and the history of my long-ago home. Written about Lincoln Massachusetts, tucked between Lexington and Concord, once and still surrounded by literary, technology, internet, the cloud, oracle, apex, business No Chapter 12 | Its Just Work 1 1 12 12 Chapter 12 | Its Just Work full 381c315f-06de-4369-ab4f-f0f3ac643241 https://share.transistor.fm/s/27e8d39a For transcription and notes, click over to https://ChristinaMoore.us/its-just-work/

]]> For transcription and notes, click over to https://ChristinaMoore.us/its-just-work/

]]> Wed, 27 Jan 2021 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1123 Sometimes all of the work smarter, better tools, teamwork boils down to focusing on the job and doing it. Nike says it well: Just do it! A team-building phrase that does carry sympathy and understanding and the tenderness of acknowledging, that work what we get paid to do. It is just work – with deadlines, and challenges, and tiny rewards. Ain’t no real short cuts, but I do find joy in working. Do others? Sometimes all of the work smarter, better tools, teamwork boils down to focusing on the job and doing it. Nike says it well: Just do it! A team-building phrase that does carry sympathy and understanding and the tenderness of acknowledging, that work what technology, internet, the cloud, oracle, apex, business No Episode 11 | PST Baby: Primary Secondary Tertiary 1 1 11 11 Episode 11 | PST Baby: Primary Secondary Tertiary full 30cf534d-bfd5-4216-878c-1962125f1ed4 https://share.transistor.fm/s/8d1f629e Show notes, transcriptions and other information can be found at https://ChristinaMoore.us/pst/

]]> Show notes, transcriptions and other information can be found at https://ChristinaMoore.us/pst/

]]> Wed, 20 Jan 2021 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1492 “What could possibly go wrong?” Around here, if there is one plan there are three plans. We’ve got to have the primary plan, then the backup plan then the other plan for when it all goes entirely wrong. PST – a reminder to start with a primary plan, a secondary plan, and a tertiary plan. Embracing failure may improve our lives, our work, and our teams. “What could possibly go wrong?” Around here, if there is one plan there are three plans. We’ve got to have the primary plan, then the backup plan then the other plan for when it all goes entirely wrong. PST – a reminder to start with a primary plan, a se Oracle, Oracle APEX, planning, PST, primary secondary tertiary, USS George Washington, FedEx Flight 14, plane crash, data management, programming, software development, entrepreneurship, business management, team management, team planning, crisis management, disaster recovery No Chapter 10 | How to Hold an Axe 1 1 10 10 Chapter 10 | How to Hold an Axe full f13b1b65-6020-40bc-bb12-7ecd3f2f2828 https://share.transistor.fm/s/1d26e37c For transcript and notes: https://ChristinaMoore.us/how-to-hold-an-axe/ or follow me on twitter @cmoore_sp

]]> For transcript and notes: https://ChristinaMoore.us/how-to-hold-an-axe/ or follow me on twitter @cmoore_sp

]]> Wed, 13 Jan 2021 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1650 Great teams, great teamwork requires planning, effort, and a handful of cute phrases. A team of software developers likely don’t need to hold an axe. “How to Hold an Axe” represents the importance of the suite of tools we do use daily. Excellence is deliberate. Join us as we explore team work and tool management… Great teams, great teamwork requires planning, effort, and a handful of cute phrases. A team of software developers likely don’t need to hold an axe. “How to Hold an Axe” represents the importance of the suite of tools we do use daily. Excellence is delib team work, centers for excellence, software development, oracle, oracle pl/sql, oracle apex No Chapter 9 | The First Minute 1 1 9 9 Chapter 9 | The First Minute full 69ddc294-580a-4fcb-8979-3fd3cf76766f https://share.transistor.fm/s/a047dfaa Wed, 16 Dec 2020 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1805 Ever think about the seconds immediately after buying something online? You get an email. You may have been added to a mailing list. In the seconds buying our product, there are 14 steps, 4 vendors, and thousands of lines of instructions. All invisible, all immediate. When it works, money flows into a bank account. When it goes badly, sweat drips, anxiety soars, and bosses pace. Follow the haps and mishaps of a software development team starting a new venture with a new product on the Soul of an Internet Machine. Ever think about the seconds immediately after buying something online? You get an email. You may have been added to a mailing list. In the seconds buying our product, there are 14 steps, 4 vendors, and thousands of lines of instructions. All invisible, a Okta, Oracle, Oracle APEX, Recurly, Avalara, funnel, innovative entrepreneur, female tech founders, small business ownership, designing software as a service, podcasting No Chapter 8 | Okta 1 1 8 8 Chapter 8 | Okta full f8244bb1-13c9-4e33-b702-3c48519d6c70 https://share.transistor.fm/s/9d939448 Head over to https://ChristinaMoore.us/okta/ for transcript, notes and more

]]> Head over to https://ChristinaMoore.us/okta/ for transcript, notes and more

]]> Wed, 09 Dec 2020 07:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1762 The sales team from IBM, DEC, Data General, and Xerox were noted for their arrogance and uniformity during the prior century. In 2019, I heard echoes of that sort of arrogance from Okta – a firm specializing in user authentication and identity management – the tools one needs to simplify logging into internet-based software. Listen in on a sales call, and step through a catastrophic failure with our team. The sales team from IBM, DEC, Data General, and Xerox were noted for their arrogance and uniformity during the prior century. In 2019, I heard echoes of that sort of arrogance from Okta – a firm specializing in user authentication and identity management Okta, IBM, DEC, Data General, DG, identity management, user authentication, women and innovation, historical perspective of cloud computing, software architecture, building a SaaS application Yes Chapter 7 | Wayfair Wayside 1 1 7 7 Chapter 7 | Wayfair Wayside full d4e449dd-ebf4-40f8-8e3c-4a6c386a792e https://share.transistor.fm/s/0a5a7af5 For transcript and full show notes, head to https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> For transcript and full show notes, head to https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 02 Dec 2020 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1013 The United States Supreme Court changed the landscape of internet commerce with a 2018 ruling called “South Dakota v Wayfair Inc”. With the stroke of five pens, business had to comply with thousands of sales tax jurisdictions within the United States – up to 58 states and territories, 3,000 counties, 10s of thousands of municipalities all want revenue from internet-based sales. This determination opened businesses to new risks. It created an entirely new business venture called: interstate sales tax compliance service provider. And new phrases such as “SST” for streamlined sales tax process. It will cost small business thousands of dollars to comply. For us, compliance will cost more than the taxes we pay. The United States Supreme Court changed the landscape of internet commerce with a 2018 ruling called “South Dakota v Wayfair Inc”. With the stroke of five pens, business had to comply with thousands of sales tax jurisdictions within the United States – up South Dakota v Wayfair Inc, Scotus, supreme course, SST, streamlined sales tax, interstate sales tax compliance service provider, sales tax, entrepreneurship, innovation, cloud computing No Chapter 6 | Recurly 1 1 6 6 Chapter 6 | Recurly full 570840fd-0b7e-40d4-b6a3-8b4e6e1b3292 https://share.transistor.fm/s/b292a337 Show notes, transcription and more at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Show notes, transcription and more at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 25 Nov 2020 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 2098 Integrating yet another vendor into our software suite permits us to replace PayPal, the effort lets us explore how to sell to a reluctant audience, how to reach customers with strong defenses, and give me a platform to discuss cluttered, noisy, and crappy websites. Maybe marketing people should accept the idea that the customer isn’t exactly who you think they are. The ideal customer is one who has money and looking for a solution or a product. Integrating yet another vendor into our software suite permits us to replace PayPal, the effort lets us explore how to sell to a reluctant audience, how to reach customers with strong defenses, and give me a platform to discuss cluttered, noisy, and crapp Software-as-a-service, saas, Recurly, software design, paypal, south Dakota v Wayfair, female entrepreneur, women in technology, api, application programming interface, women in technological advancement, designing SaaS, best practices in cloud-based software design and development No Chapter 5 | PayPal 1 1 5 5 Chapter 5 | PayPal full bae6b767-3585-452d-9bab-80992b44999d https://share.transistor.fm/s/531dc729 For show notes, downloadable transcript and more head to the website: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> For show notes, downloadable transcript and more head to the website: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 18 Nov 2020 08:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1349 Paypay is a legacy in a market they created and now they are irrelevent... they've abandoned their own market. lesson: listen to your customers or lose 'em Paypay is a legacy in a market they created and now they are irrelevent... they've abandoned their own market. lesson: listen to your customers or lose 'em historical perspective of computer technology, entrepreneurship and innovation, software design and development, this history of APIs,paypal,women in technological advancement,women in cloud-based computing No Chapter 4 | Plans 1 1 4 4 Chapter 4 | Plans full 6fad8007-5bba-4476-b0d3-3c0ebcdfbe20 https://share.transistor.fm/s/7fbd8454 Transcripts and more located at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Transcripts and more located at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 11 Nov 2020 01:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 940 The perfect plans for PodcastFlow did not survive the first months. The plans never anticipated a global shut down. And the plans failed to have the flexibility to respond to failures. This chapter does offer a checklist of 6 tasks for branding a product or company on the internet. The perfect plans for PodcastFlow did not survive the first months. The plans never anticipated a global shut down. And the plans failed to have the flexibility to respond to failures. This chapter does offer a checklist of 6 tasks for branding a product women in business, designing SaaS, paypal, the speed of technological change, adjusting on the fly, Flexibility,adaptability No Chapter 3 | The Machine 1 1 3 3 Chapter 3 | The Machine full 5bff8360-c481-416b-9422-ae22f99bdc47 https://share.transistor.fm/s/f300d976 For transcripts, show notes, and other information please visit the website: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> For transcripts, show notes, and other information please visit the website: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 04 Nov 2020 01:00:00 -0500 Christina Mcdonald Moore Christina Mcdonald Moore 1287 PodcastFlow is an internet machine. PodcastFlow completes a series of tasks, has some automation, required designing and building, and it uses energy. Our machine sits in the Center of the Internet – The Cloud. It uses cloud computing and cloud storage. It is hardware and software. It has digital data connectors to several vendors. The machine is a bunch of different parts that work together. When you stand on the outside of that machine, it just looks like magic. PodcastFlow is an internet machine. PodcastFlow completes a series of tasks, has some automation, required designing and building, and it uses energy. Our machine sits in the Center of the Internet – The Cloud. It uses cloud computing and cloud storage. I Computer technology, cloud computing, software design, software development, designing software-as-a-service, cloud-based software, women in business, women in computing, women and technology innovation No Chapter 2 | The Cloud 1 1 2 2 Chapter 2 | The Cloud full 41b4e4f9-f2d0-434f-b736-7aab88f4c850 https://share.transistor.fm/s/e36ff8d4 Exploring The Cloud and its context to business forms Chapter 2 of our story. Show notes are at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Exploring The Cloud and its context to business forms Chapter 2 of our story. Show notes are at https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 28 Oct 2020 02:00:00 -0400 Christina Mcdonald Moore Christina Mcdonald Moore 1016 The internet has a birthday (1966). Web browsers and websites do too (20 DEC 1990). The Cloud does not have a birthday. Poor cloud. Why? Because we don’t understand what it is, The Cloud Definition one: The Cloud is some remote place that stores data such as pictures, movies, words, numbers, and files. Definition two: The Cloud is at the mathematical center of the internet. Think about it: If everyone stored and retrieve data from The Cloud with equal ease and equal speed, then The Cloud would be at the center of the Internet. Come explore The Cloud. The internet has a birthday (1966). Web browsers and websites do too (20 DEC 1990). The Cloud does not have a birthday. Poor cloud. Why? Because we don’t understand what it is, The Cloud Definition one: The Cloud is some remote place that stores data such Cloud computing, cloud storage, The Cloud, AWS, Amazon, Tim Berners-Lee, Oracle, Oracle APEX No Chapter 1 | An Introduction 1 1 1 1 Chapter 1 | An Introduction full d952b334-384a-4f1e-a724-1f72bcdfdac4 https://share.transistor.fm/s/65bd6e86 Full show notes at: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Full show notes at: https://ChristinaMoore.us/the-soul-of-an-internet-machine/

]]> Wed, 21 Oct 2020 02:00:00 -0400 Christina Mcdonald Moore Christina Mcdonald Moore 1102 Meet the team, the project, and chuckle at the business mis-adventures here in the introduction to The Soul of an Internet Machine. Meet the team, the project, and chuckle at the business mis-adventures here in the introduction to The Soul of an Internet Machine. entrepreneur, pivot, oracle, apex No Trailer 1 1 Trailer trailer e468eff0-71d9-4529-a7fa-b7e4844531c0 https://share.transistor.fm/s/7de922c9
My name is Christina Moore. I am a tool-smith. For over thirty years, I design and build the tools of the modern economy. My craft and the practice of it evolved from an older time with people working over flames, and forges, and whacking things with hammers. 

I design, build, host, and support software. Software is the most ubiquitous tool of our economy and likely the least visible. You may be listening to my podcast on a computer weighing 200 grams – your mobile phone. In the recent six decades, tool smiths like me have put software into the tiniest of items. We have moved software from floppy disks to phone then into The Cloud.

In this podcast, I will explore The Cloud as an evolutionary grow stage of how we manage information and data. By we, I do mean all of us, not just the geekier amongst us. I will explore The Cloud and how it interacted with the design, development, and launch of a new business venture. Two stories for the price of one.

Who is my audience? Let’s start with the curious; curious about technology; curious about history; curious about business processes and entrepreneurship; curious about invention and product development; curious about science. 

My stories involve people pushing the margins of technology and exploring. We explore and fail. We explore and change directions.

From the first days of this project, I journaled my experiences as a business owner and technologist. I observed a subtle and massive (is that possible) shift in the architecture of software. 

In 1982, Tracy Kidder published a book called “The Soul of a New Machine”. He precisely captured the transition between the traditional big-iron landscape of the computing industry as we adopted smaller desktop units. During 2019 and 2020, I recognized that software and hardware had again made a similar step forward. In homage to Mister Kidder’s insights and timing that have named this work: “The Soul of an Internet Machine”

]]>
My name is Christina Moore. I am a tool-smith. For over thirty years, I design and build the tools of the modern economy. My craft and the practice of it evolved from an older time with people working over flames, and forges, and whacking things with hammers. 

I design, build, host, and support software. Software is the most ubiquitous tool of our economy and likely the least visible. You may be listening to my podcast on a computer weighing 200 grams – your mobile phone. In the recent six decades, tool smiths like me have put software into the tiniest of items. We have moved software from floppy disks to phone then into The Cloud.

In this podcast, I will explore The Cloud as an evolutionary grow stage of how we manage information and data. By we, I do mean all of us, not just the geekier amongst us. I will explore The Cloud and how it interacted with the design, development, and launch of a new business venture. Two stories for the price of one.

Who is my audience? Let’s start with the curious; curious about technology; curious about history; curious about business processes and entrepreneurship; curious about invention and product development; curious about science. 

My stories involve people pushing the margins of technology and exploring. We explore and fail. We explore and change directions.

From the first days of this project, I journaled my experiences as a business owner and technologist. I observed a subtle and massive (is that possible) shift in the architecture of software. 

In 1982, Tracy Kidder published a book called “The Soul of a New Machine”. He precisely captured the transition between the traditional big-iron landscape of the computing industry as we adopted smaller desktop units. During 2019 and 2020, I recognized that software and hardware had again made a similar step forward. In homage to Mister Kidder’s insights and timing that have named this work: “The Soul of an Internet Machine”

]]> Wed, 14 Oct 2020 13:42:18 -0400 Christina Mcdonald Moore Christina Mcdonald Moore 179 Exploring the intersection business and technology and the internet - this show is for people curious about software, entrepreneurship, invention, product development, and science. Exploring the intersection business and technology and the internet - this show is for people curious about software, entrepreneurship, invention, product development, and science. technology, oracle, apex, business, entrepreneur, tracy kidder, soul of a new machine, No