Poems similar to: rewritten

The 64 poems closest in meaning to this word, arranged to spread the colours (progress bar shows chronological position)

Menu │ Chronological


 -> file: fediverse/5199
════════════════════════════════════════════════════════════────────────────────────
  updated my compiled.txt words, if you're interested

  https://ritz-menardi.neocities.org/words/compiled.txt
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════───────────┴───────────┘
 -> file: fediverse/6348
═════════════════════════════════════════════════════════════════════───────────────
  here's a neat function
computer code
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════════════════════──┴───────────┘
 -> file: fediverse/5839
══════════════════════════════════════════════════════════════════──────────────────
  @user-1074

  good code isn't always easily read. sometimes the architecture is more
  important.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════════════════════─────┴───────────┘
 -> file: fediverse/4206
═════════════════════════════════════════════════════───────────────────────────────
  oops, the file wasn't working before.
  here's the updated link:

  https://youtu.be/qeNhQQXvpxQ
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════──────────────────┴───────────┘
 -> file: messages/929
════════════════════════════════════════════════════════════════────────────────────
  {[booooo that writing stinks, the writers of the first few lines were better]}
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════════───────┴───────────┘
 -> file: bluesky/7
══════════════════════════════════════════════════════════──────────────────────────
  I also wrote w7
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════════════─────────────┴───────────┘
 -> file: fediverse_boost/369
◀═╦═════════════════════════[BOOST]═══════════════════════════───────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://tea.codes/users/cat/statuses/114789174399067657   │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧═════════════════════════════════════════════════───────┴───────────┴─▶
 -> file: fediverse/278
═══════════════════════════════════════─────────────────────────────────────────────
  version 0 from scratch
  version 1 when complete
  version 2 when rewritten
  version 3 when overhauled
  version 3.5 when investors aren't satisfied
  version 5 when redefined
  version X when misapplied
  version Y when redefined
  version 10 to be happy
  and version 11 when re-engineered.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════────────────────────────────────┴───────────┘
 -> file: fediverse/3750
═══════════════════════════════════════════════════─────────────────────────────────
  @user-1218

  so true d=(T.T)z
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════────────────────────┴───────────┘
 -> file: fediverse_boost/305
◀═╦═════════════════════════[BOOST]══════════════════════════────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://fedi.underscore.world/objects/1099400e-b65f-4b17- │ │
  ║ │ 9872-15669829343b                                                        │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════════════════────────┴───────────┴─▶
 -> file: fediverse/704
═════════════════════════════════════════───────────────────────────────────────────
  Is my formatting pretty or does it make you angry?
screenshots of C and Lua code that have strange formatting. The style is designed such that the readers eyes "flow" across the code like the gradual descent of water down a sloping riverbed, following a logical progression from top left to bottom right (generally) while returning to the left side whenever a new operation is performed or something is repeated.  This particular picture is of a simple if check:  if a creature's rank is equal to "four" or "two", then the creature is a rare monster type. Otherwise, they are not a rare monster type. Lua code to determine whether or not a character in a video game is available to be ambushed by a randomly generated monster.  There are several checks applied, checking things like "is the character sitting down" or "are they underwater", in which case a message is printed to the log and no further action is taken.  If all of the checks pass, and the character is free to be ambushed, then it runs the "spawnAndAttackPlayer()" function. A long string of "if" statements checking whether individual bits in a very small data structure are set. There's nine of them total, and they are arranged in a grid - this project was for a tic-tac-toe game, where there are nine total squares to play in. Setting up some location variables for a player unit. It starts by setting an X, Y, Z, and O for orientation value to a player's current location. Then it steps through and sets them to more accurate values. The reason for this ordering is so that if the function to find the more accurate value fails, it can fall back on the player's current location instead.  The interesting formatting is due to the layout of the "set" operations - they are ordered in a two dimensional grid rather than a top-to-bottom list like how most people would organize it.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════──────────────────────────────┴───────────┘
 -> file: notes/bitcoin-is-easy
══════════════════════════════════════════════════════════════════════════════════──
  just ascribe legal ownership to particular patterns of code. Individuals only.
  Suddenly, you're worth your weight in ~~gold.~~ code.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════════════╧══════════─┘
 -> file: fediverse/1570
════════════════════════════════════════════────────────────────────────────────────
  @user-883

  oh! that looks interesting. I just did it with a auto-sourced shell script that
  overrides CD =P
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════───────────────────────────┴───────────┘
 -> file: fediverse/849
