Leanpub Header

Skip to main content
Go to Leanpub.com
Leanpub Clips — big ideas, small videos

Leanpub Clips

Short clips from Leanpub's videos.

About

These are short clips from our Leanpub videos — our Launch videos, Podcast videos, and more from our YouTube channel.

Subscribe on YouTube
Launch

Why She Named It 'Triple A' & Why Linux Means True Freedom

Assembly Arithmetic Algorithms-Linux by Chastity White Rose

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Watch on YouTubeView book
Launch

Why RPN Calculators Perfectly Explain Assembly Language Control

Assembly Arithmetic Algorithms-Linux by Chastity White Rose

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Watch on YouTubeView book
Launch

HP's RPN Calculators: No Parentheses, No Order-of-Operations Rules!

Assembly Arithmetic Algorithms-Linux by Chastity White Rose

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Watch on YouTubeView book
Launch

Standing in Rain at a Phone Booth Just to Activate Windows 😤

Assembly Arithmetic Algorithms-Linux by Chastity White Rose

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Watch on YouTubeView book
Launch

Why Linux Is the Best Programming Environment for Any Language

Assembly Arithmetic Algorithms-Linux by Chastity White Rose

Personally, I think that the Assembly system of conditional jumps makes a lot of sense. Other programming languages such as BASIC and C have "goto" statements that work like this. For example, `if(eax<ebx){goto less;}`. Modern programming languages tend to discourage the use of goto or not allow it at all. However, these languages still use jumps I have described in this section because it is required by the hardware. Both "if" and "while" statements are written by using the conditional jump statements most relevant to what you are trying to do. The only thing I have found difficult about jumps in assembly is remembering which acronym means which condition. However, since I created the chart in this chapter, now I can refer to it, and you can too! As long as I keep these six main types of conditions in my head and am working with unsigned numbers, I can write almost any assembly program from scratch.

Watch on YouTubeView book
Launch

Why Software Engineering Is Still Art, Not Engineering

Process-First Design by Sergiy Yevtushenko

Software design is the last craft that never got standardized, so the same problem yields a different structure in every shop and every sprint. Process-First Design is the method for it: design around the process, not the entity, and the dozen small structural decisions you re-litigate every time become engineering, leaving your judgment for the architecture and the domain. One running example carries it from a single use case up to a multi-tenant platform.

Watch on YouTubeView book
Launch

Stop Thinking in Entities — Processes Are the Real Source of Truth

Process-First Design by Sergiy Yevtushenko

Software design is the last craft that never got standardized, so the same problem yields a different structure in every shop and every sprint. Process-First Design is the method for it: design around the process, not the entity, and the dozen small structural decisions you re-litigate every time become engineering, leaving your judgment for the architecture and the domain. One running example carries it from a single use case up to a multi-tenant platform.

Watch on YouTubeView book
Launch

Stop Diving In Blind — Think About What You're Actually Building

Process-First Design by Sergiy Yevtushenko

Software design is the last craft that never got standardized, so the same problem yields a different structure in every shop and every sprint. Process-First Design is the method for it: design around the process, not the entity, and the dozen small structural decisions you re-litigate every time become engineering, leaving your judgment for the architecture and the domain. One running example carries it from a single use case up to a multi-tenant platform.

Watch on YouTubeView book
Launch

Why He Designed His Book to Be Read in One Sitting

Process-First Design by Sergiy Yevtushenko

Software design is the last craft that never got standardized, so the same problem yields a different structure in every shop and every sprint. Process-First Design is the method for it: design around the process, not the entity, and the dozen small structural decisions you re-litigate every time become engineering, leaving your judgment for the architecture and the domain. One running example carries it from a single use case up to a multi-tenant platform.

Watch on YouTubeView book
Launch

Exposing What's Already Happening in Design (Nobody Notices)

Process-First Design by Sergiy Yevtushenko

Software design is the last craft that never got standardized, so the same problem yields a different structure in every shop and every sprint. Process-First Design is the method for it: design around the process, not the entity, and the dozen small structural decisions you re-litigate every time become engineering, leaving your judgment for the architecture and the domain. One running example carries it from a single use case up to a multi-tenant platform.

Watch on YouTubeView book
1234