aneudy1702

npx skills add https://github.com/Leonxlnx/taste-skill --agent '*' --copy -y
--skill stitch-design-taste
--skill high-end-visual-design
--skill minimalist-ui
--skill redesign-existing-projects
--skill design-taste-frontend

npx skills add vercel-labs/agent-skills --agent '*' --copy -y
--skill vercel-composition-patterns
--skill deploy-to-vercel \

aneudy1702

📚 Staff Engineer Role Preparation – Resources & Topics

1. System Design

• Key Topics We Covered:
  • Building scalable services (monolith vs microservices)
  • Designing resilient systems (retry mechanisms, circuit breakers, backpressure)
  • Caching strategies (Redis, CDN usage)
  • Database design patterns (sharding, replication, indexing)
  • CAP Theorem, eventual consistency, strong consistency
• Queues and async processing (Kafka, RabbitMQ)

aneudy1702

Cancionero

IBCH: Lista de canciones y acordes.

Para los acordes: cada / representa un tiempo. D/// serie Re Mayor por 3 tiempos.

Fecha: 01/12/2024

1. Eres todo poderoso

aneudy1702

Hey Luis, I collected a few job listings for you to consider. I hope any of these work out for you.

Remote Jobs:

1. Customer Service Representative at Benchley Associates
   • Description: Serve as the primary contact for customers and partners through phone, email, and live chat support. Assist with order placement, delivery tracking, and app navigation.
   • Requirements: Previous experience in customer service or call centers; excellent communication skills.
   • Location: Remote
   • Application: Apply here

aneudy1702

Disclaimer: This write-up is the first part of a valuable two-part series. While it provides comprehensive resources and requirements to understand the impact of semantic HTML on accessibility, it does not include code solutions. Part 2, which is equally important, will delve into the coding aspect, offering detailed solutions. This version is tailored for workshop use, encouraging hands-on learning and problem-solving.

---

Don't <div /> Your <button />s

Here's the 🏃 TL:DR 🏃 version for the speed readers:

aneudy1702

Streamlining Software Releases: Combining GitHub Actions with Semantic-Release and Release-Please

TL;DR - Summary

Discover streamlined software release processes using GitHub Actions with 'semantic-release' and 'release-please.' This guide compares these tools for different project types, offering practical insights and resources for mastering automated releases.

---

aneudy1702

Automating your Release Process via GitHub Actions

Introduction

In the fast-paced world of software development, efficiency and automation are key. Automating your release process using GitHub Actions can significantly streamline your workflow. This article explores two powerful tools: semantic-release and release-please, focusing on their integration with GitHub Actions.

Semantic-Release as a GitHub Action

semantic-release automates the versioning and package publishing process based on Semantic Versioning principles. Integrated with GitHub Actions, it offers a seamless workflow for software release.

aneudy1702

When using both semantic-release and release-please as GitHub Actions, it's important to understand how each tool integrates with GitHub's workflow and automation features. Here's an exploration of how each tool functions within the GitHub Actions framework:

Semantic-Release as a GitHub Action

Integration with GitHub Actions:

• semantic-release can be set up as a GitHub Action to automate release processes within your GitHub repositories.
• The action will typically run on specific triggers, like a push to the main branch or a merged pull request.

aneudy1702

function maskNumbers(fullNumber, lastCharactersLen){
  const last4Digits = fullNumber.slice(-lastCharactersLen);
  const maskedNumber = last4Digits.padStart(fullNumber.length, '*');
  return last4Digits.padStart(fullNumber.length, '*');
  // Expected output: "************5581"
}

aneudy1702

import React, { useRef } from 'react';
import get from 'lodash.get';
import throttle from 'lodash.throttle';

const getTouchEndX = event => get(event, 'changedTouches[0].screenX') || 0;
const preventDefault = event => {
  event.preventDefault();
  event.returnValue = false;
  return false;
};