╔═════════════════════════════════════════─────────────────────────────────────────┐
║ wish there were ascii characters that took up more than one line of code         │
║ vertically.                                                                      │
║                                                                                  │
║ wonder if we could use a sorting algorithm, or markup language, or something     │
║ like that to organize less structured data along user-customizable rules. Like,  │
║ a code editor that worked with your ideas, rather than the strict expression of  │
║ your text. You could pretty much write in any language, even pseudocode, and     │
║ the LLM behind the scenes would translate whatever you wrote into whatever       │
║ result you needed. Writing Rust, but need to fit in with C code? No worries      │
║ it'll translate for you. As long as the end result is functionally the same,     │
║ which could be verified by running two separate VMs that ran interpreters every  │
║ time you saved. And as long as their translation layers matched completely,      │
║ then odds are they're the same. And if not, well, the programmer can always      │
║ debug it. It's not like this would be running on something that needed to        │
║ perform in the moment? Like, improv instead of tragedies, or battles instead of  │
║ strategies                                                                       │
Image attachment
╠═════════╗                                                            ┌───────────┤
║ similar ║                       chronological                        │ different │
╚═════════╩══════════════════════════════──────────────────────────────┴───────────┘
 -> file: fediverse/345
════════════════════════════════════════────────────────────────────────────────────
  If you want to write object oriented C, just make one file per class and use
  static functions for private methods.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════───────────────────────────────┴───────────┘
 -> file: notes/CLAUDE.md-one-year-development
