# factory function Published articles for factory function. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Defining and Validating Blockchain Transactions in an In-Memory Accounting Database DevFeed: [Defining and Validating Blockchain Transactions in an In-Memory Accounting Database]() Original publisher: [Read original article]() Published: 2023-01-24T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Transactions](), [data](), [Ethereum]() Tags: [bitcoin](), [blockchain](), [blockchain-transaction](), [code](), [data](), [ethereum](), [factory-function](), [function](), [go-blockchain](), [how-to](), [implementation](), [learn](), [reference](), [transactions](), [types](), [video]() ### AI overview This video explains how to define and validate transaction types for a blockchain's in-memory accounting database. It covers the transaction data type, field design, validation methods, nonce tokens, and a transaction factory function, with concepts borrowed from Ethereum for reference. ### Source excerpt Introduction In episode 17, Bill began to design an in-memory accounting database that will store the account balances on his blockchain. To build this database, Bill will add a memory pool on each node that stores a list of public addresses with their respective balances. The balances on these addresses are reconstructed by reading the previous transaction records found on his blockchain. In this video, Bill will define the types of transactions his blockchain will support. The first step Bill takes is to define the transaction data type and give a full walkthrough of the reasoning behind the fields he chose for this data type. Next, he'll define methods for this type that will validate a transaction. While writing this code, Bill will borrow a few concepts from Ethereum to build a reference implementation. Watch to learn how transactions are managed on the blockchain and how to define one on your blockchain. ## Ultimate Go: Advanced Engineering Episode 19 -- Defining a Blockchain Account Data Structure DevFeed: [Ultimate Go: Advanced Engineering Episode 19 -- Defining a Blockchain Account Data Structure]() Original publisher: [Read original article]() Published: 2023-01-24T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Blockchain](), [Data structures](), [Ethereum](), [Transactions]() Tags: [account](), [bitcoin](), [blockchain](), [data-structure](), [data-type](), [design](), [engineering](), [ethereum](), [factory-function](), [go](), [go-blockchain](), [how-to](), [learn](), [transactions](), [video]() ### AI overview This video explains how to define a user account type for a blockchain in Go. It covers the account data structure, the design rationale, and a factory function for initializing an account. ### Source excerpt Introduction In episode 18, Bill defined the Go type that will represent a transaction and implemented the methods to validate one. While developing the transaction type, Bill states that he'll be borrowing concepts from Ethereum to ensure that he's building a reference implementation. Bill's transaction type has a field named nonce, similar to Ethereum, that ensures transactions are executed in order. The nonce value of the last transaction is stored in his accounting database and later compared for additional verification. ## Composed modifiers in Jetpack Compose DevFeed: [Composed modifiers in Jetpack Compose]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2022-04-04T10:00:00Z Content type: tutorial Language: en Sources: [👨💻 Jorge Castillo]() Topics: [Jetpack Compose](), [ui](), [context](), [factory function](), [Library]() Tags: [android](), [compose](), [compose-ui](), [context](), [extension-function](), [factory-function](), [jetpack](), [jetpack-compose](), [modifiers](), [state](), [stateful](), [stateless]() ### AI overview This tutorial explains the difference between standard and composed modifiers in Jetpack Compose. Standard modifiers use extension functions and are stateless, while composed modifiers support state and access to composition context by creating them within a Composition. ### Source excerpt Learn about composed modifiers and compare those to standard ones. ## Kotlin Delegated Properties for Designing a Simple Android Library API DevFeed: [Kotlin Delegated Properties for Designing a Simple Android Library API]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-04-11T19:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [API](), [Kotlin](), [Library](), [implementation](), [Android](), [properties](), [factory function]() Tags: [android](), [api](), [api-design](), [delegates](), [factory-function](), [implementation](), [kotlin](), [library](), [properties]() ### AI overview This tutorial explains API design choices in the Krate Android SharedPreferences wrapper. It shows how Kotlin delegated properties can encapsulate reusable logic, persist values across application restarts, and hide concrete implementations behind a simple interface and factory function. ### Source excerpt When developing a library, designing an easy to use API while hiding unnecessary implementation details from clients is fundamental. Let's look at some API design choices we've made for our library Krate, an Android SharedPreferences wrapper. ## Avoid Interface Pollution DevFeed: [Avoid Interface Pollution]() Original publisher: [Read original article]() Published: 2016-10-21T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Code](), [interfaces]() Tags: [ardan-labs](), [blog](), [code](), [code-reviews](), [decoupling](), [factory-function](), [go](), [go-programming](), [golang](), [implementation](), [interface](), [programming]() ### AI overview The article explains interface pollution: declaring interfaces unnecessarily, especially when an interface duplicates a concrete type's entire API. It identifies warning signs and recommends using interfaces when callers need to provide implementations, multiple internal implementations exist, or decoupling from identified changes is necessary. ### Source excerpt Introduction Interfaces should only be used when their added value is clear. I see too many packages that declare interfaces unnecessarily, sometimes just for the sake of using interfaces. The use of interfaces when they are not necessary is called interface pollution. This is a practice I would like to see questioned and identified more in code reviews. Code Example Let's look at a code example that contains questionable design choices that raise flags for interface pollution.