asears

Get-Command pac | Format-List
Get-Command dotnet | Format-List
Get-Command code | Format-List
(Get-Command notepad).Path

$exeName = "pac"

asears

https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-messages-management

https://microsoft.github.io/copilot-studio-estimator/

https://www.copilotcalculator.com/

https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/copilot-studio

https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-quotas

asears

https://itsfoss.gitlab.io/post/lf-will-be-replaced-by-crlf-the-next-time-git-touches-it/ https://stackoverflow.com/questions/1125653/python-using-4-spaces-for-indentation-why

git config --global core.autocrlf true

editorconfig - nodejs (python should use 4 indents to match ruff/black and PEP8)

root = true

asears

(Get-Command foundry).path

$mypath = $MyInvocation.MyCommand.Path
Write-Output "Script Path: $mypath"

asears

Package                            Version
---------------------------------- --------------------
absl-py                            2.1.0
accelerate                         0.30.1
adlfs                              2024.2.0
aiohttp                            3.9.3
aiosignal                          1.2.0
alabaster                          0.7.12
alembic                            1.13.2

asears

Reasons to split into multiple workspaces
	• Simplifies cost allocation
	• Makes it possible to use separate capacities
	• Makes it possible to use separate Git repositories
	• Makes it possible to use separate Fabric Deployment Pipelines
	• Makes it possible to use separate regions
	• Makes it possible to use separate default Spark Environment
	• Makes it possible to use separate network security settings
	• Makes it possible to use separate workspace identities

asears

File Type Deployment, Validation, and Testing Guide

This guide maps file types found across the repos to practical deployment, schema checks, data checks, unit tests, and integration tests. It is written for Windows + PowerShell workflows.

Core Principles

• Run fast static checks (lint/schema/type) on every PR.
• Run data and integration checks on merge/main or release branches.
• Keep unit tests isolated with mocks/stubs for network, DB, and cloud calls.
• Use plan/preview first for infrastructure changes.

asears

{
	"folders": [
		{
			"path": "."
		}
	],
	"settings": {
		"workbench.editorAssociations": {
			"*.md": "vscode.markdown.preview.editor"
		}

asears

"""
The most atomic way to train and inference a GPT in pure, dependency-free Python.
This file is the complete algorithm. Everything else is just efficiency.

@karpathy and @claude with the refactoring barkie dog :ruff:
"""

import logging
import math  # math.log, math.exp
import operator

asears

# Few helpful rebase commands

git config --global core.editor=code
git config --global sequence.editor=code --wait --reuse-window
# Find the divergent commit
git merge-base --fork-point main
# Interactive rebase
git rebase -i