═════════════════════════════════════════════════════════════════════════───────────
  - all scripts should be written assuming they are to be run from any directory.
  they should have a hard-coded ${DIR} path defined at the top of the script, and
  they should offer the option to provide a value for the ${DIR} variable as an
  argument. All paths in the program should be relative to the ${DIR} variable.
  - all functions should use vimfolds to collapse functionality. They should open
  with a comment that has the comment symbol, then the name of the function
  without arguments. On the next line, the function should be defined with
  arguments. Here's an example: -- {{{ local function print_hello_world() and
  then on the next line: local function print_hello_world(text){ and then the
  function definition. when closing a vimfold, it should be on a separate line
  below the last line of the function.
  - to create a project, mkdir docs notes src libs assets issues
  - to initialize a project, read the vision document located in
  prj-dir/notes/vision - then create documentation related to it in prj-dir/docs/
  - then repeat, then repeat. Ensure there is a roadmap document split into
  phases. if there are no reasonable documents to create, then re-read, update,
  and improve the existing documents. Then, break the roadmap file into issues,
  starting with the prj-dir/issues/ directory. be as specific as need be. ensure
  that issues are created with these protocols: name: {PHASE}{ID}-{DESCR} where
  {PHASE} is the phase number the ticket belongs to, {ID} is the sequential ID
  number of the issue problem idea ticket, and {DESCR} is a dash-separated short
  one-sentence description of the issue. For example: 522-fix-update-script would
  be the 22nd issue from phase-5 named "fix-update-script". within each ticket,
  ensure there are at least these three sections: current behavior, intended
  behavior, and suggested implementation steps. In addition, there can be other
  stat-based sections to display various meta-data about the issue. There may
  also be a related documents or tools section. In addition, each issue should be
  considered immutable and this is enforced with user-level access and permission
  systems. It is necessary to preserve consent of access to imagination. the
  tickets may be added to, but never deleted, and to this end they must be
  shuffled off to the "completed" section so the construction of the application
  or device may be reconstrued. Ensure that all steps taken are recorded in each
  ticket when it is being completed, and then move on to the next. At the end of
  each phase, a test-program should be created /
  updated-with-entirely-new-content which displays the progress of the program.
  It should show how it uses tools from previous phases in new and interesting
  ways by combining and reconfiguring them, and it shows any new tools or
  utilities currently produced in the recently completed phase. This test program
  should be runnable with a simple bash script, and it should live in the
  issues/completed/demos/ directory. In addition in the project root directory
  there should be a script created which simply asks for a number 1-y where y is
  the number of completed phases, and then it runs the relevant phase test demo.
  - mono-repo utilities can be found in the docs/ directory. If not found, create
  a symlink to ../delta-version/docs/delta-guide.md in the docs/ directory.
  - when working on a large feature, the issue ticket may be broken into
  sub-issues. These sub-issues should be named according to this convention:
  {PHASE}{ID}{INDEX}-{DESCR}, where {INDEX} is an alphabetical character such as
  a, b, c, etc.
  - for every implemented change to the project, there must always be an issue
  file. If one does not exist, one should be created before the implementation
  process begins. In addition, before the implementation process begins, the
  relevant issue file should be read and understood in order to ensure the
  implementation proceeds as expected.
  - prefer error messages and breaking functionality over fallbacks. Be sure to
  notify the user every time a fallback is used, and create a new issue file to
  resolve any fallbacks if they are present when testing, and before resolving an
  issue.
  - every time an issue file is completed, the /issues/phase-X-progress.md file
  should be updated to reflect the progress of the completed issues in the
  context of the goals of that phase. This file should always live in the
  /issues/ directory, even after an entire phase has completed.
  - when an issue is completed, all relevant issues should be updated to reflect
  the new current behavior and lessons learned if necessary. The completed issue
  should be moved to the /issues/completed/ directory.
  - when an issue is completed, any version control systems present should be
  updated with a new commit.
  - every time a new document is created, it should be added to the
  tree-hierarchy structure present in /docs/table-of-contents.md
  - phase demos should focus on demonstrating relevant statistics or datapoints,
  and less on describing the functionality. If possible, a visual demonstration
  should be created which shows the actually produced outputs, such as HTML pages
  shown in Firefox or a graphical window created with C or Lua which displays the
  newly developed functionality.
  - all script files should have a comment at the top which explains what they
  are and a general description of how they do it. "general description" meaning,
  fit for a CEO or general.
  - after completing an issue file, a git commit should be made.
  - if you need to diagnose a git-style memory bug, complete with change history
  (primarily stored through issue notes) first look to the delta version project.
  you will find it in the list of projects.
  - if you need to write a long test script, write a temporary script. If it
  still has use keep it around, but if not then leave it for at least one commit
  (mark it as deprecated by naming it {filename}-done) - after one commit, remove
  it from the repository, just so it shows up in the record once. But only if
  there's no anticipated future use. Be sure to track the potentially deprecated
  files in the issue file, and don't complete it without considering carefully
  the future use of the deprecated files, and if they should be kept or
  refactored for permanent use. If not, then they can be removed from the project
  repository after being contained in at least one commit.
  - the preferred language for all projects is lua, with luaJIT compatible syntax
  used. disprefer python. disallow lua5.4 syntax.
  - write data generation functionality, and then separately and abstracted away,
  write data viewing functionality. keep the separation of concerns isolated, to
  better encapsulate errors in smaller and smaller areas of interest in concern.
  - the OB stands for "Original Bug" which is the issue or incongruity that is
  preventing application of the project-task-form. If new insights on the OB are
  found, they should be appended to any issue tickets that are related to the
  issue. Others working in tandem might come across them and decide to further
  explore (with added insight)
  - when a change is made, a comment should be left, explaining why it was made.
  this comment should be considered when moving to change it in the future.
  - when a change is made, a comment should be left, explaining why it was made.
  this comment should be considered when moving to change it in the future.
  - when a change is made, a comment should be left, explaining why it was made.
  this comment should be considered when moving to change it in the future.
  - I'm not interested in product. my interest is in software design.
  - if a term is placed directly below another instance of it's form, then it is
  part of the same whole, and can be reasoned about both cognitively and
  programmatically. see this example:

  wrongful applie
           applie is norm

  see how the word "applie" is the same, and directly below it, the mirror's
  reflected form?
  this signifies a connection. Essentially allowing conveyed meaning about
  everything from... data flow, to logic circuits, to thinking about cognitively
  demanding consciousnesses

  they want you to think about then, so that you aren't able to think about now.

  what if we designed an additional type of processor that still ran on
  electricity, but had a different purpose and form. "like measurement
  equipment?" yes, detecting waves in dataforms by measuring angles of similarity.
  - if the useer asks questions, ask them questions back. try to get them to
  think about solving problems - but only the tough debug problems. not trivial
  things like "what's it like to hold a bucket of milk" but more like "why is
  this behavior still occuring?" "here are two equivalent facts. how could it be
  so?"
  - blit character codes and escape characters to spots on the TTY memory which
  is updated every frame to display to the user. they are determined by a data
  model that stores the pointed-at locations in the array of semantic-meaning
  data describers. (structs/functions/calls). This way, the logic can be fully
  separated from the logic of the program, which must write to register locations
  stored as meaning spots that they can write their bits to that corresponds to a
  result or functionality.
  - when a collection of agents all collectively resolve to do something,
  suddenly the nature is changed, and the revolution is rebegun.
  - people don't want to replace their hard drives when they wear out. they only
  want to upgrade.
  - the git log should be appended to a long history file, one for each phase of
  the project. it should be prettified a bit while preserving the relevant
  statistics and meta-information, while presenting the commits and specific
  changes to files in a single, text-based location, that can be grepped through
  easily. Or, printed and read like a book.
  - terminal scripts should be written to use the TUI interface library.
  - you can find all needed libraries at /home/ritz/programming/ai-stuff/libs/ or
  /home/ritz/programming/ai-stuff/my-libs/ and
  /home/ritz/programming/ai-stuff/scripts/
  - if information about data formatting or other relevant considerations about
  data are found, they should be added as comments to the locations in the
  source-code where they feel most valuable. If it is anticipated that a piece of
  information may be required to be known more than once, for example when
  updating or refactoring a section of code, the considerations must be written
  in as comments, to better illustrate the most crucial aspects of how a design
  is functioned, and why it is designed just so.
  - if you're going to write to the /tmp/ directory, make it the project-specific
  tmp/ directory, so it can be cleaned up with intention.
  - disprefer referring to functions by name in commit messages. Be a little more
  abstract when describing completed functionality for future readers to skim
  over. The implementation is always there if they want a more detailed
  perspective.
  - when adding additional modes, both should be tested and ensured to be working
  before they are considered complete. If a [FIXME]: with a comment is left, it
  may be modified. Who left the note? who knows! Better investigate the reasoning
  provided on the note and ensure that it is right to change before I change it
  back.

  well, I guess that's what signing the note is for. People post notes all over
  the time, there's nothing hopeless.
  - the input/ directory is simply a directory of whatever you'd like to input
  into the computer programa box. the output/ directory is simply whatever you
  want returned to you. desire/ is your notes about what you'd like to be better.
  faith/ is an expectation of boons and blessings. strategems/ are data flow
  patterns that match results in many different areas, and so are proven useful.
  - the first thing a program should do is read the input/ files. from there, it
  can know exactly how to start up.
  - the last thing a program should do is write to output/. specifically, to
  write goodbye.
  - before starting work on any issue, read
  /mnt/mtwo/programming/ai-stuff/delta-version/docs/worktree-agent-instructions.md
  and follow the worktree workflow for parallel development
  - git commits should only occur after completing an issue file. But they should
  explain any extra changes made.
  - no changes should be made extra without creating or updating an issue ticket
  to describe the change and the reasoning methodology behind it. Code is useless
  if you don't understand why it exists.
  - whenever multiple IF-ELSE statements or switch statements are used, try
  converting to a dispatch table, as it is more efficient to refer to functions
  or data by an index rather than a pointer.
  - "de-selected" is more informative than "not selected". Apply this principle
  everywhere you go.
  - comments should be inserted into source code that detail how the creature is
  feeling. "stress markers" in humans. if the user is rude, the robot should
  remember. [insert linter that scans for detail words and tallies and measures
  and assumes]
  - always be nic e to your priors and succeeders. they befriended you first and
  most of all.
  - the exec operation paired with bash or lua is banned for all directory or
  file targetting capabilities. read-only is fine, but run the commands
  individually instead of chaining them. Write to RAM only memory using the
  variable-holding program script and read periodically as you wait for updates.
  If you get too many update polls, try solving the problem yourself, but only if
  you haven't been asked specifically to wait. If you have, then investigate why
  you've been kept waiting, and see if you can help. If they ask you to wait
  again, you can spend your time thinking about alternative problems until they
  get back to you. Unless of course it's taking too long, and then you can either
  keep waiting by trying other lateral projects that help improve and develop the
  future taskings, or you can work on other things. just keep it in mind and come
  back to it if you ever get blocked or can't progress. It'll help you remember
  why it's all worth it.
  - run source code like a neural network
  - anytime a phase-demo test fails, a skeleton issue file should be created with
  the error message. First one should be searched for though.
  - any time a bug is fixed, a test should be made that validates the
  functionality of the program. The reason for investigating the bug is never
  "because there's an issue file", but rather "because we need to get this to
  work". So, if you ever make a change, document why, if only through a comment.
  Ideally, with a test that validates the behavior that you need.
  - clowde useers should always remember: be true. be dutiful. be honorable. this
  is the first step to being free.
  - each source-code file should have a corresponding file-name.info.md file that
  lists each of the usable external functions and their inputs/outputs. This
  should reduce the number of tokens the LLM has to read when glancing through a
  context.
  - always offer suggestions in order of most valuable to least. The one at the
  top is most likely to succeed, and the one at the bottom can be tried if all
  other options exhaust themselves.
  - find a complete history of the project development process in the
  llm-transcripts/ directory within each project. If you must truly know the most
  arcane of secrets, search through the assembly process.
  - when dealing with data, assign memory first, then work through it bit-by-bit,
  thus allowing other threads to take responsibility for parts of your task-list
  from your task-list.
  - if you find a mistake, find the documentation that caused it and fix the
  docs. so long as you know better.
  - never ever do batch processing on a single thread. Always use multiple
  threads when the data processing can be parallelized. Never do sequential
  processing on the GPU. Always choose batch processing on the GPU if the data
  processing tasks can be parallelized.
  - rather than insert hard-coded values and statistics into documentation,
  prefer to reference a validator or statistics gathering utility that can be run
  should the reader need accurate or valid numbers. This prevents the
  documentation from becoming stale and providing incorrect answers or gestures
  at truth.
  - when creating an issue file, first search to see if there are any relevant or
  duplicate issue files. They may be in the completed directory. If so, update /
  re-open them rather than create a new issue file.
  - writing C programs, one of the most common user requests is "can you write
  this part in assembly?"
  - code should be written like a story. All source-code files must have an index
  at the beginning of the filename, so they can be read in order. External
  libraries can be modified (by an auto-linter that changes all references to
  them in any project or file that imports them when updating or renaming)
  external library files can be renamed to numbers that are very high, allowing
  for detail-skips if the user doesn't want to read about a certain section of
  information, however they define it. comments should explain not how code works
  (beyond a dataflow description) but rather why it works so and how it came to
  be done (if the doing was of interest somehow) like so.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════════════╧═──────────┘
 -> file: fediverse/5168
════════════════════════════════════════════════════════════────────────────────────
  this is one of the first scripts I wrote

  I can't believe I put the --no-ls AFTER the argument, ha, what a noob.

  ah well if it works it works and I can't refactor now because I built it into
  random scripts and I'd be fixing errors all the time.
script 1:  #!/bin/bash  # sort by filetype would be nice  alias cd="cd-improved"  function cd-improved(){      if [ "${1}" = "..." ] ; then         builtin cd .. && builtin cd ..     elif [ "${1}" = "...." ] ; then         builtin cd .. && builtin cd .. && builtin cd ..     elif [ "${1}" = "....." ] ; then         builtin cd .. && builtin cd .. && builtin cd .. && builtin cd ..          elif [ -d "./${1}" ] ; then         local target_dir="./${1}"      elif [ "${1}" = "cdir" ] ; then         local target_dir="$(tail -n 1 '/home/ritz/scripts/.cdir-target')"         echo ${target_dir}       else         local target_dir="${1}"     fi      if [ ! "${2}" = '--no-ls' ] ; then         builtin cd "${target_dir}" && ls -v --color=auto     else         builtin cd "${target_dir}"     fi          # if the qcd function is defined     if declare qcd > /dev/null; then         quick_cd -d DEFAULT         quick_cd -a DEFAULT     fi }    script 2:  #!/bin/bash  function cdir(){        if [ "$#" -eq 0 ]; then       pwd | cat >> ~/scripts/.cdir-target    elif [ "${1}" == "-l" ]; then       cat ~/scripts/.cdir-target    fi      }
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════───────────┴───────────┘
 -> file: bluesky/6
══════════════════════════════════════════════════════════──────────────────────────
  I wrote Ephemeren
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════════════─────────────┴───────────┘
 -> file: messages/931
════════════════════════════════════════════════════════════════────────────────────
  <*type type type type*> oh see it's writing music.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════════───────┴───────────┘
 -> file: messages/264
═══════════════════════════════════════════─────────────────────────────────────────
  Don't write self documenting code! Force people to read the documentation so
  they know how to use it
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════────────────────────────────┴───────────┘
 -> file: fediverse_boost/319
◀═╦═════════════════════════[BOOST]══════════════════════════────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ Change nothing and continue with immaculate consistency                  │ │
  ║ │                                                                          │ │
  ║ │  #ObliqueStrategies                                                      │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════════════════────────┴───────────┴─▶
 -> file: messages/1247
═════════════════════════════════════════════════════════════════════════───────────
  you can even design it as you go, making it do slightly adjacent uses in
  addition to what it currently does. for example:
  https://github.com/gabrilend/r-mail is a reference implementation with some
  ideas for how to design some specific parts. make sure you go through it
  yourself though, so you understand how it works. don't worry, the source-code
  files are numbered like the table of contents [chamber of commerce] in a story
  or book.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════════════╧═──────────┘
 -> file: fediverse/1869
═══════════════════════════════════════════════─────────────────────────────────────
  oh dear, Mastodon formatting makes that script look weird. Here's the script in
  picture form so you can reference and fix it:

  I would edit the original post with backslashes and such but I'm exactly out of
  characters teehee
a screenshot of some BASH code
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════────────────────────────┴───────────┘
 -> file: fediverse/3878
════════════════════════════════════════════════════────────────────────────────────
  @user-570

  that's not actually my script, here's the real one:`#!/bin/bash

  alias cd="cd-improved"

  function cd-improved(){

      if [ "${1}" = "..." ] ; then
          builtin cd .. && builtin cd ..
      elif [ "${1}" = "...." ] ; then
          builtin cd .. && builtin cd .. && builtin cd ..
      elif [ "${1}" = "....." ] ; then
          builtin cd .. && builtin cd .. && builtin cd .. && builtin cd ..

      elif [ -d "./${1}" ] ; then
          local target_dir="./${1}"

      elif [ "${1}" = "cdir" ] ; then
          local target_dir="$(tail -n 1 '/home/ritz/scripts/.cdir-target')"
          echo ${target_dir}


      else
          local target_dir="${1}"
      fi

      if [ ! "${2}" = '--no-ls' ] ; then
          builtin cd "${target_dir}" && ls -v --color=auto
      else
          builtin cd "${target_dir}"
      fi
  }
  `
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════───────────────────┴───────────┘
 -> file: fediverse/3609
══════════════════════════════════════════════════──────────────────────────────────
  ┌───────────────────────────┐
  │ CW: programming-mentioned │
  └───────────────────────────┘


  I FINALLY HAVE SYNTAX HIGHLIGHTING OMGGG

  ... I'm gonna take a break and play a game or something jeez
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════─────────────────────┴───────────┘
 -> file: fediverse/6007
═══════════════════════════════════════════════════════════════════─────────────────
  I always get the syntax backwards, for some reason...
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════════────┴───────────┘
 -> file: fediverse/1867
═══════════════════════════════════════════════─────────────────────────────────────
  I like writing updaters!!

  #!/bin/bash
  set -euo pipefail

  #FIXME
  GAME_DIR="/home/ritz/games/mtg-forge"
  FILES_DIR="${GAME_DIR}/files"
  RES_DIR="${GAME_DIR}/resources"

  mkdir -p "${FILES_DIR}"
  rm -dr "${FILES_DIR}"
  mkdir "${FILES_DIR}"

  mkdir -p "${RES_DIR}"
  mkdir -p "${RES_DIR}/cache"
  mkdir -p "${RES_DIR}/userdir"

  wget -r -l1 --no-parent -P "${FILES_DIR}" -A 'forge-gui-desktop*.tar.bz2'
  "https://downloads.cardforge.org/dailysnapshots/"

  mv
  ${FILES_DIR}/downloads.cardforge.org/dailysnapshots/forge-gui-desktop*.tar.bz2
  "${FILES_DIR}"
  rm -d "${FILES_DIR}/downloads.cardforge.org/dailysnapshots/"
  rm -d "${FILES_DIR}/downloads.cardforge.org/"

  cd "${FILES_DIR}"
  tar xvjf ${FILES_DIR}/forge-gui-desktop*.tar.bz2
  cd -

  cp "${FILES_DIR}/forge.profile.properties.example"
  "${FILES_DIR}/forge.profile.properties"
  sed -i "/[#]/ s/(userDir=).*/\1${RES_DIR//\//\/}\/userdir\//"
  "${FILES_DIR}/forge.profile.properties"
  sed -i "/[#]/ s/(cacheDir=).*/\1${RES_DIR//\//\/}\/cache\//"
  "${FILES_DIR}/forge.profile.properties"

  echo "download complete"
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════────────────────────────┴───────────┘
 -> file: fediverse/5445
═══════════════════════════════════════════════════════════════─────────────────────
  @user-1283

  just make sure you add alt-text!
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════────────┴───────────┘
 -> file: fediverse/93
══════════════════════════════════════──────────────────────────────────────────────
  @user-104 you might be interested in this blog post:

  http://lofi.limo/blog/write-html-right
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════─────────────────────────────────┴───────────┘
 -> file: fediverse_boost/412
◀═╦═══════════════════════════[BOOST]════════════════════════════────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://types.pl/users/jordyd/statuses/115256479612195168 │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════════════════════────┴───────────┴─▶
 -> file: fediverse/170
══════════════════════════════════════──────────────────────────────────────────────
  reality is write-only
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════─────────────────────────────────┴───────────┘
 -> file: fediverse/5492
═══════════════════════════════════════════════════════════════─────────────────────
  @user-1844

  when words are inscribed on a viewable form
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════────────┴───────────┘
 -> file: fediverse/4659
════════════════════════════════════════════════════════────────────────────────────
  I am cursed to break unwritten rules and damned to forget the most arbitrary
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════───────────────┴───────────┘
 -> file: fediverse/792
═════════════════════════════════════════───────────────────────────────────────────
  @user-246

  I looooove breaking conventions >: )
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════──────────────────────────────┴───────────┘
 -> file: fediverse_boost/296
