1. Redo Wells post; learn how to use html img tags properly (3)
2. Full Ossasepia log summaries (not highlights). Read English prose style references (4)
3. Publish weekly review (2)
4. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed. (1)
1. Redo Wells post; learn how to use html img tags properly (3)
2. Full Ossasepia log summaries (not highlights). Read English prose style references (4)
3. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed. (1)
1. Redo Wells post; learn how to use html img tags properly (3)
2. Full Ossasepia log summaries (not highlights). Read English prose style references (4)
3. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed. (1)
Some pics from a recent trip to Wells – starting off with a typically grey English lunchtime:
I’ve taken a liking to cider, recently (and to a certain cider drinker, though that’s another story!) – one wonders if the tor cider company’s apples are as full of holes as the protocol…
We could hear music lessons over on the left hand side – sounded like a bassoon and saxaphone.
Yours truly:
“Let nothing perish” – clock dates from the 14th century, apparently!
They wouldn’t let us inside the Cathedral, on account of not being muzzled. Fuck ’em.
Not seen: Thai street food, that was far too delicious and far too greasy to photograph.
This looks like exactly what I’m after. I should’ve engaged with these guys while YH was open, and started building relationships with people. Still – no time like the present! There’s value beyond the training/software/hardware: interacting with cool people.
A couple of hardware-related questions: it’s not clear to me whether the issue of Intel CPUs all being shit is resolved;
1. Publish JWRD post with questions/thoughts prior to speaking with Dorion in afternoon. Ask Dorion questions. (1)
2. Publish post on last week’s Wells trip (1.5)
3. Reread last week’s summary & last week’s posts. Post comments. (1.5)
4. Full Ossasepia log summaries (not highlights). (3)
5. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed. (1)
1. Read JWRD sales article twice. Publish post with questions/thoughts prior to speaking with Dorion in evening. Ask Dorion questions. (4)
2. Publish post on last week’s Wells trip (1.5)
3. Reread last week’s summary & last week’s posts. Post comments. (1.5)
4. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)
Somehow managed to do less work than last week – 9 hours vs 11. Bleurgh. I went AWOL on Tuesday, maybe partly for reasons of ego defence after Diana pointed out my superficial habit of doing whatever’s easiest when it comes to work. I was blind to my fault, and I’m grateful she pointed it out. How best to show that gratitude? Change.
Rather than running/hiding from the issue, I need to fix it. Replace “what’s the least amount of work I can do to solve this problem?” with “what’s the best job I can do?”; “how can I grow the most while doing this?”
I’ve been focusing solely on the solution, without realising that the process of solving is where the learning/growth happens.
I’ve also been thinking about my relationship with Diana: what I want it to be; what I can do to make it so. I want mentorship, pointing out of my blindspots; meaning flowing from a structure of authority – to work on what matters, so I matter too.
What can I do to achieve this sort of relationship? The YH project has shut; things aren’t as they were before, but the Pageboy’s Pledge still looks like good practice:
I ask for help to expose and correct my mistakes so that I can learn from them and grow to be a better person.
I commit to my own improvement through training as directed by my Master.
I practice at all times unflinching honesty towards myself, my peers, my betters and my Master.
I open myself up to take in fully and make the most of my Master’s feedback whenever gifted and in any form given.
I submit to my Master’s judgement at all times.
Along with a line from the YH homepage:
The focus is on killing stupidity on sight, not on protecting egos, feelings, inner idjits and other unhelpful constructions.
I can work hard, change (not run!) in response to Diana’s feedback, and grow into the best possible version of myself.
I’ll keep doing all the lifestyle fixes from last week’s review.
1. Summarise #o logs. Comment on things I’ve learned. Publish. (3)
2. Translate Don Quixote. Publish work; thoughts so far. (2)
3. Review today’s agenda; publish tomorrow’s agenda. Have this done at least 2 hours before bed (1)
Have a friend visiting 22-23, so agenda curtailed.
I wanted some help with style when it comes to summarising the ossasepia logs, so asked my dad – an English teacher who’s done some editing work – to have a go:
Diana asked whether S wanted to make an account on his platform to add her feedback. Why not post it all to younghands.club and use his tags there? He could drop the text-in-paste approach: simpler to just write it, as she could read many paragraphs.. As the selection thing meant few changes in his ‘theme’, she was puzzled, for the original post was clearly explained, step by step.
S replied that using the github like ‘issues’ as a comment system would facilitate line selection, comments, project tracking, etc, at the cost of making an account, and it would not be on github. Following the steps on two themes in the original article didn’t work. He thought the git based approach would enhance discussions, but still simple and text based, just pushing files, which she’d see, with more functional searching.
D answered that the imagined gain was unreal if at another’s expense. Did he just like experimenting? With anytrhing not working he should check his setup limitations and alleged ‘improvements’ – No more over-optimizing nor website-juggling, or she’d banish it, and comment/read ONLY from younghands.club.
S conceded, admitting that she and the others knew better, and now finding that the files have to be Text for git to parse/enable; markdown and org files are parsed into html, so his ideas wouldn’t work as hoped. He promised to revert to the old, safe practice.
He explained his ‘e’ as analogous to its use in maths notation+reasoning: example N1’s value V1! = N2’s V1, but both use action a1 to reach V.
D argued that there is no such * condition *: V1 and V2 being different evaluations, by different agents, of the same action – with perhaps different results.
S agreed, but what did ‘herps derps’ mean?
She said ‘herp derp’, as verb or noun, was a…term of art. He should log search. The Urban dictionary meaning was doing something dopey.
Kakobrekla turned out rogue, but the groups s1 and s2 each proudly spouted self-deluded rubbish. Shades of meaning make human languages fuzzy, particularly with slang and neologisms.
Diana asked whether he and the trilema group could hack into any computer they chose.
I like the concision – not repeating “s/he said…” when it’s the same person speaking, as well as the more natural narrative style. My attempt is a lot more wordy/clunky. I’ll attempt to emulate the smoother flow in my next summary.
There’s an error on the final line: Shrysr asked Diana about hacking; not the other way round – seems summarisers are prone to error!
Work on what matters, so you matter too.