Reading List
The most recent articles from a list of feeds I subscribe to.
Making crochet cacti
I noticed some tech bloggers I follow have been making April Cools Day posts about topics they don’t normally write about (like decaf or microscopes). The goal isn’t to trick anyone, just to write about something different for a day.
I thought those posts were fun so here is a post with some notes on learning to crochet tiny cacti.
first, the cacti
I’ve been trying to do some non-computer hobbies, without putting a lot of pressure on myself to be “good” at them. Here are some cacti I crocheted:
They are a little wonky and I like them.
a couple of other critters
Here are a couple of other things I made: an elephant, an orange guy, a much earlier attempt at a cactus, and an in-progress cactus
Some of these are also pretty wonky, but sometimes it adds to the charm: for example the elephant’s head is attached at an angle which was not on purpose but I think adds to the effect. (orange guy pattern, elephant pattern)
I haven’t really been making clothing: I like working in a pretty chaotic way and I think you need to be a lot more careful when you make clothing so that it will actually fit.
the first project: a mouse
The first project I made was this little mouse. It took me a few hours (maybe 3 hours?) and I made a lot of mistakes and it definitely was not as cute as it was in the pictures in the pattern, but it was still good! I can’t find a picture right now though.
buying patterns is great
Originally I started out using free patterns, but I found some cacti patterns I really liked in an ebook called Knotmonsters: Cactus Gardens Edition, so I bought it.
I like the patterns in that book and also buying patterns seems like a nice way to support people who are making fun patterns. I found this guide to designing your own patterns through searching on Ravelry and it seems like a lot of work! Maybe I will do it one day but for now I appreciate the work of other people who make the patterns.
modifying patterns chaotically is great too
I’ve been modifying all of the patterns I make in a somewhat chaotic way, often just because I made a mistake somewhere along the way and then decide to move forward and change the pattern to adjust for the mistake instead of undoing my work. Some of of the changes I’ve made are:
- remove rows
- put fewer stitches in a row
- use a different stitch
This doesn’t always work but often it works well enough, and I think all of the mistakes help me learn.
no safety eyes
A lot of the patterns I’ve been seeing for animals suggest using “safety eyes” (plastic eyes). I didn’t really feel like buying those , so I’ve been embroidering eyes on instead. “Embroidering” might not be accurate, really I just sew some black yarn on in a haphazard way and hope it doesn’t come out looking too weird.
My crochet kit came with a big plastic yarn needle that I’ve been using to embroider and also
no stitch markers
My crochet kit came with some plastic “stitch markers” which you can use to figure out where the beginning of your row is, so you know when you’re done. I’ve been finding it easier to just use a short piece of scrap yarn instead.
on dealing with all the counting
In crochet there is a LOT of counting. Like “single crochet 3 times, then double crochet 1 time, then repeat that 6 times”. I find it hard to do that accurately without making mistakes, and all of the counting is not that fun! A few things that have helped:
- go back and look at my stitches to see what I did (“have I done 1 single crochet, or 2?”). I’m not actually very good at doing this, but I find it easier to see my stitches with wool/cotton yarn than with acrylic yarn for some reason.
- count how many stitches in total I’ve done since the last row, and make sure it seems approximately right (“well, I’m supposed to have 20 stitches and I have 19, that’s pretty close!”). Then I’ll maybe just add an extra stitch in the wrong place to adjust, or maybe just leave it the way it is.
notes on yarn
So far I’ve tried three kinds of yarn: merino (for the elephant), cotton (for the cacti), and acrylic (for the orange dude). I still don’t know which one I like best, but since I’m doing small projects it feels like the right move is still to just buy small amounts of yarn and experiment. I think I like the cotton and merino more than the acrylic.
For the cacti I used Ricorumi cotton yarn, which comes in tiny balls (which is good for me because if I don’t end up liking it, I don’t have a lot of extra!) and in a lot of different colours.
There are a lot of yarn weights (lace! sock! sport! DK! worsted! bulky! and more!). I don’t really underestand them yet but I think so far I’ve been mostly using DK and worsted yarn.
hook size? who knows!
I’ve mostly been using a 3.5mm hook, probably because I read a tutorial that said to use a 3.5mm hook. It seems to work fine! I used a larger hook size when making a hat, and that also worked.
I still don’t really know how to choose hook sizes but that doesn’t seem to have a lot of consequences when making cacti.
every stitch I’ve learned
I think I’ve probably only learned how to do 5 things in crochet so far:
- magic ring (mr)
- single crochet (sc)
- half double crochet (hdc)
- front post half double crochet (fphdc)
- double crochet (dc)
- back loops only/front loops only (flo/blo)
- increase/decrease
The way I’ve been approaching learning new crochet stitches is:
- find a pattern I want to make
- start it without reviewing it very much at all
- when I get to a stitch I don’t know, watch youtube videos
- don’t watch it very carefully and get it wrong
- eventually realize that it doesn’t look right at all, rewatch the video, and continue
I’ve been using Sarah Maker’s pages a lot, except for the magic ring where I used this 3-minute youtube video.
The magic ring took me a very long time to learn to do correctly, I didn’t pay attention very closely to the 3-minute youtube video so I did it wrong in maybe 4 projects before I figured out how to do it right.
every single thing I’ve bought
So far I’ve only needed:
- a crochet kit (which I got as a gift). it came with yarn, a bunch of crochet needles in different sizes, big sewing needles, and some other things I haven’t needed yet.
- some Ricorumi cotton (for the cacti)
- 1 ball of gray yarn (for the elephant)
I’ve been trying to not buy too much stuff, because I never know if I’ll get bored with a new hobby, and if I get bored it’s annoying to have a bunch of stuff lying around. Some examples of things I’ve avoided buying so far:
- Instead of buying polyester fiberfill, to fill all of the critters I’ve just been cutting up an old sweater I have that was falling apart.
- I’ve been embroidering the eyes instead of buying safety eyes
Everything I have right now fits in a the box the crochet kit came in (which is about the size of a large shoebox), and my plan is to keep it that way for a while.
that’s all!
Mainly what I like about crochet so far is that:
- it’s a way to not be on the computer, and you can chat with people while doing it
- you can do it without buying too much stuff, it’s pretty compact
- I end up with cacti in our living room which is great (I also have a bunch of real succulents, so they go with those)
- it seems extremely forgiving of mistakes and experimentation
There are definitely still a lot of things I’m doing “wrong” but it’s fun to learn through trial and error.
Introducing ChatMimi: The Xe Iaso Cinematic Universe (XICU) Chatbot
New CODE100 challenge: #BuntStattBraun
liblzma and xz version 5.6.0 and 5.6.1 are vulnerable to arbitrary code execution compromise
Some Git poll results
A new thing I’ve been trying while writing this Git zine is doing a bunch of polls on Mastodon to learn about:
- which git commands/workflows people use (like “do you use merge or rebase more?” or “do you put your current git branch in your shell prompt?”)
- what kinds of problems people run into with git (like “have you lost work because of a git problem in the last year or two?”)
- which terminology people find confusing (like “how confident do you feel that you know what HEAD means in git?”)
- how people think about various git concepts (“how do you think about git branches?”)
- in what ways my usage of git is “normal” and in what ways it’s “weird”. Where am I pretty similar to the majority of people, and where am I different?
It’s been a lot of fun and some of the results have been surprising to me, so here are some of the results. I’m partly just posting these so that I can have them all in one place for myself to refer to, but maybe some of you will find them interesting too.
these polls are highly unscientific
Polls on social media that I thought about for approximately 45 seconds before posting are not the most rigorous way of doing user research, so I’m pretty cautious about drawing conclusions from them. Potential problems include: I phrased the poll badly, the set of possible responses aren’t chosen very carefully, some of the poll responses I just picked because I thought they were funny, and the set of people who follow me on Mastodon is not representative of all git users.
But here are a couple of examples of why I still find these poll results useful:
- The first poll is “what’s your approach to merge commits and rebase in git”? 600 people (30% of responders) replied “I usually use merge, rarely/never rebase”. It’s helpful for me to know that there are a lot of people out there who rarely/never use rebase, because I use rebase all the time – it’s a good reminder that my experiences isn’t necessarily representative.
- For the poll “how confident do you feel that you know what HEAD means in
git?”, 14% of people replied “literally no idea”. That tells me to be careful
about assuming that people know what
HEADmeans in my writing.
where to read more
If you want to read more about any given poll, you can click at the date at the bottom – there’s usually a bunch of interesting follow-up discussion.
Also this post has a lot of CSS so it might not work well in a feed reader.
Now! Here are the polls! I’m mostly just going to post the results without commenting on them.
merge and rebase
poll: what's your approach to merge commits and rebase in git?
merge conflicts
poll: if you use git, how often do you deal with nontrivial merge conflicts? (like where 2 people were really editing the same code at the same time and you need to take time to think about how to reconcile the edits)
another merge conflict poll:
have you ever seen a bug in production caused by an incorrect merge conflict resolution? I've heard about this as a reason to prefer merges over rebase (because it makes the merge conflict resolution easier to audit) and I'm curious about how common it is
I thought it was interesting in the next one that “edit the weird text file by hand” was most people’s preference:
poll: when you have a merge conflict, how do you prefer to handle it?
merge conflict follow up: if you prefer to edit the weird text file by hand instead of using a dedicated merge conflict tool, why is that?
poll: did you know that in a git merge conflict, the order of the code is different when you do a merge/rebase?
merge:
<<<<<<< HEAD
YOUR CODE
=======
OTHER BRANCH'S CODE
>>>>>>> c694cf8aabe
rebase:
<<<<<<< HEAD
OTHER BRANCH'S CODE
=======
YOUR CODE
>>>>>>> d945752 (your commit message)
(where "YOUR CODE" is the code from the branch you were on when you ran `git merge` or `git rebase`)
git pull
poll: do you prefer `git fetch` or `git pull`?
(no lectures about why you think `git pull` is bad please but if you use both I'd be curious to hear in what cases you use fetch!)
commits
[poll] how do you think of a git commit?
(sorry, you can't pick “it’s all 3”, I'm curious about which one feels most true to you)
branches
poll: how do you think about git branches? (I'll put an image in a reply with pictures for the 3 options)
as with all of these polls obviously all 3 are valid, I'm curious which one feels the most true to you
git environment
poll: do you put your current git branch in your shell prompt?
poll: do you use git on the command line or in a GUI?
(you can pick more than one option if it’s a mix of both, sorry magit users I didn't have space for you in this poll)
losing work
poll: have you lost work because of a git problem in the last year or two? (it counts even if it was "your fault" :))
meaning of various git terms
These polls gave me the impression that for a lot of git terms (fast-forward, reference, HEAD), there are a lot of git users who have “literally no idea” what they mean. That makes me want to be careful about using and defining those terms.
poll: how confident do you feel that you know what HEAD means in git?
another poll: how do you think of HEAD in git?
poll: when you see this message in `git status`:
”Your branch is up to date with 'origin/main’.”
do you know that your branch may not actually be up to date with the `main` branch on the remote?
poll: how confident do you feel that you know what the term "fast-forward" means in git, for example in this error message:
`! [rejected] main -> main (non-fast-forward)`
or this one:
fatal: Not possible to fast-forward, aborting.
(I promise this is not a trick question, I'm just writing a blog post about git terminology and I'm trying to gauge how people feel about various core git terms)
poll: how confident do you feel that you know what a "ref" or "reference" is in git? (“ref” and “reference” are the same thing)
for example in this error message (from `git push`)
error: failed to push some refs to 'github.com:jvns/int-exposed'
or this one: (from `git switch mybranch`)
fatal: invalid reference: mybranch
another git terminology poll: how confident do you feel that you know what a git commit is?
(not a trick question, I'm mostly curious how this one relates to people's reported confidence about more "advanced" terms like reference/fast-forward/HEAD)
poll: in git, do you think of "detached HEAD state" and "not having any branch checked out" as being the same thing?
poll: how confident do you feel that you know what the term "current branch" means in git?
(deleted & reposted to clarify that I'm asking about the meaning of the term)
other version control systems
I occasionally hear “SVN was better than git!” but this “svn vs git” poll makes me think that’s a minority opinion. I’m much more cautious about concluding anything from the hg-vs-git poll but it does seem like some people prefer git and some people prefer Mercurial.
poll 2: if you've used both svn and git, which do you prefer?
(no replies please, i have already read 300 comments about git vs other version control systems today and they were great but i can't read more)
gonna do a short thread of git vs other version control systems polls just to get an overall vibe
poll 1: if you've used both hg and git, which do you prefer?
(no replies please though, i have already read 300 comments about git vs other version control systems today and i can't read more)
that’s all!
It’s been very fun to run all of these polls and I’ve learned a lot about how people use and think about git.