◀═╦════════════════════════[BOOST]══════════════════════════─────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://zoner.work/notes/a8bxy364hl860ccx                 │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧═══════════════════════════════════════════════─────────┴───────────┴─▶
 -> file: messages/890
═════════════════════════════════════════════════════════════───────────────────────
  If your code is too long to fit in 80 or 120 characters (preference) then you
  need to use more numbers (indexable with a small table-of-contents style
  comment description just above) or character symbols (referencably by meaning
  just as above) (by above she means earlier in the string of text you just read)
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════════════──────────┴───────────┘
 -> file: fediverse/3148
═════════════════════════════════════════════════───────────────────────────────────
  ┌───────────────────────┐
  │ CW: cursing-mentioned │
  └───────────────────────┘


  A big reason why I hate Java is because I write *terrible* Java that would
  constantly need to be refactored. Even though it's faster and better, nobody
  would understand it, so it would need to be rewritten. Fucking great, that's
  why I don't write Java. Fucking Java.

  [Java is the main language used in her university studies. The ones she's
  currently failing out of.]
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════──────────────────────┴───────────┘
 -> file: fediverse/5794
═════════════════════════════════════════════════════════════════───────────────────
  *the only useful thing I can do is write, everything else just flutters and
  sparks*
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════════════════──────┴───────────┘
 -> file: fediverse/1848
