This document outlines a 3-step process for decoding embedded code:
1. Identify the data generators - the parts of code that send data in a particular format. This allows writing an API to read the data.
2. Identify the data transformers - the business logic and algorithms that do most of the work. This is often where bugs occur.
3. Identify the data consumers - the parts of code that consume information. These act as containers to hold the data, allowing an API to send data out.
This document outlines a 3-step process for decoding embedded code:
1. Identify the data generators - the parts of code that send data in a particular format. This allows writing an API to read the data.
2. Identify the data transformers - the business logic and algorithms that do most of the work. This is often where bugs occur.
3. Identify the data consumers - the parts of code that consume information. These act as containers to hold the data, allowing an API to send data out.
This document outlines a 3-step process for decoding embedded code:
1. Identify the data generators - the parts of code that send data in a particular format. This allows writing an API to read the data.
2. Identify the data transformers - the business logic and algorithms that do most of the work. This is often where bugs occur.
3. Identify the data consumers - the parts of code that consume information. These act as containers to hold the data, allowing an API to send data out.
It is about programming in a structured way and read the
code in a structured fashion.
It is adhering to some terminology and understanding the
meaning of that terminology
It is all about following a process and getting great
results in terms of reading the code and comprehending the code.
Follow #balemarthyvamsi SWIPE >>
02 #1 - Identify Data Generators The first segment of code organization is to identify the data "generators". Under this group, the underlying data transfer mechanisms do not matter much. What matters more is the data, who is sending is and in what format is that data present.
Advantage : One can easily write an API
to read the data. #balemarthyvamsi SWIPE >> 03 #2- Identify Data Transformers This IS the logic of the code. Most commonly it is also called "Business logic", "algorithm", or "Middleware". It does all the second level of heavy lifting for the application. In some cases where the design is lightweight like a super loop structure, it does all the things that application offloads. Advantage : This is the PART that mostly changes and have bugs. #balemarthyvamsi SWIPE >> 04 #3- Identify Data Consumers This is similar to Data Generators. The operation is to consume the information from Data Transforming part of the code. Similar to generator, it does not need to worry much about the way the data is displayed or sent, the mechanisms. It needs to become the "container" to hold the data. Advantage : One can easily write API that sends the data out. #balemarthyvamsi SWIPE >> #balemarthyvamsi
I am open to help early
career embedded developers with their resume and career mentoring. DM me if you are interested
CODING FOR ABSOLUTE BEGINNERS: How to Keep Your Data Safe from Hackers by Mastering the Basic Functions of Python, Java, and C++ (2022 Guide for Newbies)
Knight's Microsoft Business Intelligence 24-Hour Trainer: Leveraging Microsoft SQL Server Integration, Analysis, and Reporting Services with Excel and SharePoint