hackrole hackrole

You probably don't know how to do Prompt Engineering

(This post could also be titled "Features missing from most LLM front-ends that should exist")

Apologies for the snarky title, but there has been a huge amount of discussion around so called "Prompt Engineering" these past few months on all kinds of platforms. Much of it is coming from individuals who are peddling around an awful lot of "Prompting" and very little "Engineering".

Most of these discussions are little more than users finding that writing more creative and complicated prompts can help them solve a task that a more simple prompt was unable to help with. I claim this is not Prompt Engineering. This is not to say that crafting good prompts is not a difficult task, but it does not involve doing any kind of sophisticated modifications to general "template" of a prompt.

Others, who I think do deserve to call themselves "Prompt Engineers" (and an awful lot more than that), have been writing about and utilizing the rich new eco-system

EDIT: check out fix-python instead, make Python run "as usual" on NixOS!

How to: make Python dependencies installed via pip work on NixOS

The issue

You are using NixOS
You start working on a Python project
You manage the dependencies in a classic Python virtual environment using pip or poetry

A curated list of command-line utilities written in Rust

Note: I have moved this list to a proper repository. I'll leave this gist up, but it won't be updated. To submit an idea, open a PR on the repo.

Note that I have not tried all of these personally, and cannot and do not vouch for all of the tools listed here. In most cases, the descriptions here are copied directly from their code repos. Some may have been abandoned. Investigate before installing/using.

The ones I use regularly include: bat, dust, fd, fend, hyperfine, miniserve, ripgrep, just, cargo-audit and cargo-wipe.

atuin: "Magical shell history"
bandwhich: Terminal bandwidth utilization tool

There's a couple of ways, one way is

Get search results
- Do SPC / and type in your search string
- or SPC x S and search string - where x is your scope indicator (p for project, d for directory, etc..)
Once you have the occurences you want, hit C-c C-e inside the helm buffer to put all your match occurences and puts them into a special buffer called the edit buffer or something like that
in that buffer you can use any commands you'd normally use on a buffer
the C-c C-c to commit your changes.

Comparison of ZSH frameworks and plugin managers

Changelog

update 1: add a FAQ section
update 2: benchmark chart and feature comparison table
update 3:
- improve the table with missing features for antigen
- new zplg times result

	(require 'flycheck)

	;; From https://github.com/flycheck/flycheck/issues/1974#issuecomment-1343495202
	(flycheck-define-checker python-ruff
	"A Python syntax and style checker using the ruff utility.
	To override the path to the ruff executable, set
	`flycheck-python-ruff-executable'.
	See URL `http://pypi.python.org/pypi/ruff'."
	:command ("ruff"
	"--format=text"

	let
	nixpkgs-src = builtins.fetchTarball {
	# master of 2021-01-05.
	url = "https://github.com/NixOS/nixpkgs/archive/1a57d96edd156958b12782e8c8b6a374142a7248.tar.gz";
	sha256 = "1qdh457apmw2yxbpi1biwl5x5ygaw158ppff4al8rx7gncgl10rd";
	};

	pkgs = import nixpkgs-src {
	config = {
	# allowUnfree may be necessary for some packages, but in general you should not need it.

	from sqlalchemy import event
	from sqlalchemy.orm import sessionmaker
	from app.db.session import engine
	import pytest
	import app.tests.config


	@pytest.fixture(
	scope='function',
	autouse=True # New test DB session for each test todo we need it only for tests with Client fixture

	pandoc -f gfm -w jira -o outfile.jira infile.md

	# To import converted file into Confluence:
	# - Create new page
	# - Click on the body of the page, click on the " + \/" dropdown in toolbar ("Insert more content") and select "Markup"
	# - Paste the contents into the pop-up window (select "Confluence wiki" as the format)
	# - Note: The "Markdown" option in the import pop-up doesn't seem to work for Github flavored markdown (gfm).

	# find the kube node of the running pod, appear next to hostIP, and note containerID hash
	kubectl get pod mypod -o json
	# -> save hostIP
	# -> save containerID

	# connect to the node and find the pods unique network interface index inside it's container
	docker exec containerID /bin/bash -c 'cat /sys/class/net/eth0/iflink'
	# -> returns index

	# locate the interface of the node