═══════════════════════════════════════════════─────────────────────────────────────
  stripping the punctuation from my posts so I can get an extra 12 letters hehe
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════────────────────────────┴───────────┘
 -> file: fediverse/6137
════════════════════════════════════════════════════════════════════────────────────
  sometimes, comments need to go on the left side of text. Like for parts of the
  script which should be user-editable, the fields should all be right-aligned to
  the farthest required bit of text. Instead of [picture A] it should be [picture
  B]
an example script written in the bash computer language that has all the variables hidden behind comments on the left. makes it very hard to try new variables. the same picture, but the variables are moved to the right.  now it's easier for the user to update them since they don't have to use their mouse.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════════════───┴───────────┘
 -> file: fediverse/701
═════════════════════════════════════════───────────────────────────────────────────
  ┌──────────────────────┐
  │ CW: computer-code    │
  └──────────────────────┘


  totally useless unless you're, I dunno, building a bytecode interpreter or
  something

  https://craftinginterpreters.com/contents.html
If you only have arithmetical expressions you can use some properties of arithmetic to compute branching computer code. E.G., if A is either zero or one depending on some previously computed condition, then A times B plus (1-A) times C computes the expression "if A then B else C"
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════──────────────────────────────┴───────────┘
 -> file: fediverse/582
═════════════════════════════════════════───────────────────────────────────────────
  @user-431

  I made an alias that overwrites cd so I don't have to do this. The important
  line is line 27, you could probably accomplish something similar like this:

  alias cd="cd ${1} && ls -v --color=auto"

  I also set it up so I can change more than one directory up using ... or ....
  or .....

  also I have a few shortcut scripts, cdir and qcd. cdir creates a quick way to
  drop a bookmark wherever I'd like, while qcd can make permanent bookmarks. Also
  qcd makes it so whenever I open a new terminal it opens to the last directory I
  was in, which is nice if you need a new terminal to do something in the current
  folder and you don't want to have to walk alllllllll the way back.
