Bootstrap knowledge of LLMs ASAP. With a bias/focus to GPT.
Avoid being a link dump. Try to provide only valuable well tuned information.
Neural network links before starting with transformers.
The target audience for this is people who are beginners at software engineering and using linux. A lot of the information here may be obvious or already known to you. The language involved is C but you do not need to know any C to read this tutorial. I used mg
to write this blog post. I used vs code to edit the source code.
This post is also available on gopher://tilde.team:70/0/~river/tweak-free-software
If you use a piece of free software and it's 99% perfect but there's just this one thing it does that annoys the hell out of you.. you can in theory just fix it! Here's a look at what doing that is like. Hopefully it inspires you, or you pick up a could tricks on the way!
0-00.usa.cc | |
0-mail.com | |
0.pl | |
001.igg.biz | |
0039.cf | |
0039.ga | |
0039.gq | |
0039.ml | |
007addict.com | |
00b2bcr51qv59xst2.cf |
Rebol [] | |
last-20-closed-issues: { | |
query($owner:String!,$repo:String!) { | |
repository(owner:$owner, name:$repo) { | |
issues(last:20, states:CLOSED) { | |
edges { | |
node { | |
title | |
url |
# PHP Architecture Tester pre-commit hook for git | |
# | |
# @author Carlos Alandete <carlos.alandete@gmail.com> | |
# | |
STAGED_FILES_PHP=$(git diff --cached --name-only --diff-filter=ACM | grep '^src.*\.php\?$') | |
if [[ "$STAGED_FILES_PHP" == "" ]]; then | |
printf "\033[1;32mNo files that could affect PHP Architecture Tester\033[0m\n\n" | |
exit 0 | |
fi |
import 'dotenv/config'; | |
import { NestFactory } from '@nestjs/core'; | |
import * as repl from 'repl'; | |
import * as Logger from 'purdy'; | |
const LOGGER_OPTIONS = { | |
indent: 2, | |
depth: 1, | |
}; |
// inspired by https://github.com/tj/git-extras/blob/master/bin/git-line-summary | |
const util = require("util"); | |
const exec = util.promisify(require("child_process").exec); | |
const execSync = require("child_process").execSync; | |
const DIR = "/Users/poshannessy/FB/code/react-clean"; | |
const REF = "origin/master"; | |
const AUTHOR = "Paul O’Shannessy"; | |
const PERIOD_DAYS = 1; |
Because Travis CI can automatically execute scripts after successfully (or unsuccessfully!) executing tests, it is an obvious choice for a deployment tool. In order to deploy to a Git repository on a remote server, the process generally is as follows:
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
If you want to use travis_retry
from within your own shell script files then you first have to make the travis_retry
shell function available by sourcing the travis_retry.sh
file, otherwise you just get a "command not found" error. See example.sh
for a full example.
Note that the original function as found in the travis-ci/travis-build repository was slightly modified to allow it to be used in a shell context where set -e
is enabled.
For reference, a tweet by Travis CI saying that you should copy the travis_retry
code as I've done here:
https://twitter.com/plexus/status/499194992632811520