# properties C# properties are members implemented with accessors that read, write, or compute data-field values. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Implicit Assertions Are More Readable DevFeed: [Implicit Assertions Are More Readable]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2026-09-01T04:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [test](), [API](), [properties]() Tags: [api](), [cypress](), [how-to](), [products](), [properties](), [test]() ### AI overview A tutorial on making Cypress API tests more readable by using descriptive assertions, precise value ranges, implicit assertions, and cy-spok for validating nested response objects. ### Source excerpt Recently I saw a Linkedin post that shows "b ## Enterprise Architecture Quietly Depended on Humans in Far More Places Than We Realised DevFeed: [Enterprise Architecture Quietly Depended on Humans in Far More Places Than We Realised]() Original publisher: [Read original article]() Author: flashdba Published: 2026-06-08T14:19:07Z Content type: opinion Language: en Sources: [flashdba]() Topics: [Enterprise Architecture](), [Architecture & Design](), [Artificial Intelligence](), [Actor](), [properties]() Tags: [actor](), [agentic](), [agentic-ai](), [ai](), [architecture](), [cloud](), [databases](), [databases-and-agentic-ai](), [enterprise-architecture](), [inferencing](), [performance](), [properties]() ### AI overview This article argues that enterprise architecture depended on implicit properties supplied by human participants, including predictable workload, intent, accountability, feedback, and limited capacity. It concludes that agentic AI exposes pressure across multiple technical and organisational domains by removing those assumptions simultaneously. ### Source excerpt Enterprise architecture was built around a human actor whose presence provided properties nobody designed and nobody priced. Agentic AI is the first technology to remove those properties simultaneously - and the absence is now visible across every domain. ## Beyond Positions: Kotlin's New Name-Based Destructuring DevFeed: [Beyond Positions: Kotlin's New Name-Based Destructuring]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-03-18T01:24:50Z Content type: tutorial Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Kotlin](), [Compiler](), [properties]() Tags: [android](), [android-app-development](), [androiddev](), [compiler](), [data-class](), [kotlin](), [kotlin-2](), [kotlin-native](), [properties]() ### AI overview This tutorial explains Kotlin 2.3.20's experimental name-based destructuring declarations, which match variables to properties instead of relying on componentN() position. It also covers the compiler option and supported modes. ### Source excerpt Image generated using Perplexity Name-based destructuring declarations were introduced in Kotlin 2.3.20 and match variables to properties rather than relying on position-based componentN(). Previously, destructive declarations used position-based destruction: data class User(var firstName: String, var lastName: String) val user = User("Alice", "Husseini") // componentN() val(firstName,lastName) = user println(firstName) println(lastName)Drawback of the componentN() based approach Destructuring relies on the order of componentN() functions, lastName receives the value of firstName, and firstName receives the value of lastName 👇 data class User(var firstName: String, var lastName: String) val user = User("Alice", "Husseini") // componentN() val(lastName,firstName) = user println(firstName) -> Husseini println(lastName) -> AliceName-based destructuring ✨ It's an Experimental feature. We can control how the compiler interprets destructuring declarations with the -Xname-based-destructuring compiler option. kotlin { // .. compilerOptions { freeCompilerArgs.add("-Xname-based-destructuring=only-syntax") } }Each variable refers to a property by name.val user = User("Alice", "Husseini") // Name-based destructuring (val firstName = firstName, val lastName = lastName) = userModeshttps://kotlinlang.org/docs/whatsnew2320.html#languageMode -- Name-Mismatch⚠ Warning ⚠Name-Mismatch warningMode -- Complete Position-based destructuring using square brackets []: data class User(var firstName: String, var lastName: String) val user = User("Alice", "Husseini") // componentN() val [firstName,lastName] = userReferences What's new in Kotlin 2.3.20 | Kotlin Stay in touch https://www.linkedin.com/in/navczydev/ JavaScript is not available. navczydev - Overview navczydev.bsky.social Beyond Positions: Kotlin's New Name-Based Destructuring was originally published in ProAndroidDev on Medium, where people are continuing the conversation by highlighting and responding to this story. ## IPTC export changed in Photos for macOS 26 Tahoe DevFeed: [IPTC export changed in Photos for macOS 26 Tahoe]() Original publisher: [Read original article]() Author: Rob Published: 2025-11-11T11:00:00Z Content type: article Language: en Sources: [Rob Allen]() Topics: [macOS](), [data](), [properties]() Tags: [data](), [exiftool](), [export](), [mac](), [macos](), [photography](), [rodeo-flickr-uploader]() ### AI overview Photos for macOS 26 Tahoe changed JPEG IPTC export behavior: Object Name, Caption-Abstract, and Keywords properties are no longer populated as they were in macOS 15 Sequoia. The export still provides the data through Title, Description, and Subject, and Rodeo version 0.5 was updated to resolve the issue. ### Source excerpt I've recently upgraded my MacBook Air to macOS 26 Tahoe and one thing I noticed was that Rodeo's rules were no longer working. With the help of exiftool, I worked out that when exporting to JPEG from Photos for macOS 26 Tahoe, the Object Name, Caption-Abstract and Keywords IPRC properties were no longer being populated. This is a regression from macOS 15 Sequoia. This is the data from exiftool. Output from macOS 15 Sequoia: $... continue reading. ## Designing a hierarchical Authorisation system DevFeed: [Designing a hierarchical Authorisation system]() Original publisher: [Read original article]() Author: Authorisation Published: 2025-09-20T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Actor](), [object](), [structure](), [service](), [properties]() Tags: [actor](), [apis](), [billing](), [finance](), [object](), [recursion](), [service](), [structure]() ### AI overview This article explains how to design a hierarchical authorization system for Goiter. It contrasts a flat mapping of users, objects, and actions with a hierarchical model in which groups can have multiple parents and inherit rules. The article notes that recursive parent lookup can reduce rule bloat, while assuming a maximum recursion depth of 10. ### Source excerpt . [Designing a Hierarchical Authorisation System](designing-a-hierarchical-authorisation-system-cover... ## Gradle Footguns: Don't add potentially-empty providers to collection properties DevFeed: [Gradle Footguns: Don't add potentially-empty providers to collection properties]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2024-09-11T17:33:13Z Content type: tutorial Language: en Sources: [Zac Sweers]() Topics: [Gradle](), [bug](), [properties]() Tags: [bug](), [gradle](), [properties]() ### AI overview The article explains a Gradle bug involving potentially empty providers added to collection properties. An absent provider can clear the property value rather than only its elements, causing exceptions or leaving the property unusable. ### Source excerpt After pairing with Tony Robalik on a recent weird behavior I was seeing in Gradle, we encountered a deliciously evil bug in Gradle. It's documented a little in Gradle 8.7's release notes (see Better API for updating collection properties), but the basic premise is ## Gradle Properties - Tadeas Kriz DevFeed: [Gradle Properties - Tadeas Kriz]() Original publisher: [Read original article]() Published: 2024-06-17T19:34:40Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Gradle](), [properties](), [configuration](), [debugging]() Tags: [configuration](), [debugging](), [gradle](), [priority](), [properties]() ### AI overview This post explains where Gradle properties come from, how different property types are passed into and used by build scripts, and how their priorities affect configuration. It highlights behaviors that may differ from Gradle documentation, including system properties loaded from multiple locations and project properties created from system properties. ### Source excerpt Understanding how Gradle properties work can save you a lot of time debugging. This post explains how to set properties and what their priorities are. ## Item 29: Minimize elements' visibility DevFeed: [Item 29: Minimize elements' visibility]() Original publisher: [Read original article]() Published: 2024-05-06T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [interface](), [Kotlin](), [class](), [properties](), [maintenance]() Tags: [class](), [how-to](), [interface](), [kotlin](), [maintenance](), [properties](), [workshop-learning-programming]() ### AI overview The article explains why APIs should minimize visible elements: smaller interfaces are easier to learn, maintain, test, and change. It also shows how restricting visibility in Kotlin helps protect class invariants by encapsulating internal state, including making property setters private. ### Source excerpt Why we should minimize elements' visibility and how to do it. ## Computed Properties for Haskell Records DevFeed: [Computed Properties for Haskell Records]() Original publisher: [Read original article]() Published: 2023-11-30T00:00:00Z Content type: article Language: en Sources: [Romes' Musings]() Topics: [Haskell](), [properties](), [data type](), [Swift](), [C]() Tags: [c](), [data-type](), [extension](), [haskell](), [properties](), [rust](), [swift]() ### AI overview This article explains Haskell record types and related syntax extensions, including OverloadedRecordDot and NamedFieldPuns. It then introduces computed properties by comparing Haskell records with properties in Swift, C#, and Java. ### Source excerpt Contents 1 Records in Haskell 1.1 Overloaded Record Dot 1.2 Named Field Puns 2 Computed Properties 3 Conclusion 1 Records in Haskell Haskell has so-called record types, which are also commonly known as structs, for instance, in C, Swift, and Rust. To define a square, one would write: data Point = Point { x :: Int , y :: Int } data Square = Square { topLeft :: Point , bottomRight :: Point } mySquare = Square{ topLeft = Point{x = 0, y = 0} , bottomRight = Point{x = 2, y = 2} } mySquareWidth = x (bottomRight mySquare) - x (topLeft mySquare) In Haskell record types are just syntactic sugar for ordinary product types paired with functions that get and set these fields. In essence, the above is not fundamentally different from having the following standard product types and functions: data Point = Point Int Int data Square = Square Point Point x, y :: Point -> Int x (Point px _) = px y (Point _ py) = py topLeft, bottomRight :: Square -> Point topLeft (Square tl _) = tl bottomRight (Square _ br) = br -- And setters... 1.1 Overloaded Record Dot However, by turning on the OverloadedRecordDot syntax extension, you can use more syntactic sugar to project the fields of a record instead of using the field name as a standard function: {-# LANGUAGE OverloadedRecordDot #-} mySquareWidth = mySquare.bottomRight.x - mySquare.topLeft.x which is neat! I like OverloadedRecordDot. It looks clean and feels more like using proper property of the record data type. It is also less ambiguous for an LSP to suggest the record properties of a data type by typing after the ., than it is to suggest functions to apply to the record type argument. 1.2 Named Field Puns Since I'm already writing about records, I'll mention another extension I quite enjoy: NamedFieldPuns. Traditionally, when matching on a record, you can list the field names and bind variables to the value associated with that field. Continuing the above example: area :: Square -> Int area Square{topLeft = tl, bottomRight = br} = (br.x ## Kotlin Reflection: Method and property references DevFeed: [Kotlin Reflection: Method and property references]() Original publisher: [Read original article]() Published: 2023-10-16T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Programming](), [classes](), [function](), [properties]() Tags: [classes](), [dependency-injection](), [functions](), [gson](), [interfaces](), [java](), [koin](), [kotlin](), [property](), [workshop-learning-programming]() ### AI overview This tutorial introduces Kotlin reflection, explaining how programs inspect classes, functions, properties, annotations, constructors, and other source-code elements at runtime. It also describes uses in Gson serialization, Koin dependency injection, and the hierarchy of Kotlin reflection reference types. ### Source excerpt The general hierarchy of Kotlin reference classes, and details about method and property references. ## More Accessible Graphs with Jetpack Compose Part 3: Differentiating without Color DevFeed: [More Accessible Graphs with Jetpack Compose Part 3: Differentiating without Color]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-06-11T04:27:29.325000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Graphs](), [Jetpack Compose](), [color](), [Code](), [function](), [properties]() Tags: [accessible](), [code](), [color](), [function](), [graphs](), [jetpack-compose](), [patterns](), [properties]() ### AI overview The third article in a series on accessible graphs with Jetpack Compose explains why data should not be differentiated by color alone. It demonstrates using different point shapes and line patterns to improve distinguishability for people with color-vision differences and across screens with varying color reproduction. ### Source excerpt This blog post is the third one in my series on more accessible graphs with Jetpack Compose. You can find the previous two from the following links: More Accessible Graphs with Jetpack Compose Part 1: Adding Content Description More Accessible Graphs with Jetpack Compose Part 2: Adding Keyboard Interaction The third topic we will cover is differentiating data by other means than color. Color is a convenient way to distinguish data, but what if you can't see color? Or what if you see colors differently? For example, the example project we've been developing during the blog post series would look like this for someone who can't see color at all: And someone with red-green color blindness: Another aspect of why not use color alone is that phone screens display color differently. A noticeable difference on a high-end external screen for a designer might be almost the same shades for a lower-end phone, making usage impossible. There are better ideas than just using color to differentiate data. In the next section, let's explore some of these other ways. Options for Color When talking about graphs, there are generally two ways to improve the distinguishability of data: Shapes and patterns. For example, if a bar chart is initially differentiated by color, adding patterns for different colors could differentiate those bars. For a line chart, both these options are valid. Let's explore both and differentiate the data by adding different shapes for points and some patterns for the line. This solution is not the most beautiful because I'm mixing these two options, but it's there to demonstrate, not to be a final design. The Code In the situation we're starting with, the function we're using to draw the data points looks like this: drawPoints( points = pixelPoints.map { Offset(it.x + 20f, it.y) }, pointMode = PointMode.Points, color = color, strokeWidth = 8.dp.toPx(), cap = StrokeCap.Round, ) It takes the points and point mode from the parameters, and other than that, everythin ## Kotlin and Java interoperability: Properties and annotations DevFeed: [Kotlin and Java interoperability: Properties and annotations]() Original publisher: [Read original article]() Published: 2023-08-07T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [interoperability](), [Java](), [properties]() Tags: [annotation](), [interoperability](), [java](), [jvm](), [kotlin](), [properties](), [workshop-learning-programming]() ### AI overview This tutorial explains how Kotlin properties map to Java getters, setters, fields, delegates, and constructor parameters. It shows how use-site annotation targets select specific generated JVM elements and discusses Kotlin object declarations, companion objects, and compiler-generated static methods for Java interoperability. ### Source excerpt Kotlin property is Java getter, setter, field and possibly more. So what to do, when you need to annotate or use a specific JVM element? ## Map as a property delegate DevFeed: [Map as a property delegate]() Original publisher: [Read original article]() Published: 2023-05-08T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [properties](), [interface](), [object]() Tags: [function](), [interface](), [kotlin](), [maps](), [property](), [standard-library](), [state](), [variables](), [workshop-learning-programming]() ### AI overview A Kotlin tutorial explains how Map can act as a read-only property delegate, including use cases for objects with known and dynamically added properties. It also explains variable assignment and shared mutable-object behavior through a community puzzle. ### Source excerpt How do we use Map as a property delegate, and why the result of a famous puzzler should not be surprising. ## Observable and Vetoable delegates DevFeed: [Observable and Vetoable delegates]() Original publisher: [Read original article]() Published: 2023-05-02T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [properties](), [function]() Tags: [kotlin](), [logs](), [properties](), [workshop-learning-programming]() ### AI overview A tutorial on Kotlin observable and vetoable delegates, explaining how property changes can trigger actions, update views, log changes, and influence application state. ### Source excerpt What are observable and vetoable delegates, and what are their real-life use cases. ## Lazy property delegate DevFeed: [Lazy property delegate]() Original publisher: [Read original article]() Published: 2023-03-27T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Optimization](), [performance-optimization](), [properties]() Tags: [kotlin](), [lazy](), [performance](), [property](), [regex](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin's lazy property delegate, which postpones read-only value initialization until first use. It presents use cases involving expensive object construction, application startup, testing, regular-expression compilation, and computed properties. ### Source excerpt What is lazy delegate, and what are its real-life use cases. ## Property delegation DevFeed: [Property delegation]() Original publisher: [Read original article]() Published: 2023-03-20T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [properties](), [Programming](), [Refactoring]() Tags: [behavior](), [function](), [implement](), [kotlin](), [patterns](), [property](), [property-delegation](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin property delegation, a feature for extracting reusable property patterns such as lazy, observable, binding, and dependency-injection behaviors. It describes how delegated getters and setters work and how to implement custom property delegates. ### Source excerpt What is property delegation, how does it work, and how can we implement our custom property delegate. ## The Houdini Properties and Values API is coming to CSS in Chromium 85 DevFeed: [The Houdini Properties and Values API is coming to CSS in Chromium 85]() Original publisher: [Read original article]() Published: 2020-07-21T00:00:00Z Content type: release Language: en Sources: [Una Kravets]() Topics: [CSS](), [API](), [Chromium](), [properties]() Tags: [api](), [chromium](), [css](), [properties](), [property](), [variables]() ### AI overview The article covers the arrival of the Houdini Properties and Values API in CSS with Chromium 85. ### Source excerpt The Houdini Properties and Values API is coming to your CSS file in Chromium 85. ## 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. ## Dynamic beans in spring DevFeed: [Dynamic beans in spring]() Original publisher: [Read original article]() Published: 2017-05-31T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Code](), [configuration](), [properties](), [import]() Tags: [code](), [configuration](), [create](), [dependency](), [implement](), [properties](), [property](), [spring]() ### AI overview A tutorial on programmatically creating Spring beans with BeanFactoryPostProcessor and BeanDefinitionRegistry. It covers defining individual and multiple beans, using constructor or factory-method initialization, and generating bean definitions from property-based options. ### Source excerpt Some time ago I've been trying to dynamically create spring beans. After fast stackoverflow check I decided to drop it and go with something else. Lately I've been trying to implement more complicated bean registration mechanism in which skipping dynamic bean creation wasn't an option. Here's how you can create spring beans "from code". Read more ## Converting Plaid to Kotlin: Lessons learned (Part 1) DevFeed: [Converting Plaid to Kotlin: Lessons learned (Part 1)]() Original publisher: [Read original article]() Published: 2015-11-03T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Android](), [android-apps](), [Code](), [properties](), [context]() Tags: [android](), [code](), [kotlin](), [properties](), [property](), [property-delegation]() ### AI overview This tutorial compares part of the Plaid Android app after rewriting HomeActivity in Kotlin. It discusses reduced boilerplate and Kotlin approaches to view binding, resource binding, property declarations, context-dependent initialization, and property delegation. ### Source excerpt Everything Android, Kotlin and other random topics ## Using the Constretto Configuration Factory DevFeed: [Using the Constretto Configuration Factory]() Original publisher: [Read original article]() Author: mick Published: 2011-01-19T18:07:02Z Content type: tutorial Language: en Sources: [Finn.no]() Topics: [configuration](), [Library](), [Development](), [Code](), [properties](), [import]() Tags: [code](), [configuration](), [development](), [file](), [import](), [library](), [properties](), [startup]() ### AI overview This article describes a factory created at FINN.no to reduce verbose Constretto configuration code. The factory provides concise access to individual configuration files and caches ConstrettoConfigurations, which the source says improves application startup performance. ### Source excerpt Development at FINN.no was quick to jump on the Constretto library. It's a great addition to any application making it easy to handle different environments and profiles with just the one build. When using Constretto at FINN.no one problem we found with the API is that it creates very verbose client code when the same ini or properties file is accessed throughout various class files. For example a repetition of the following happens public static final String CONSTANT_A = new ConstrettoBuilder() .createIniFileConfigurationStore() .addResource(new DefaultResourceLoader().getResource("classpath:file.ini")) .done() .getConfiguration() .evaluateToString("CONSTANT_A"); public static final String CONSTANT_B = new ConstrettoBuilder() .createIniFileConfigurationStore() .addResource(new DefaultResourceLoader().getResource("classpath:file.ini")) .done() .getConfiguration() .evaluateToString("CONSTANT_B"); One way around this is to use spring injection. This makes nice concise code but comes with two flaws: the constants can no longer be constant (they have to be member fields), and you have to lump all your properties together into one big "globals" store (days of f77 comes to mind). A third problem with this approach is that you're passing Constretto's context through Spring's context, we don't really want chained contexts but direct access to individual contexts if possible. So looking for a more elegant solution to all this we wrote a simple factory, that has now been accepted upsteam, that provides the necessary convenience methods so the constants can be declared short, sweet, and simple import static org.constretto.util.StaticlyCachedConfiguration.config; public static final String CONSTANT_A = config("classpath:file.ini").evaluateToString("CONSTANT_A"); public static final String CONSTANT_B = config("classpath:file.ini").evaluateToString("CONSTANT_B"); This also caches the ConstrettoConfigurations improving your application's startup performance. This was taken from Co ## The Universal Design Pattern DevFeed: [The Universal Design Pattern]() Original publisher: [Read original article]() Author: Steve Yegge (noreply@blogger.com) Published: 2008-10-20T10:06:00Z Content type: article Language: en Sources: [Steve Yegge]() Topics: [properties](), [Refactoring](), [Persistence](), [Programming](), [Programming language](), [class](), [object](), [XML](), [JavaScript](), [Lisp]() Tags: [article](), [javascript](), [lisp](), [persistence](), [properties](), [refactoring](), [technical](), [technical-article](), [xml]() ### AI overview This technical article presents the Properties Pattern, also known in its fullest form as the Prototype Pattern. It explains the pattern as a flexible approach to modeling problems across programming languages and as a general-purpose persistence strategy, while comparing it with class-based object-oriented, relational, and XML modeling. ### Source excerpt This idea that there is generality in the specific is of far-reaching importance. -- Douglas Hofstadter, Gödel, Escher, Bach Note: Today's entry is a technical article: it isn't funny. At least not intentionally. Update, Oct 20th 2008: I've added an Updates section, where I'll try to track significant responses, at least for a week or so. There are three entries so far. Contents Introduction Three Great Schools of Software Modeling Class Modeling Relational Modeling XML Modeling Other schools Finding the sweet spot Property Modeling Brains and Thoughts Who uses the Properties Pattern? Eclipse JavaScript Pushing it even further The pattern takes shape... Wyvern Lisp XML revisited Bigtable Properties Pattern high-level overview Representations Keys Quoting Missing keys Data structures Inheritance The deletion problem Read/write asymmetry Read-only plists Performance Interning strings Perfect hashing Copy-on-read caching Refactoring to fields Refrigerator REDACTED Rolling your own Transient properties The deletion problem (remix) Persistence Query strategies Backfills Type systems Toolkits Problems Further reading New Updates Final thoughts Introduction Today I thought I'd talk about a neat design pattern that doesn't seem to get much love: the Properties Pattern. In its fullest form it's also sometimes called the Prototype Pattern. People use this pattern all over the place, and I'll give you a nice set of real-life examples in a little bit. It's a design pattern that's useful in every programming language, and as we'll see shortly, it's also pretty darn useful as a general-purpose persistence strategy. But even though this pattern is near-universal, people don't talk about it very often. I think this is because while it's remarkably flexible and adaptable, the Properties Pattern has a reputation for not being "real" design or "real" modeling. In fact it's often viewed as a something of a shameful cheat, particularly by overly-zealous proponents of object-oriented desi