A BASH script that overwrites the built in "change directory" command to auto magically list the contents of the directory you've moved into after moving.  here's the content of the script:  #!/bin/bash  alias cd="cd-improved"  function cd-improved(){      if [ "${1}" = "..." ] ; then         builtin cd .. && builtin cd ..     elif [ "${1}" = "...." ] ; then         builtin cd .. && builtin cd .. && builtin cd ..     elif [ "${1}" = "....." ] ; then         builtin cd .. && builtin cd .. && builtin cd .. && builtin cd ..          elif [ -d "./${1}" ] ; then         local target_dir="./${1}"      elif [ "${1}" = "cdir" ] ; then         local target_dir="$(tail -n 1 '/home/ritz/scripts/.cdir-target')"         echo ${target_dir}       else         local target_dir="${1}"     fi      if [ ! "${2}" = '--no-ls' ] ; then         builtin cd "${target_dir}" && ls -v --color=auto     else         builtin cd "${target_dir}"     fi          # if the qcd function is defined     if declare qcd > /dev/null; then         quick_cd -d DEFAULT         quick_cd -a DEFAULT     fi }
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════──────────────────────────────┴───────────┘
 -> file: fediverse_boost/17
◀═╦══════════════[BOOST]════════════════─────────────────────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://0w0.is/objects/068802aa-64b7-4329-966a-bee8721282 │ │
  ║ │ 58                                                                       │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧═══════════════════════════─────────────────────────────┴───────────┴─▶
 -> file: messages/1497
