khalidx

Tickets

Tip

If you only take away one thing from this document, it should be this:

Write a "press release" before you start any work.

The only thing that should be a ticket is something that is worthy of a press release. Otherwise, it's likely just a subtask of a larger ticket, and should be tracked as such.

This makes it clear to all participants the "story" of what we are trying to accomplish, and the benefits unlocked for our customers. It also makes it easier to understand and to prioritize our work, and to understand platform "features" we've shipped.

khalidx

TLDR: This post highlights the importance of securing dependencies in the software supply chain.

What protects an organization from this behavior:

1. A developer joins the organization as employee number 523,001
2. The developer writes code for the organization on some work project
3. The developer makes their own OSS package, outside of organization work, and publishes it to npm (or another registry)
4. The developer installs their own npm package, to use on the organization's work project
5. The package goes on to live undedected for years at the organization

khalidx

If you're using SSH with VSCode to develop on a remote server, this config will help you keep your terminal sessions around even if you are disconnected from the server.

This means you can log off and enjoy a coffee, and as long as your server is still up and running, you can connect back at any time and jump back into your terminal as you left it.

Start a session

tmux

khalidx

Read/View-Only User for AWS Account Analysis

An AWS CloudFormation Template for creating a read/view-only IAM user with programmatic (CLI) access.

Tip

This is useful for conducting a more complete analysis and inventorying of an AWS account.

The AWS IAM Role created in this CloudFormation Stack is similar to the following:

• The AWS [ReadOnlyAccess] Managed Policy

khalidx

Tip

In a Codespace, we have access to the CODESPACE_NAME and the GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN environment variables.

We can use these variables to build the corresponding URL that will be used when forwarding a port in GitHub Codespaces.

Here's how we can build the URL for the forwarded port 80:

khalidx

FROM ubuntu:noble

# Install necessary packages
RUN apt update
RUN apt install -y <package-name>
RUN rm -rf /var/lib/apt/lists/*

khalidx

This is a general guideline for your first meeting with a potential co-founder.

Just replace any {variable} with information about you, your guest, or your startup.

Co-Founder Matching Template

Intro Call

Co-Founder Matching Call with {Guest} on {Date}

khalidx

Description

Next.js doesn't seem to protect routes that use getServerSideProps().

How can you protect endpoints like:

/_next/data/*/*/something.json

Is this a bug? You can get 50% of the way there with middleware, but the middleware doesn't run on /_next/data/ unless you configure it to.

khalidx

🚧 Issue Description

If you've ever run a script like npm run test from your package.json:

{
  "scripts": {
    "test": "node --test src/**/*.test.js"
  }
}

khalidx

Replace <FirstName>, <LastName>, and <Email> with your information.

mkdir ./cli/ && cd ./cli/
go install github.com/spf13/cobra-cli@latest
cobra-cli init --author "<FirstName> <LastName> <Email>" --license MIT --viper
go mod tidy