xpepper

#!/bin/bash

# Default action is 'start'
ACTION="${1:-start}"
POST_START_COMMAND="$2"

if [ "$ACTION" == "start" ]; then
    # Check if Rancher Desktop is already running
    if docker ps &> /dev/null; then
        echo "Rancher Desktop is already running."

xpepper

#!/bin/bash

OPENAI_API_KEY="${OPENAI_API_KEY}"
HOST="https://api.openai.com"
MODEL="gpt-3.5-turbo"

# Check if the API key is set
if [ -z "$OPENAI_API_KEY" ]; then
    echo "OpenAI API key is not set. Please set the OPENAI_API_KEY environment variable."
    exit 1

xpepper

If you want to invest your next learning session with a code kata (TL;DR: you should), here's an opinionated list of kata catalogs:

• https://www.codurance.com/katas, code katas on different topics and with different difficulty
• https://github.com/emilybache/Racing-Car-Katas, to test your knowledge of the SOLID principles with on-hands practice
• https://matteo.vaccari.name/blog/archives/293 is also a code kata that challenge your ability to follow the OCP principle
• https://github.com/gamontal/awesome-katas, a more generic, community-driven list of katas
• https://nealford.com/katas/ and https://fundamentalsofsoftwarearchitecture.com/katas/list.html, because who said that katas are just about improving coding skills? Architectural katas are a good way to practice architectural skills!

Remember, when tackling a kata, you should first have a clear idea of what you want to learn or what skills you want to sharpen (e.g., improving TDD skills, refactoring skills, code design skills, etc.). If you want to impr

xpepper

Certainly! I'll provide you with some code examples that illustrate common mistakes related to ownership and borrowing in Rust. For each example, you can determine whether it would compile or not, and I'll explain why it should or should not compile based on Rust's rules.

Example 1: Multiple Ownership Attempt

fn main() {
    let s1 = String::from("hello");
    let s2 = s1;
    let s3 = s1;

xpepper

Sure, I'd be happy to help you practice recognizing ownership and borrowing violations in Rust! Here are some code examples for you to evaluate:

Example 1:

let mut s = String::from("hello");

let r1 = &s;
let r2 = &s;
println!("{}, {}", r1, r2);

xpepper

Here are some Rust code examples that involve ownership and borrowing. For each example, determine whether it will compile and explain why or why not based on Rust's ownership and borrowing rules.

Example 1

fn main() {
    let s1 = String::from("hello");
    let s2 = &s1;
    drop(s1);
    println!("s2 says: {}", s2);
}

xpepper

defaults write com.apple.dock appswitcher-all-displays -bool true && killall Dock

xpepper

import com.casavo.gluglu.core.infrastructure.http.installLoggingConfiguration
import com.casavo.gluglu.core.infrastructure.http.installUserAgentConfiguration
import io.ktor.client.HttpClient
import io.ktor.client.request.get
import io.ktor.client.request.url
import io.ktor.http.isSuccess
import kotlinx.coroutines.runBlocking

val client = HttpClient {
    expectSuccess = true

xpepper

markmap
colorFreezeLevel color maxWidth initialExpandLevel 2 #2980b9 300 1

The Ultimate Guide to Developer Counter-Productivity

xpepper

#!/usr/bin/env bash

export AWS_PAGER="" 

db_connections () {
     echo "## ${1}:"
     aws cloudwatch get-metric-statistics \
          --namespace AWS/RDS \
          --dimensions Name=DBInstanceIdentifier,Value=$1 \
          --metric-name DatabaseConnections \