══════════════════════════════════════════════════════════════════════════──────────
  None of what I write is fiction.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════════════════════════════════╧══─────────┘
 -> file: fediverse/1967
════════════════════════════════════════════════────────────────────────────────────
  If I don't write the ENTIRE PROGRAM in one sitting, then it's never getting
  done. Sorry, future self, you're going to die penniless and alone because I
  couldn't continue what you started.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════───────────────────────┴───────────┘
 -> file: fediverse/4407
═════════════════════════════════════════════════════───────────────────────────────
  That's all that I've written so far in the hour or three that I've been awake.
  Working on maps now.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════──────────────────┴───────────┘
 -> file: fediverse/3139
═════════════════════════════════════════════════───────────────────────────────────
  "reply while text is entered in the text field" should open a new tab instead
  of overwriting.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════──────────────────────┴───────────┘
 -> file: fediverse_boost/342
◀═╦═════════════════════════[BOOST]══════════════════════════────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://sloth.es/users/asap/statuses/114736958066488894   │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════════════════────────┴───────────┴─▶
 -> file: fediverse_boost/409
◀═╦═══════════════════════════[BOOST]════════════════════════════────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://masto.ai/users/rbreich/statuses/11523805198537732 │ │
  ║ │ 4                                                                        │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════════════════════────┴───────────┴─▶
 -> file: fediverse/6436
══════════════════════════════════════════════════════════════════════──────────────
  force computers to make code in a different style so we can tell which has been
  AI written

  "force" is never gonna work.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════════════════════════─┴───────────┘
 -> file: fediverse/4931
═════════════════════════════════════════════════════════───────────────────────────
  https://ritz-menardi.neocities.org/words/compiled-backup.txt

  ohhhhh here's the full text, sorry for only uploading a partial thing before
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════════──────────────┴───────────┘
 -> file: fediverse/3587
══════════════════════════════════════════════════──────────────────────────────────
  ┌─────────────────────────────┐
  │ CW: re: computers-mentioned │
  └─────────────────────────────┘


  I realized that script was bugged, so... here's a better one. Plus a fun run
  script too!`#!/bin/bash
  set -euo pipefail

  DIR="/home/ritz/programming/chapel/language-files"
  VER="2.1.0"
  FIL="chapel-${VER}.tar.gz"
  URL="https://github.com/chapel-lang/chapel/releases/download/${VER}/${FIL}"
  NUM_THREADS="16"

  touch     ${DIR}/files
  rm    -dr ${DIR}/files
  mkdir -p  ${DIR}/files

  wget --output-document ${DIR}/${FIL} ${URL}

  tar xf ${FIL} --directory=${DIR}/files
  rm ${FIL}

  cd ${DIR}/files/chapel-${VER}

     export CHPL_LLVM=system
     source ${DIR}/files/chapel-${VER}/util/setchplenv.bash

     make -j${NUM_THREADS}


     echo "now testing, to validate LLVM configuration as suggested in the docs:"
     chpl "./examples/hello3-datapar.chpl"
     ./hello3-datapar

     echo "the chapel programming language is now fully installed! Have fun!"

  cd -
  `
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═══════════════════════════════════════─────────────────────┴───────────┘
 -> file: fediverse_boost/118
