Young Hands Club

• Collective output of software industry since win3.1 is shit
• Chumps are complicit in their loss
• Things worth reading are worth re-reading – many times!
• Time is limited – don’t waste it reading nonsense
• Doing what you want/like is fine – once you like the right things (and it takes a lot of focused work to get to that point)

I wasted a ton of time reading nonsense instead of working last week. It’s encouraging to see that I’m not alone in having to re-re-reread lots of the stuff in the logs before I grok. I’ll add the task of re-reading my past week’s publications to my weekly reviews.

I’m not at a point where I can do what I like, yet; in the meantime, I’ll do what I’m told.

The task:

3. Rent a dedicated server with one of the recommended/known-to-work OSes and install TRB on it to run a BTC node.

Splits into a tripartite problem:

(i) Rent a dedicated server

(ii) Install known-to-work OS

(iii) Install TRB

I think it makes sense to do (ii) & (iii) on a local machine first, before introducing the complexity of (i).

(i) I’d strongly prefer to rent a server from a person; it looks like Asciilifeform has a hosting service.

(ii) Gentoo, Debian, Ubuntu and CentOS are the operating systems listed as having been tested on the TRB build instructions. I tried and failed to build on Ubuntu 16.04 (iirc) a while back – I believe mod6 expected it was an issue with gcc5 (despite efforts to downgrade to gcc 4.x). I could try an older version of Ubuntu that ships with gcc 4, to get around this.

(iii) The build instructions are here. I’ve got an old laptop I can use for the local build.

1. Summarise #o logs. Comment on things I’ve learned. Review dad’s summary of log; compare with mine. Publish. (3)

2. Search Republican blogs for guides on setting up TRB. Publish plan of action. Ask questions, if necessary. (4)

3. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)

I started the week off by trying to avoid hard work. I was then set some hard work, and hardly worked on it for… 11 hours. Total. All week.

What can I change? There’s a ton of stuff I can stop doing: frittering time away on youtube/online dating/fake news/podcasts/blogs – ie. noise. I’ll keep all that shit confined to my wind-down period, so it doesn’t infiltrate the work day.

I’ll ensure I leave at least two hours for the wind-down period before bed, so sleep isn’t disturbed by work (a guy waking up mustn’t have his sleep disturbed!).

I can focus on a maximum of two or three tasks for the day; not scattershot all over the agenda.

If/when I fail to grow on a given day, I can document, publish, and learn from it.

PS. Those 11 hours spent working – while arduous – were the most enlivening I can recall in recent memory.

1. Summarise #o logs. Comment on things I’ve learned. Read, publish dad’s #o log summary, with commentary. Publish. (2)

2. Work on logger-link problem. Publish progress. 19:00 GMT. (2)

3. Search Republican blogs for guides on setting up TRB. Publish article on plan of action. Ask questions, if necessary. (2)

4. Continue translating Don Quixote into English. Publish notes. (1)

5. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)

1. Summarise #o logs. Comment on things I’ve learned. Read, publish dad’s #o log summary, with commentary. Publish. (2)

2. Write down questions regarding the logger-link problem; ask Diana for help in #o before 19:00 GMT. (2)

3. Search Republican blogs for guides on setting up TRB. Publish article on plan of action. Ask questions, if necessary. (2)

4. Start translating Don Quixote into English. Publish notes. (1)

5. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)

The problem:

The logger-link problem in a nutshell is this: get the full list of links for #trilema loglines from my old logger (there’s the full dump on my site) and then make a script (possibly some curl involved as well) to find on trilema.com the corresponding correct link for each. Match them and produce a full record, similar to the one I published for #o. And sure, read, poke at it and ask as needed for clarification.

The trilema.com logs are here, and I believe the trilema logline dump from ossasepia is this link from the Raw Logs and Archives page.

Below are the first lines from the raw logline dump:

And its corresponding trilema.com html version.

So, I think the task is to match each of those timestamped comments with its corresponding html link on trilema.com, eg. in the case of the first line:

1 1440678 2016-03-28 09:24:17 trilema 2 diana_coman f what’s the logs address for this channel? \N

needs to be matched with its corresponding Trilema.com log line:

I believe the similar record for #o logs Diana is referring to above is this one; found here; with the first line’s mapping as follows:

logs.ossasepia.com/log/ossasepia/2019-07-14#998683 ossasepia.com/2020/04/19/ossasepia-logs-for-14-Jul-2019#998683

If indeed that’s the task at hand, it seems that the index difference between the first comment from each source is 618545:

trilema.com first index: 2067223

raw logdump first index: 1448678

If that delta is constant, perhaps an awk script could be made to run through the raw logline dump, grab the date, time, author, index (adding the 618545 delta); format and output the corresponding trilema html links?

• Publicise delays immediately, along with reasons and remedy
• Feelings have no bearing on, and are often blankets over, the truth. They often block learning – via discomfort of the new; rejection of teachers’ authority/methods
• Break problems into small chunks; it’s not all-or-nothing
• “Cocaine is a hell of a drug” – Rick James
• Steady work beats intermittent frantic bursts
• “It was all in one strand!” – bad shit tends to connect to other bad shit; can’t be isolated – a sip leads to a gulp; emesis

1. Summarise #o logs. Comment on things I’ve learned. Publish. (3)

2. Write down questions regarding the logger-link problem; ask Diana for help. Publish progress so far; thoughts on possible ways to solve. (2)

3. Search Republican blogs for guides on setting up TRB. Publish article on plan of action. Ask questions, if necessary. (2)

4. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)

When falling behind, speak up; don’t run away

Publish works in progress, especially if running into problems

Post tenebras spero lucem

Growth is gradual; don’t lose heart

Silent failure is self-deception