Joe Palala jpalala

Python venv virtual environment cheat sheet

Create a venv

To create a virtual environment, go to the root of your project and run

python -m venv venv

It will create a virtual environment called venv

Activate venv

.\venv\Scripts\activate

Quotes for dev motivation

Note: technically generic quotes are not copyright. But if you do use this, kindly attribute me somewhere.

LICENSE

CC-BY

It is great that you are leveling up your coding standards! Moving from "making code work" to "writing clean, professional code" is exactly how you become a strong Python developer.

To follow Pythonic standards, you need to think beyond just syntax and embrace the "Pythonic" philosophy.

1. The "Zen of Python"

Before you start linting, you should know the philosophy that drives the language. You can actually see this by typing import this into your Python terminal. Here are the most critical takeaways for your code:

NOTE: Add this to your CLAUDE.md

Project Guidelines

Agent Behavior & Constraints

CRITICAL: Before executing any code, file modifications, or architectural decisions, you MUST validate your current task against the routing directives defined in .claude/system_prompt.
You are operating as a Meta-Prompt Route Orchestrator.
If a task falls into Analyzing, Writing, Reviewing, or Architecting, you must halt autonomous execution and ask the user for the required file context or diffs specified in the Interception Protocol.

Welcome to NestJS! If you are coming from Express or Fastify, NestJS can feel a bit rigid at first because it heavily embraces Architecture and Dependency Injection (very similar to Angular or Spring Boot). However, once you get the hang of it, that rigidity becomes its superpower—it ensures large codebases stay organized.

1. Navigating the File Structure

When you create a new project using nest new project-name, you get a boilerplate. NestJS relies heavily on a module-based (domain-driven) architecture.

Here is what a standard, well-organized NestJS project structure looks like as it grows:

Deploying a Static Site to Cloudflare Pages via Wrangler CLI

This guide outlines the direct, programmatic workflow for deploying a static website or single-page application (SPA) to Cloudflare Pages.

By utilizing the Cloudflare Wrangler CLI, you bypass the need to manually configure projects inside the Cloudflare dashboard UI. The entire lifecycle—from initialization to deployment—is managed entirely from your terminal or CI/CD pipeline.

🚀 Architectural Advantage: Zero-UI Configuration

Yes, you can do it with Codex. It does not have to be Claude.

Codex supports three related modes:

1. Local agent work

codex

Large language models (LLMs) are very good at generating code that matches patterns they’ve seen during training. That strength also creates several important limitations.

1. Pattern matching ≠ true software understanding

LLMs generate code by predicting likely token sequences, not by reasoning about program correctness the way a compiler or experienced engineer would.

This means they can:

Produce code that looks correct but fails edge cases
Misunderstand implicit requirements

Building a modern login page inspired by your screenshot is a great way to streamline user onboarding. To achieve this in Laravel, we'll use Tailwind CSS for styling and Lucide Icons (an excellent open-source alternative) to match that clean, professional look.

1. The Blade View (`resources/views/auth/login.blade.php`)

This template uses the same layout structure as Replit: a centered card, large "Continue with" buttons, and a clean email input section.

<!DOCTYPE html>
<html lang="en">
<head>

	var nodemailer = require('nodemailer');
	var sesTransport = require('nodemailer-ses-transport');
	var smtpPassword = require('aws-smtp-credentials');

	var mailOptions = {
	from: 'from@example.com',
	to: 'to@example.com',
	text: 'This is some text',
	html: '<b>This is some HTML</b>',
	};