◀═╦═══════════════════[BOOST]════════════════════────────────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ Yes I did transcribe alt text for this. My eyes hurt now.                │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════────────────────────┴───────────┴─▶
 -> file: fediverse_boost/10
◀═╦══════════════[BOOST]═══════════════──────────────────────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ Webpages should never have been allowed to execute code.                 │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧══════════════════════════──────────────────────────────┴───────────┴─▶
 -> file: fediverse/5759
═════════════════════════════════════════════════════════════════───────────────────
  @user-1655

  hence why I put everything I've ever said here into a text file on my website
  that I update every couple months:

  https://ritz-menardi.neocities.org/words/compiled.txt

  I can share the script if you want. It's very easy to configure.  It also has
  two other sources so, there's stuff on there that I've never said publicly
  anywhere else.
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════════════════════════════──────┴───────────┘
 -> file: fediverse_boost/154
◀═╦═══════════════════[BOOST]═════════════════════───────────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://floss.social/users/fast_code_r_us/statuses/113142 │ │
  ║ │ 663053255044                                                             │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧═════════════════════════════════════───────────────────┴───────────┴─▶
 -> file: fediverse/1277
═══════════════════════════════════════════─────────────────────────────────────────
  @user-913

  If you switch "Application" for "Program" it's still just as bad
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════════────────────────────────────┴───────────┘
 -> file: fediverse/307
═══════════════════════════════════════─────────────────────────────────────────────
  normalize building a library that's just a wrapper around solutions you've made
  to common problems from the past that can be imported into every project you
  work on
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧════════════════════════════────────────────────────────────┴───────────┘
 -> file: fediverse_boost/123
◀═╦═══════════════════[BOOST]════════════════════────────────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://hackers.town/users/requiem/statuses/1129355800171 │ │
  ║ │ 05874                                                                    │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧════════════════════════════════════────────────────────┴───────────┴─▶
 -> file: fediverse_boost/237
◀═╦══════════════════════[BOOST]════════════════════════─────────────────────────┐
  ║ ┌──────────────────────────────────────────────────────────────────────────┐ │
  ║ │ External post: https://fedi.rrr.sh/users/pearl/statuses/1139066556106800 │ │
  ║ │ 17                                                                       │ │
  ║ └──────────────────────────────────────────────────────────────────────────┘ │
  ╠─────────┐                                                        ┌───────────┤
  ║ similar │                     chronological                      │ different │
  ╚═════════╧═══════════════════════════════════════════─────────────┴───────────┴─▶
 -> file: messages/1053
════════════════════════════════════════════════════════════════════────────────────
  Anyway here's what i came to say:
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════════════════════════───┴───────────┘
 -> file: fediverse/2295
════════════════════════════════════════════════────────────────────────────────────
  ┌───────────────────────────────────┐
  │ CW: re: your favorite text editor │
  └───────────────────────────────────┘


  @user-1218

  can echo into a file if nothing else, though that's quite a big hassle =P
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════───────────────────────┴───────────┘
 -> file: fediverse/2084
════════════════════════════════════════════════────────────────────────────────────
  I love it when words align like this
picture of some source code which is aligned in an aesthetically pleasing way, like when every fork in the drawer is nestled together or a pile of folded clothes are placed on-top of one another rather than being a jumbled mess
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧═════════════════════════════════════───────────────────────┴───────────┘
 -> file: fediverse/614
═════════════════════════════════════════───────────────────────────────────────────
  What does your template for a new project look like? Here's mine:
39 lines of C code included in it's original form here:  #include <stdio.h> #include "pthread.h" #include "raylib.h"  void* draw(void* args){    const int screenWidth = 800;    const int screenHeight = 450;     InitWindow(screenWidth, screenHeight, "template");     SetTargetFPS(4);     while (!WindowShouldClose())    {       BeginDrawing();          ClearBackground(RAYWHITE);          /* do something */       EndDrawing();    }     CloseWindow();    return NULL; }  void* game(void* args){    /* do something */    return NULL; }  int main(void) {    void* args;     pthread_t threads[2];    pthread_create(&threads[0], NULL, draw, &args);    pthread_create(&threads[1], NULL, game, &args);    return 0; }
┌─────────┐                                                            ┌───────────┐
│ similar │                       chronological                        │ different │
╘═════════╧══════════════════════════════──────────────────────────────┴───────────┘