pablisco

Behaviour

One of the things we tend to do in OOP is to create types to define behaviours. However, types are best used to describe data, i.e. objects. We've had to use types in the past because of language limitations.

This is a small description of how we can use the power of functions to define code in a way that is easier to read, maintain and test.

Consumer Component

hrules6872

#!/usr/bin/env kscript

/*
 * Copyright (c) 2023. Héctor de Isidro - hrules6872
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0

hrules6872

/*
 * Copyright (c) 2023. Héctor de Isidro - hrules6872
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

hrules6872

/*
 * Copyright (c) 2023. Héctor de Isidro - hrules6872
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

hrules6872

Pull Requests became popular for two reasons:

• Asynchronous communication. Developers can review and respond at any time, allowing them to continue development without interruption and review PRs when they come to a natural pause in their flow.
• Quality Assurance. Reviewing and testing code before it hits the target branch ensures that the target branch stays clean.

How to Pull Request:

• Authoring
  • Keep them small: it's very tempting to rewrite, refactor, boy scout and reformat the code as you develop but in general, it's best not to do it all at once.
  • Perform a Self-Review: although it's very tempting to just dump your changes in a PR and let other people find the mistakes, create a draft PR and do a full review yourself. You can also use this “self-review” to point things out to your reviewers.
  • Create a meaningful title: keep the title short and meaningful and avoid titles generated from the b

hrules6872

"Pair programming is a conversation. You're always talking. You're always explaining. You're always trying to combine your knowledge." - Sarah Mei

• Pair programming is vital for collaborative teamwork and high quality software.
• What it's not.
  • It's not as simple as "two people working at a single computer".
  • If your pair programming involves arguing, jockeying for position/influence, or trying to prove something, it's not actually pairing.
  • If your pair programming involves one person typing while another person silently watches, it's not actually pairing.
  • If your pair programming is on a computer where one of you is the "owner" and one of you is the "guest," it's not actually pairing.
• How to pair?

hrules6872

@Composable
private fun Calendar(
  modifier: Modifier = Modifier,
  date: LocalDate
) {
  val firstDate = with(date) {
    val firstOfMonth = withDayOfMonth(1)
    val firstDayOfFirstWeek = firstOfMonth.dayOfWeek.value
    firstOfMonth.minusDays(firstDayOfFirstWeek.toLong())
  }

hrules6872

/*
 * Copyright (c) 2022. Héctor de Isidro - hrules6872
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software

hrules6872

fun Modifier.horizontalFadingEdge(
    scrollState: ScrollState,
    length: Dp,
    edgeColor: Color? = null,
) = composed(
    debugInspectorInfo {
        name = "length"
        value = length
    }
) {

hrules6872

fun <TYPE> List<TYPE>.padEndOrCompact(size: Int, fallback: TYPE): List<TYPE> {
  if (size < 0) throw IllegalArgumentException("Desired length $size is less than zero.")
  return (0 until size).map { this.getOrNull(it) ?: fallback }
}

fun <TYPE> List<TYPE>.padEnd(size: Int, fallback: TYPE): List<TYPE> {
  if (size < 0) throw IllegalArgumentException("Desired length $size is less than zero.")
  return when {
    size > this.size -> this.padEndOrCompact(size, fallback)
    else -> this