Clockwork UConsole CM4

i am so sick rn but the leaf site got hacked and its shit got leaked. i fear i must get up just to see the uncommented 10k lines of code. what the fuck were you all doing. is this normal in php

how did the janitors live like this

were they operating this by sacrificing virgin lines of code to the maw of source files

The 100% Good Twine SugarCube Guide!

The 100% Good Twine SugarCube Guide is a coding guide for the SugarCube format of Twine. It is meant as an alternative to the SugarCube documentation, with further explanations, interactive examples, and organised by difficulty. The goal of this guide is to make the learning curve for new SugarCube user less steep, and provide a comprehensive and wide look over the format.

VIEW / DOWNLOAD THE GUIDE!!!!

The Guide is compartmentalised in (currently) four categories:

THE BASICS or the absolute basics to start with SugarCube. No need for extra knowledge. Just the base needed to make something.

THE BASICS + adding interactivity, and creating a fully rounded IF game May require a bit of CSS knowledge (formatting rules)

INTERMEDIATE MODE adding more customisation and complex code Will probably require some CSS knowledge, and maybe some JavaScript

ADVANCE USE the most complex macros and APIs Will surely require some JavaScript/jQuery knowledge

Note: The Advanced Use includes all the APIs, macros, and methods not covered by the previous categories. This includes code requiring very advance knowledge of JavaScript/jQuery to be used properly.

Each category explains many aspects of the format, tailored to a specific level of the user. More simpler explanations and examples are available in earlier chapters, compared to the later ones.

If something is unclear, you found a mistake, you would like more examples in the guide, or would like a feature covered, let me know!

The Guide currently covers all macros (as of SugarCube v.2.37.3), all functions and methods, and APIs. It touches upon the use of HTML, CSS, JavaScript and jQuery, when relevant. It also discusses aspects of accessibility.

The Guides also provides a list of further resources, for the different coding languages.

The Guide is available in a downloadable form for offline view:

HTML file that can be opened in Twine

.tw file that can be opened in Twine

source code, separating the chapters, .js and .css files

GITHUB REPO | RAISE AN ISSUE | TWINE RESOURCES TWEEGO | TEMPLATES | CSCRIPT 2 SG GUIDE

Twine® is an “an open-source tool for telling interactive, non-linear stories” originally created by Chris Klimas maintained in several different repositories (Twinery.org). Twine is also a registered trademark of the Interactive Fiction Technology Foundation.

SugarCube is a free (gratis and libre) coding format for Twine/Twee created and maintained by TME.

VIEW / DOWNLOAD THE GUIDE!!!!

As of this release (v2.0.0), it is up to date with the version 2.37.3. If you are looking for the guide covering SugarCube 2.36.1, you can find it on my GitHub.

Note: the Guide is now complete. There won't be further substantial updates.

Ok. I am going to let you in on a secret about how to make programming projects.

You know how people write really good code? Easy to read, easy to work with, easy to understand and very efficient?

By refactoring.

The idea that you write glorious nice code straight is an insane myth that comes from thinking tutorials is how people actually code.

That is because programming is just writing. Nothing more. Same as all other writing.

The hobbit is ~95000 words.

Do you think Tolkien created the Hobbit by writing 95 thousand words?

Of course not! He wrote many many times that. Storylines that ended up scrapped or integrated in other ways, sections that got rewritten, dialog written again and again as the rest of the story happened. Background details filled in after the story had settled down

Writing. Is. Rewriting.

Coding. Is. Refactoring.

Step 1 in programming is proof of concept. Start with the most dangerous part of your project ( danger = how little experience you have with it * how critical it is for your project to work )

Get it to do... anything.

Make proof of concept code for all the most dangerous parts of the project. Ideally there is only 1 of these. If there is more than 3 then your project is too big. ( yes, this means your projects needs to be TINY )

Then write and refactor code to get a minimum viable pruduct. It should do JUUUUUST the most important critical things.

Now you have a proper codebase. Now everytime you need to expand or fix things, also refactor the code you touch in order to do this. Make it a little bit nicer and better. Write unit tests for it. The works.

After a while, the code that works perfectly and never needs to be touched is hard to read. Which does not matter because you will never read it

And the code that you need to change often is the nicest code in the codebase.

TRYING TO GUESS AHEAD OF TIME WHAT PARTS OF THE CODE WILL BE CHANGED OFTEN IS A FOOLS ERRAND.

( also, use git. Dear god use git and commit no more than 10 lines at once and write telling descriptions for each. GIT shows WHAT you did. YOU write WHY you did it )

Is this how to make your hobby project?

Yes. And also how all good software everywhere is made.

linux is just such a good special interest. it is a never ending hyperfixation; there is always a new rabbit hole to get lost in.

no matter how much i research, how much i read, i discover something new. i don't think i spent a day not learning ever since i made the switch years ago.

linux really tickles my autism in the best way.

my lungs r on fire & i am full of ire

today there is much to do, such as arrange ten functions into a menu using jframes on netbeans,,, i feel like eclipse or intellij would be better but i have very little time to explore because of how much i have to do. also being ill these past few days has been less than ideal.

i have very limited spoons and breathing is very hard. fuck my yaoi life. i'll be working on C problems because i need to understand data structures better, but my minors are also creeping up on meeeee

will reblog w a progress update by EOD.

I just love this image so much. How is anyone supporting him on patreon.

I distinctly remember ranting on tumblr about a problem in my code like half a year ago and I was frustrated with arrays of strings in c++ and I REMEMBER a furry adding a comment that just said “you could try parsing the string uwu” and I did it and it WORKED and I was so relieved because I had been fighting with it for like a week.

The only problem is I can’t find that post and I think I dreamt it up. I think God came to me in a dream as a furry responding to my tumblr post to help me fix my code. I am going insane why did my brain do this.

I think about this post every time i have some difficulties with my linux setup (basically daily)