Wordsmith

Reader

Read the latest posts from Wordsmith.

from @emsenn@wordsmith.social

Introduction

Please note any “TODO” or “TK” – that means text around it is incomplete or inaccurate, such as missing a citation.

This document is a manual of how I style my writing: construct it in a way that I think accurately and precisely communicates my ideas.

It is in early development.

License and Editorial Information

The Written Voice

This section contains a general description of the voice I try to use. By voice, I mean the mix of content and style that gives my writing its personality. I wrote every rule in this manual with the primary objective of clarifying my voice.

My tone might change depending on what I'm writing, but my voice should stay consistent.

Write Respectfully

An important part of my tone is writing respectively: making positive assumptions about the writing's subject and audience.

To treat the reader with respect:

  • I don't tell them how to feel.

To treat the subject with respect I:

  • I acknowledge people have qualities, but are not those qualities. (For details, see Describing a Person).

The Rules of Writing

The “rules” of writing are those relatively immutable standards which guide the construction of a clause or sentence. I call them rules because that's what everyone else seems to call them. Personally, I don't think they should be viewed that strictly.

Rules of Grammar

Rules of Punctuation

Rules of Spelling and the Treatment of Specific Words

  • Spelling

    • UK or US?
  • Noun Style Guide

    • Pronouns

      • Gender

        I hate that there needs to be this section but there does.

    • Proper Noun Style Guide

      • Specific Proper Noun Style Guide

        This section contains how to write specific proper nouns. It is simply a list of proper nouns that Gill and Sennhauser has found itself writing several times, so wanted to establish a precise styling for.

        | Noun | Notes | | Gill and Sennhauser | no ampersand | | Org-mode | not “Mode” | | emsenn | not captialised |

    • Collective Noun Style Guide

      | singular noun | formal collective noun(s) | comedic collective noun(s) | | congressperson | members of congress | a swamp | | yak | cabinet, herd | tangle, gridlock | | lawyer | huddle, group | tangle |

  • Verb Style Guide

    • Verb Specifications

      • “To,” not “in order to,” or “as a way to,”

      • “Also,” not “in addition”

      • remove, not extract, eliminate, take away

        I mean, unless those are what make more sense.

      • use

        Normally, you should use “use” in your sentences, unless you're speaking of something that is being used in an unusual way, then you can say utilize. But you should probably still say use.

      • method or methodology

        Usually method, unless it's not.

  • Contraction Style Guide

    For my personal tone, I should:

    • Use common contractions:
      • it's
      • you're
      • that's
      • don't

    In all writing, I should:

    • Never mix contractions and their full form in the same piece. This is bad: If you don't secure the hatch, you cannot proceed with decompression.
    • Never form contractions from a noun and verb. This is bad: the client's almost here.

    Use common contractions, such as it’s, you’re, that's, and don’t, to create a friendly, informal tone.

    Don't mix contractions and their spelled-out equivalents in UI text. For example, don’t use can’t and cannot in the same UI.

    Never form a contraction from a noun and a verb, such as emsenn’s developing a lot of new cloud services.

    Avoid ambiguous contractions, such as there’d, it’ll, and they’ll.

  • Adverb Style Guide

    • Forbidden Adverbs

      Obviously not forbidden, but, avoid them.

      | Adverb | Suggested alternative | | clearly | Drop it. If the sentence feels barren without it, maybe it's not that clear and you should rephrase. | | completely | Whatever it did, it did it. You only need to specify if it was incomplete. | | exceedingly | | | excellent | | | extremely | | | fairly | | | few | | | huge | | | interestingly | Leave it to your reader to decide if they're interested | | largely | | | literally | | | many | | | mostly | | | quite | | | relatively | | | remarkably | | | several | | | signficantly | | | substantially | | | surprisingly | | | tiny | | | various | | | vast | | | very | |

      Avoid vague adverbs:

      • clearly
      • completely
      • exceedingly
      • excellent
      • extremely
      • fairly
      • few
      • huge
      • interestingly
      • largely
      • literally
      • many
      • mostly
      • quite
      • relatively
      • remarkably
      • several
      • significantly
      • substantially
      • surprisingly
      • tiny
      • various
      • vast
      • very
  • Adjective Style Guide

    • Order of Adjectives

      • List of the Order of Adjectives

        Adjectives should occur be written in the following order:

        1. Quantity: many, seventeen, a few
        2. Opinion: interesting, good, gorgeous
        3. Size: big, narrow, tall
        4. Quality: broken, uncut, smooth
        5. Shape: square, rotund, triangular
        6. Age: 12-year-old, young, elderly
        7. Color: cerulean, green, pink
        8. Origin: English, Roman, Argentinian
        9. Material: Wood, aluminium, concrete
        10. Type: U-shaped, professional, engineer's
        11. Purpose: cleaning, camping, baking
      • Superseding Rules to the Order of Adjectives

        • If you've got something that might be a reduplicative (hocus-pocus, mama), it might be worth changing the order to give the noun phrase a better meter. The chief example of this is the big bad wolf.
        • Modifiers to an adjective should directly precede them in the phrase. This is most important for inserting a negation – that is, making sure to write, “there were several not calm individuals gathered at the gates.” /(Note “not calm” would more properly be “excited,” or a more appropriate positive adjective, but “not calm” is more suited for the piece. This demonstrates that even when you violate some rules to achieve the proper voice and tone, you don't suddenly throw out the others.)
      • Examples from Literature

        • “It was cold, bleak, biting weather,” in A Christmas Carol by Charles Dickens
        • “He's an extraordinary looking man,” in The Strange Case of Dr. Jekyll and Mr. Hyde by Robert Louis Stevenson
        • “And each separate dying ember wrought its ghost upon the floor,” in The Raven by Edgar Allan Poe
      • Examples from Our Portfolio

        Coming soon – just as soon as we have a portfolio!

    • Adjective Specifications

      • Apologise Adjective Specification

        | Adjective | Meaning | | formal | An apology given with the relevant authority of the apologizer. | | sincere | An apology issued from the individual person who is the apologizer. | | courteous | An apology issued as a social habit. |

    • Describing a Person

      • Describing a part of their identity.

        Identity Phrasing
        Member of a racially marginalized ethnicity person of color
  • Special Words Style Guide

    • Reduplicatives

      Reduplicatives are words like mama, mish-mash, or bang-bang

Rules of Writing Titles, Names, and Proper Terms

Rules of Writing Numbers and Mathematics

Rules of Abbreviations and Jargon

Rules of Quotations and Dialog

  • When using quotes “improperly”:
    • When using a specific term literally or as a strong metaphor, use “double-quotes”.
    • When using a specific term as a loose analogy, use 'single-quotes'.

Rules of Phrases and Sentence Construction

  • Phrasing Style Guide

    • Avoidable Cliches

      • not rocket science
      • isn't rocket science
      • outside the box

Rules of Colors and Sensory Descriptions

  • Use the web standard names
  • If sensation is important, treat it like clues in a mystery: provide 3.

Structuring Text

Structuring a Sentence

Structuring a List

Structuring a Paragraph

Structuring a Piece

  • Sections, chapters, parts? How to use what?

Guidelines for Determining Structure

This section contains guidelines for determining how you should structure a piece of writing, for example a short list of software dependencies the reader will need to install.

Tone

Tone is that variable element of writing which conveys the piece's attitude and intention. Word choice, sentence and paragraph structure, layout, and other attributes all factor into defining a pieces tone.

I find it most helpful to define a piece's tone with adjectives, such as formal, colloquial, or emotional. When creating a piece, I record these as properties, sorted from highest to lowest importance. That is, when two tone adjectives have contradicting rules, the one written first is the one whose rules are followed.

Adjectives

  • Authentic

  • Colloquial

  • Emotional

  • Formal

  • Natural

  • Sophisticated

Writing for Content Type

Fiction Writing

  • Mysteries

    • Always give a clue to a reader three ways, and always give the reader three clues.

Marketing Writing

  • High-End Hotel Description Writing

    The standard tone is sophisticated, natural, and authentic.

  • Online Landing Page For Service

    • Structure

      • Headline
      • Proposition
      • Exchanged utility
      • Explanation of Fulfillment
      • Social Proof
      • Closing Argument
      • CTA
  • Sales Letter

Technical Writing

  • Guide for Writing Instructions

  • Guide for Writing Training Procedures

    • Procedures should be written to the trainee: you're encouraged to use second-person voicing to give direct instructions.

Rules of Publishing

Formatting

  • PDF

  • HTML

  • Formatting by Content Type

Licensing ::

Writing Training and Exercises

About this Section

This section (is in early development and) contains instructions on training staff in how to write.

Writing Flow Training

This training (is in early development and) will teach you how to write a piece, from assignment to submission.

  • Prerequisites

    This training assumes you have completed the following trainings

  • Instructions

    This section (is in early development and) contains the individual lessons for this training.

    • Writing Flow, Lesson One: The Assignment

      This lesson (is in early development and) will teach you about assignments, the unit of work for the writing necessary to accomplish an objective. Some examples of assignments are:

      • a bundle of pieces for a client.
      • a single piece written as a bid for client.
      • a series of emails for an internal marketing campaign.

      • Assignment Properties

        Assignment properties are standardized pieces of information about an assignment. Assignment properties include things like the piece's length requirements and its tone. Assignment properties are located in three places, and are inherited on-top of each other in this order:

        • First, the assignment should have whatever properties are in the Assignment Template.
        • Second, the assignment should have whatever properties are recommended by the appropriate style guide.
        • Finally, the assignment may include its own properties.

        Here's an example of what an assignment's properties might look like:

        :PROPERTIES: :minimum-length: 700 :recommended-length: 900 :max-length: 1000 :tone: sophisticated terse :END:

Assignment Research Training

This section (is in early development and) will teach you how to conduct research for a writing assignment.

High-End Hotel Description Writing Training

This training (is in early development and) will teach you how to write descriptions for high-end hotels.

  • Prerequisites

    This training assumes you have completed the following trainings: -Writing Flow Training

  • Instructions

    • High-End Hotel Description Writing, Lesson One: Interpretting the Assignment

      This lesson (is in early development and) will teach you how to interpret an assignment.

      Assignments are kept in the Writing Assignments lesson's assignment is specifically. You may notice the assignment is brief: most assignments will include relatively few guidelines, and will rely on your training and descretion as a writer.

    • High-End Hotel Description Writing, Lesson Two: Tone and Style

      The tone for this piece should be sophisticated while remaining natural and authentic. (Remember to check the section for guidance on these terms.)

      The reader should be addressed in second-person plural, to connect them to the hotel and “travel” through the article. While it's appropriate to emphasize the luxury of a 5-star hotel, do not over-sell a 3-star hotel.

      The following should be applied over your assignment specification:

      :PROPERTIES: :tone: sophisticated natural authentic :perspective: third :address: second-person plural :END:

    • High-End Hotel Description Writing, Lesson Three: Structure

      Expert opinion (15 words exactly), in the form of a quote, given in the hotel brief. E.g. Tom Gill, London: “A contemporary hotel which provides tranquillity right in the heart of London's historical city centre.”

      We love (80 words) in a list form

      This highlights why the expert has chosen this offer, explaining what they loved about the hotel and the destination. There should be 4 or 5 ‘We Love’ points which are communicated in the hotel brief.

      Don’t hesitate to add personal touches to the points, e.g. complimentary breakfasts: give examples of what you can eat, where you can eat it.

    • High-End Hotel Description Writing, Advanced Lesson: Tom's Musings

      Think of some USPs (unique selling points) that help the hotel stand out. Maybe it's close to the beach or has a spa facility, the most important thing is drawing in the reader immediately. Don’t forget to mention the location of the establishment, the number of stars, the surrounding areas and the style/architecture of the place.

      Example: “In Saintes-Maries-de-la-Mer, where the Mediterranean Sea and the Rhône Delta meet, one can experience traditional atmosphere and spectacular surroundings. The 5-star hotel, Les Arnelles, is a charming building defined by a harmonious relationship with the great outdoors, both inside and out. Its balance of contemporary and natural aesthetics firmly roots the hotel as the standout place to stay.”

    • High-End Hotel Description Writing, Advanced Lesson: Room Descriptions

      For each room, write a title with the name of the room included and the size in brackets. Don’t hesitate to reiterate the type of person who could benefit from this room (family, couple). Describe the benefits of the room: the decoration, the surrounding area, etc.

      Mention facilities (complimentary or optional), size, view, style, who can stay (no. of adults/children, babies allowed or not).

      Example: Beach Front Villas (95 m²): “Situated directly on the beach, these villas are ideal for a trip with the whole family; up to two adults and two children can comfortably stay here. You also have direct access to the beach and swimming pool; putting paradise outside your hotel door.”

Writing Training

  • Creative Writing Training

    • Writing Prompts

      • Writing Prompt: Force a Villian on a Vacation

        You have the opportunity to take someone you dislike – fictional or real – and send then anyplace you choose – real, on earth. You have now intercepted a post card from this person sent back to their associates. What does it say?

      • Writing Prompt: You're a Disgruntled Baby

        Continue this sentence: “I know I'm only 20 months old, but I don't think it's right that my parents…“

      • Writing Prompt: You've Won!

        Continue this sentence: “When I received the letter, I almost threw it away. It looked like a scam. When I opened it, it definitely looked like a scam. No one just gives this sort of thing away. But here I am, watching the delivery crew drop off a brand new…“

      • Writing Prompt: Give Them a Condiment

        • [ ] Think of three fictional characters and write them down:

          -

        • In that order, describe each – in a complimentary manner – by comparing them to the following condiment:

          • Ketchup
          • Mayonnaise
          • Peanut Sauce
  • Training exercises

    • Word Substitution and Sentence Reconstruction Training Exercises

      • Word Substitution and Sentence Reconstruction Exercise: Write Around Character Replacements

        • [ ] Go to Wikipedia and find a random article.
        • [ ] Write 150 words about the topic. Choose your own writing type and tone.
        • [ ] In your piece, use the table below to replace characters. For each row in the column, go to whatever character position is suggested, and replace it with the suggested character. Rewrite the text to make sense around the character, replacing words or sentences as needed, while keeping the document truthful to the Wikipedia article on which it is based – and keeping the characters in the right position!

        | POSITION | CHARACTER | | 12 | e | | 88 | p | | 156 | i | | 287 | o |

      • Word Substitution and Sentence Reconstruction Exercise: Konami Code

        Like “Write Around Character Replacements”, but with the Konami Code.

    • Comparative Writing Training Exercises

      • Comparative Writing Exercise: Neither Slinky nor Scarf

        Describe a snake by writing the ways in which it is unlike a slinky and scarf, but you may not directly mention the snake, slinkies, or s

 
Read more...

from @emsenn@wordsmith.social

TODO Introduction

Please note any “TODO” or “TK” – that means text around it is incomplete or inaccurate, such as missing a citation.

This document is a manual of the procedures I use to publish my writing. It is intended to serve as a companion to my writing manual.

License & Editorial Information

This document and the source code it contains are released under the MIT License and maintained at https://git.sr.ht/~emsenn/publishing-manual, where a list of syndications is available.

Table of Contents

TODO Requirements

TODO Emacs

TODO Org-mode

TODO LaTeX

TODO Ox-Hugo

TODO Hugo

TODO Git

TODO Setup

TODO Installing Emacs and Org-Mode

TODO Installing Ox-Hugo and Hugo

TODO Installing LaTeX stuff

Rendering Methods

TODO Render as HTML

Hyper-text Markup Language, or HTML, is the document format used across the Web.

While editing your Org-mode source document in Emacs, run org-export~dispatch and

TODO Render as PDF

TODO Render as LaTeX

TODO Render as Plain-Text

TODO Render as Hugo-Compatible Markdown

Publishing Methods

TODO To Neocities (HTTPS)

TODO To DAT Protocol

TODO LBRY

TODO Wordsmith.social

TODO Tabletop.press

 
Read more...

from @emsenn@wordsmith.social

Introduction

Please note any “TODO” or “TK” – that means text around it is incomplete or inaccurate, such as missing a citation.

This document is a manual of the procedures I use to write. It is intended to serve as a prequel to my publishing manual.

License & Editorial Information

This document and the source code it contains are released under the MIT License and maintained at https://git.sr.ht/~emsenn/writing-manual, where a list of syndications is available.

Table of Contents

Requirements

Emacs

Org-mode

Setup

Installing Emacs and Org-Mode

Constructing a Document Repository

Every piece of writing I make exists in its own repository. There are a few reasons for this. On the technical front, it lets me change how any given document works, and deviate from the “standard” format as much as I want. On the publicity front, it makes it easier to promote just the pieces I want to with an audience, without necessarily exposing them to other pieces before appropriate. On the legal front, it makes it certain their license is their own, pretty safely against any “infective” licenses syndication platforms might have.

Each repository contains, when I make it, two files: the source file that I'll write in, and the README, where I explain some information about the document, useful to potential future authors or the editors.

Source File

The source file is the Org-mode file which represents the document. It's the file that you'll edit as you draft and later edit the piece, and it's what is used to generate renderings for publishing the document online and other places.

Org-mode Declarations

  • Document Metadata

    #+TITLE: {{doc.title}}
    #+DESCRIPTION: A document: an demonstration, "{{doc.title}}," by emsenn
    #+AUTHOR: emsenn
    #+DATE: 2019-01-29
    
  • Rendering Export Options

    #+OPTIONS: toc:nil ':nil num:nil
    
  • HTML Rendering Export Options

    #+HTML_HEAD: <link rel="stylesheet" href="/home/emsenn/org/projects/oats/build/oats.css">
    #+HTML_HEAD: <style>#content{width:85vw;max-width:40rem;margin:0 auto;padding:3rem 2rem 6rem;}</style>
    

Frontmatter

  • Introduction

    ```org

    • TODO Introduction /Please note any “TODO” or “TK” – that means text around it is incomplete or inaccurate, such as missing a citation./

    This document is... ```

    • License and Editorial Information

      Every document should state its license and link back to the public repository its available at, if it is. The README includes the full text of the license.

      Depending on the length and history of the document, it might be worth including another paragraph providing those details, but note that most of that information probably belongs just in the Document History section of the README.

      ** TODO License and Editorial Information
      This document and the source code it contains are released under the
      MIT License and maintained at
      [[https://git.sr.ht/~emsenn/{{doc.slug}}]], where a list of
      syndications is available.
      
  • Table of Contents

    #+TOC: headlines 1
    

A Section

* Demo Section
#+BEGIN Introduction
This section is about...
#+END

#+TOC: headlines 1 local

README

The README of a document is primarily aimed at editors, authors, and publishers, not the reading audience. (That's who the License and Editorial Information section of the source file is for.)

README Frontmatter

# "{{doc.title}}"
_A document: an essay, "{{doc.title}}," by emsenn._

Summary

The document's summary should specify what type of document it is, when it was written, and usually, what it was in response to, more than its topic. (Which is usually clear from the title and catalyst/trigger.)

**"{{doc.title}}"** is a {{doc.type}} I wrote on {{doc.date}}...

List of Renderings

After explaining what the document is about in the summary, I list all the renderings (and syndications) of the document. Since this is a fresh piece, there's only one thing to list: the source file.

- [Original Org-mode Version](./{{doc.slug}}.org)

Repository Disclosure

This repository is maintained at
[git.sr.ht/~emsenn/{{doc.slug}}](https://git.sr.ht/~emsenn/{{doc.slug}})
and mirrored on [Gitlab.com](https://gitlab.com/emsenn/{{doc.slug}}).

Author Credits

## Document Authorship
This document was written by [emsenn].

Language Disclosure

## Language
This document is written in English.

Document History

## Document History
This document was first drafted in November 2018 in response to my
experience with a small business a couple months prior.

Contribution Guidelines

## Contributing
I welcome contributions, please send a message to my [public inbox].

Financial Disclosure

## Financing
This document was written voluntarily and has no associated costs.
Donations to this project's maintainer may be made at:

- https://ko-fi.com/emsenn/
- https://en.liberapay.com/emsenn/

For more ways to contribute financially, see
[emsenn.net/contribute](https://emsenn.net/contribute).

License

## License
This document, as software, is released under the MIT License:

    Copyright 2019 emsenn

    Permission is hereby granted, free of charge, to any person
	obtaining a copy of this software and associated documentation
	files (the "Software"), to deal in the Software without
	restriction, including without limitation the rights to use,
	copy, modify, merge, publish, distribute, sublicense, and/or
	sell copies of the Software, and to permit persons to whom the
	Software is furnished to do so, subject to the following
	conditions:

    The above copyright notice and this permission notice shall be
	included in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
	EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
	OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
	NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
	HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
	WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
	FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
	OTHER DEALINGS IN THE SOFTWARE.

Credits

## Credits
- This document was written by [emsenn].
[emsenn]: https://emsenn.net
[public inbox]: https://lists.sr.ht/~emsenn/public-inbox

Drafting

Editing

 
Read more...

from @emsenn@wordsmith.social

Introduction

In this very short essay, I explain why I choose to write my name in lowercase.

License and Editorial Information

This essay is released under the MIT License, and is maintained at https://git.sr.ht/~emsenn/why-emsenn-is-lowercase.

“msenn”

When I was 12 I joined a server where everyone's name was their first initial and the first four letters of their last name. So my username was “msenn.”

“emsenn”

After a while we migrated systems and the rule was relaxed, and many original members changed their names to be more phonetic – I added an e to the start of mine, to become “emsenn.”

Because my name originated as a username, I always write it in lowercase: a nod to my “heritage.”

(And yes, everyone calls me emsenn, even in real life.)

 
Read more...

from Adriano Maini

Tornando da Aubagne.

E fu così che non ricordo quasi niente di quel viaggio di ritorno del 1983 da Aubagne. E l'alberghetto davanti al quale mi lasciarono, ormai nel cuore della notte, fu un po' come un tocco finale. A me sembra ancora adesso, per farla breve, tratto di peso da un qualche romanzo dove compare Maigret, con la differenza che io mi trovavo a Marsiglia e non a Parigi. Solita tappezzeria un po' ... trasandata, solito rubinetto che sgocciolava, solita persiana che cigolava al vento, solite voci di donne e uomini: queste cose, nonostante il ... mal di testa me le ricordo, così come mi ricordo di avere dormito ben poco.

Fu veramente comodo il viaggio di ritorno in treno, un bel treno ancora di quelli di una volta, posizionato in una vera poltrona (non ci si crederà!) tutta per me: l'unica dello scompartimento, credo, ma non me la ero certo lasciata sfuggire!

E così capita che, stando al computer posto vicino ad una vetrinetta dove é custodita una così bella bambolina, mi siano affiorati alla memoria ricordi un po' sfumati che mi hanno indotto a scrivere queste righe. Anzi, mi sembra quasi che anche la graziosa contadinella al termine di questo post intenda mandare i suoi garbati saluti a tutti!

 
Continua...

from chrischn

erklärung

ich erkläre dir meine liebe

ich erkläre dir, wie dein lächeln, dein blick in mir herzrasen erzeugen, noch immer wie am ersten tag

ich erkläre dir, wie jedes wort das du sprichst, jeder gedanke den du äußerst mir vorkommen, als hätte auch ich sie sprechen können, sie hätte denken können

ich erkläre dir, wie das gefühl von deinen lippen auf meinen, deinen händen auf meiner haut sich anfühlen, wie warme wahrheit, die in mich fließt

ich erkläre dir, wie die ängste die du verspürst mir kraft geben, dir zur seite zu stehen, wie sie meine ängste kleiner werden lassen

ich erkläre dir, wie der gedanke an dich und mich in einer zukunft diese zukunft für mich erst zum leben erwecken, erst erstrebenswert machen

ich erkläre dir, wie sogar deine zweifel mir die sicherheit geben, das es richtig ist und wahr

ich erkläre dir, wie all die schwierigkeiten und hürden, die wir zu überwinden haben mich mit leichtigkeit erfüllen und mit zuversicht

ich erkläre dir, wie ich mit eintausend worten dir niemals meine liebe erklären könnte

ich sehe dich an und ich küsse dich und erkläre dir meine liebe

#chrischn #liebe #31072013

 
Weiterlesen...

from chrischn

während ich durch den tag gehe durch mein leben gefasst und bei mir die füße fest auf dem boden

kommt in einem moment ganz unerwartet der gedanke an dich

und die tiefste sehnsucht reißt mich aus meinen gedanken reißt mich von den füßen

wie eine plötzliche windböe an den herbst erinnert erinnert es mich an den sturm den du entfacht hast in meinem leben

#chrischn #leben #liebe #11112015

 
Weiterlesen...

from chrischn

ich will nicht immer so viel wollen glauben so viel wollen zu müssen ich will dürfen und ich darf wollen warum hab ich nur immer das gefühl so viel zu sollen

ich sitze hier und denke ich verbringe meine zeit mit warten dass sie vorbei zieht ohne das ich gemusst haben würde oder gesollt

viel schwerer ist es nichts zu tun was ich nicht tu weil ich glaube dass ihr darauf wartet dass ich es selbst von mir verlang

während ich mich selbst aus meiner zeit vertreib is da immer die angst dass sie ohne mich nicht bleibt und am ende hab ich mich selbst verpasst

#chrischn #depression #leben #kapitalismus #07092016

 
Weiterlesen...

from chrischn

erinnerungen an eine vergangenheit die nie eine zukunft hatte die nichtmal eine gegenwart hat

das wird mir eine leere sein es ist die selbe leere wie schon immer

als hätte ich nichts gelernt aus all dem und wie ironisch eines besseren belehrt vielmehr allen besseren beleert

#chrischn #liebe #depression #05062017

 
Weiterlesen...

from chrischn

Ein Raum der sich langsam füllt mit Leere

ein Raum in dem es Freude gab und Angst Wahnsinn und Lust ein Raum voller Schmerz voller Hoffnung und immer voller Liebe

ein Raum in mir der sich langsam füllt mit Leere

ein Raum den du geschaffen hast

ein Raum für uns für immer

#chrischn #liebe #16102017

 
Weiterlesen...

from secstate

I discovered Nethack for the first time this weekend. Well, I knew it existed for a while, but I had always sort of poked around at it, generally unimpressed. But on Friday there was a lobste.rs post about a speedrun of nethack that totally captured my attention. The runners used the inventory at the start of a randomly generated map to determine which seed was used by the RNG to build the dungeon. From there, they had a general sense of what would work. This resulted in an ascension, as victories are called, of sub 8 minutes. The previous best on the most popular nethack server, nethack.alt.org, was more than 90 minutes. Crazy.

All that to say that reading about their speedrun made me realized how much more there was in nethack. Much more. And now I’m hooked. I also joined the IRC channel for NAO and with IRCCloud I get notifications when I’m done with a game with my final score. It’s actually kind of delightful. Now I need to stop wasting time with it :)

 
Read more...

from Robbie's Words

This week and next, I'm receiving training for Magento, a big-time e-commerse framework that allows you to create a web storefront to sell stuff. This is clearly not the correct choice for our website at work, but the shopping cart at the very least will be leaps and bounds better than what we currently have.

Anyway, I'm being trained on how to develop for Magento so I can be prepared to customize and change it however my company's managers might want or need, and as I'm doing the training, I'm finding that this, like many other big-time frameworks, is just way too over-engineered.

Look at this class namespace: Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection

Why in the world would anyone do this?? I can't even comprehend the process that could possibly have gone into architecting this structure! Who would let this happen? Who would want to work this way?

On top of that, to create a new module, the file and folder structure is so convoluted that you need training to understand how it works; there's no way to figure it out by looking at it! Here's the full sample module file structure from the first part of the training (in order of creation):

app/
  code/
    Mastering/
      SampleModule/
        registration.php
        Block/
          Hello.php
        Controller/
          Adminhtml/
            Index/
              Index.php
          Index/
            Index.php
        etc/
          module.xml
          adminhtml/
            routes.xml
          frontend/
            routes.xml
        Model/
          Item.php
          ResourceModel/
            Item.php
            Item/
              Collection.php
        Setup/
          InstallData.php
          InstallSchema.php
          UpgradeData.php
          UpgradeSchema.php
        view/
          frontend/
            layout/
              mastering_index_index.xml
            templates/
              hello.phtml

Can you believe this?? This many files and folders JUST to create a single page that spits out a tiny list of items! God help you if you didn't have training to know what any of this is for. Plus some files need to be capitalized or lower-case; everything is very specifically laid out.

Compare this to any of my own projects. If I had to accomplish the same thing, I would need 1, maybe 2, files at most to do anything similar. Here, my biggest non-work project to date is the new version of Lexiconga that I've been building:
https://github.com/Alamantus/Lexiconga/tree/master/src
If you had to walk through that code without knowing how it worked, you could actually do it if you understand the JavaScript used.

I don't understand how this happens to software projects. This is just an insane way to develop anything, and I can't comprehend how anyone could want this.

 
Read more...

from the elegant rubble

Well, I haven't posted here in over a month. So it's good know I bring the same dedication to creating original content here as I did on Tumblr.

And that month has been a MONTH, ya know?

I'm glad things are finally settling in, and the rhythms of the new year are starting to show. Don't get me wrong, for as crazy as the last month was, it was generally a very good month. But after a while it gets hard for me when each day is completely different in structure and schedule than the one before it. And being human, it's so much easier to dwell the stressful and hectic than the meaningful and restorative.

Nothing fucks with a schedule like the holidays, but it wasn't just the holidays. I took on my first copy editing freelance gig. I upped the dosage on my medication. I had an intense job interview that required preparation.

The end of the year really did feel like a time of change. The calendar was turning over, and it was time for me to do the same. I thought a lot about how I wanted the new year to be, but first I had to get there. And sometimes the waiting is the hardest part.

I grew pretty restless. Literally and figuratively. The first two weeks of higher medication dosage really screwed with my sleep. I wasn't falling asleep until 3 or 4am, and then getting up at 7 or 8. And yet I felt fine. Well, not fine. I felt like a stimulant was keeping my brain awake 20 hours of the day. But at least I wasn't sleepy?

For most of the month, the weather wasn't helping. Up until about a week ago, it felt like we were stuck in an extended autumn. I love autumn, but what I love about autumn are the moving parts. The weather cooling, the leaves changing, the days growing shorter. It felt like autumn came, did its thing and was ready to clock out, but winter never showed up to relieve her. For most of December it was just cold, gray, and dead. Being Colorado, there was also the occasional unseasonably warm day thrown in there. But a 70 degree day surrounded by bare trees and brown grass isn't just unseasonable, it's unsettling.

And yet:

The holidays were very good. I completed my copy editing project ahead of schedule. I eventually got some sleep. I still don't know if I got the job, but I did get a second interview.

In the first week or so of the new year, my restless, anxious energy was beginning to congeal into something more robust and sustainable. The world was making a little more sense, and fitting into the spaces I wanted it to.

And then my cat injured his ACL.

I didn't even know cats had ACLs. But if someone in this house was going to get a sports injury, it sure as hell wasn't going to be me. We don't know how he did it. He just showed up in the kitchen one night with a BAD limp. So we packed him up and took him to our vet (which thankfully is three blocks away and open 24 hours).

They determined that he had done something to the ACL in his back left leg. They couldn't tell if he had torn it or just aggravated it. The only way to know for sure was x-rays. But first, they recommended a week of no jumping or climbing stairs and a course of anti-inflammatories. Then, if there wasn't significant improvement, we'd take him back for x-rays.

Tycho (the cat in question) lives his life spread out over three floors. This meant he had to be sequestered, ideally with someone who could intercept any attempts to jump or climb on anything and generally keep an eye on him. Since I work from home – and since his food, water and litter are in my room already – the role of nursemaid fell to me. I didn't mind at all. I was worried about him, and having him in the same room as me all day every day made it easier to monitor his progress and hopefully assuage my apprehension.

It also turned me into the world's lightest sleeper, as any noise overnight might be Tycho needing me. Of course, the vast majority of noises each night were not Tycho. But the fragile peace I had just made with sleep was now shattered. Sigh.

Tycho didn't actually need much attention from me. He took to his isolation pretty well. That was worrying for a while. He was very low energy the first few days. I mean, he's a cat, so even at perfect health, his energy is usually channeled only into moving from one nap spot to another, but this was different. He curled up in my TV chair and didn't move all day, except for food and bathroom time, and even that was much less than usual. It took until Friday before he was interested in going on his 'rounds' in my room. He'll inspect my bookshelves, poke at Joy-Cons, sniff my laundry, attack my shoelaces, push things off my desk. Normal cat duties.

Yesterday was his first day had access to the whole house again. He didn't even notice until lunch time. But today he was back to most of his old routines. He still has a bit of a limp. It's clear that his leg is still causing some discomfort. He can't sit like a loaf very long without having to flop his hips over and stick his back legs out. We're still monitoring him, and probably will be bringing him in for a follow up soon. But he does feel like Tycho again.

Yet again, I feel like things are starting to settle down, like I might get a chance to see what 2019 is “really” going to be like. But the truth is, it will probably continue to be exactly like it already is. Exactly like 2018 was. The real question is: what will *I be like?

“Time changes everything? That's what people say. It's not true. Doing things changes things. Not doing things leaves things exactly as they were.” – House (S03E12, “One Day, One Room”)

Current Music: None, but I have the horse riding song from Breath of the Wild stuck in my head

#lifeupdate #tycho

 
Read more...

from bsmall2

Rain came last night for the first time in a while.

Water on the berries, flowers, and leaves lets you appreciate the beauty in a new way.

Berries

Rain on Berries 1

Rain on Berries 2

Flowers

Rain Drops on Sasanqua

Rain Drops on Tsubaki (Camellia Japonica)

Leaves

Norabouna Leaves

Rain Drops on Reddish Norabouna Leaf

Rain Drops on Green Norabouna Leaf

Other Green Leaves

Rain Drops on Bean Leaf with Tendril

Ruccola and Curly Leaf Mustard

Ladybug on Grean Leaf

The pictures in this post are from PixelFeed posts: – https://pixelfed.social/p/bsmall2/31489https://pixelfed.social/p/bsmall2/31491https://pixelfed.social/p/bsmall2/31498

I've been working with a Diaspora* account for over two years and it has been great. Markdown is great for on-line posts. Diaspora* is great for conversations and being “excellent to each other”. I like the minimalist, distraction free environment of WriteFreely too. And the ability to edit posts, and the default to post a Draft anonymously before going public could make WriteFreely a great tool for composition. I think Barry Lane has a book on writing that is about the importance of re-writing. Maybe I should write my Diaspora* posts here on WriteFreely, as drafts and the blog posts. After catching all the mistaken word typos and the awkward sentences, then maybe I should upload to Diaspora*... – https://ruhrspora.de/u/bsmall2

My feeling is that WriteFreely could be useful for writing or composition classes.... There could be a fediverse education program waiting to be discovered

#Garden #Raindrops #Norabouna #のらぼう菜 #MyGarden #ladybug #PixelFeed #myphoto #fediverse #Diaspora* #WriteFreely #Composition #Education #facdev

 
もっと読む…