Jim O'Flaherty chaotic3quilibrium

Given the two software engineering principles, A and B, below the "---"...

What kinds of contexts arise where they are in conflict with wach other?
Wouldn't they more accurately be call a bias or guideline, than a principle?

A. The Single Responsibility Principle (SRP) states that a class or module should have one, and only one, reason to change, meaning it should focus on a single task or actor. As the 'S' in SOLID, it separates concerns to ensure that changes in one business rule do not necessitate changes in others, making code easier to maintain, test, and understand. B. The DRY (Don't Repeat Yourself) principle is a software development guideline stating that "every piece of knowledge must have a single, unambiguous, authoritative representation within a system". It aims to reduce duplication of logic, data, and documentation, ensuring that changes are made in one place to improve maintainability and reduce bugs.

Effective Scala Case Class Patterns

Version: 2022.03.02

	import React, { useState, useMemo } from 'react';
	import {
	Activity,
	Server,
	Cloud,
	Settings,
	Info,
	BarChart3,
	CheckCircle2,
	Trophy,

	package org.public_domain.java.utils;

	import java.util.Iterator;
	import java.util.stream.Stream;
	import java.util.stream.StreamSupport;
	import org.jetbrains.annotations.NotNull;

	/**
	* File: org.public_domain.java.utils.StreamUtils.java
	* <p>

	package org.public_domain.java.utils;

	import java.util.*;
	import java.util.Map.Entry;
	import java.util.function.Function;
	import java.util.function.Supplier;

	/**
	* File: org.public_domain.java.utils.Memoizer.java
	* <p>

	package org.public_domain.java.utils;

	import java.util.NoSuchElementException;
	import java.util.Objects;
	import java.util.Optional;
	import java.util.function.Consumer;
	import java.util.function.Function;
	import java.util.function.Predicate;
	import java.util.function.Supplier;
	import org.jetbrains.annotations.NotNull;

	package org.public_domain

	import zio.console._
	import zio.{ExitCode, UIO, URIO, ZIO}

	import java.io.IOException

	object PurelyFunctionalHangman extends zio.App {
	def run(args: List[String]) : URIO[Console, ExitCode] =
	hangman.exitCode

	//StackOverflow Question: https://stackoverflow.com/q/77362860/501113

	//Updated/fixed the 5 code files to incorporate the answer by Turing85: https://stackoverflow.com/users/4216641/turing85

	import scalatags.JsDom.all._

	val textAreaInput =
	textarea.render

	val buttonExecuteTransform =
	button("Execute Transform").render

	val textAreaOutput =
	textarea.render

	//C1 - Initial Scala solution attempt

	val lettersToDigitsPrefixSize = 3

	val letterToDigits =
	List(
	'a' -> List(1, 3, 7, 9),
	'b' -> List(2, 4, 6, 8),
	'c' -> List(1, 3, 7, 9),
	'd' -> List(2, 4, 6, 8),

Jim O'Flaherty chaotic3quilibrium

Effective Scala Case Class Patterns

Available As