I got through my first week of school! Yusss. So far I definitely feel old above all else. On Friday I was flanked by two young men (and by men I mean ~19 year olds) in one of my lecture classes, both texting the whole class. shakes head Oh, youngn’s.
Maybe I’m being optimistic, but I think it’s going to be a fairly easy quarter. I’m enrolled in quite a few credits (18 to be precise) but a lot of what I’m taking is pretty much review, so mostly I think it’s going to be about time management for various assignments. And time management is something I have become a pro at in the last two years.
I’m taking Calc II, which will have some new content but so far has just been stuff I know. I’m taking Chem, which I already technically have credit for, but figured I might as well take since I haven’t taken it since high school. And now that we’re getting into the content I’m finding I actually remember quite a lot of it. So mostly review. And for Bio, that is really the only class that’s going to be primarily new stuff, but nothing in the syllabus looks too scary or completely unfamiliar.
I’m also taking one of the two computer science courses that will be necessary to open up all the other classes for my major. I heard from a friend that the course would be teaching Python, so I sneakily went and starting learning Python a few weeks ago. In fact, I’ve already started writing a program! I’m currently designing my next sweater pattern, and I thought that writing up a program to do all the math would be not only a perfect way to get some Python under my belt, but to save me the headache that is designing patterns in spreadsheets.
It has been going so great. Every time I learn a new thing that will be some kind of shortcut for what I’m doing it’s like I can actually feel the lightbulb in my head going off and the gears clicking into place. I also am really liking Python. I’ve been dabling in some other languages, and so far I can see why Python has a lot of appeal for many poeple.
It is a very exciting process. And honestly, I find writing patterns this way makes a ton of sense. It all follows the same logical structure of the final pattern, and when the math isn’t coming out right it’s way easier to track down why when using variables and written out calculations than it has ever been (for me at least) to track down which C8-C16 - H8-H15 * B2 spreadsheet row calculation is doing what wrong. I’ve always dreaded needing to go back to old pattern spreadsheets after any amount of time has passed (even though I heavily comment my spreadsheets) because it’s a nightmare trying to figure out what I was doing. I feel like going back to something like this program is not really much more work than just reading over the pattern.
In short, it’s awesome.
And even though my program is verrrry very basic and there are things that I know for a fact could be done better (it’s kind of hard to figure out the best way to do something when you don’t even have the vocabulary to articulate a search for what you want to accomplish) I’m very glad I decided to jump on in with it.
It has definitely also served to make me feel very prepared in my programming class. We haven’t had a lab yet, but in the lecture there hasn’t been anything covered this week that I’m not already very comfortable with, which is a nice feeling. My biggest fear going back to school is that I would end up bumbling along like a total n00b, especially in my programming class. I am feeling really good right now because though I’m amply prepared for the course, there’s still a ton I’m going to get out of it as I go along as I’ve really only scratched the surface in my own program. I also really like having this program to work on as I’m in the class too, because it gives me a great way to contextualize new things that I’m going to be learning. Just the other day I learned that the // operator exists, which when I saw it my face actually lit up and I was like wiggling in my chair because it’s the perfect operator for a knitting program. I actually couldn’t wait to get home and put it in place of all my int(a/b) scenarios haha… Neeeerd.
It has been a little overwhelming getting back into such a structured schedule after having so much freedom to make my own in the last few years (getting up at 6:30 am has only really been a possibility for me thanks to early sunrises, if I had started in Fall I’m pretty sure I just wouldn’t have managed to get out of bed the first day.) but I’m actually really glad to be so busy. I’ve been floundering about for the last year or so without any real sense of purpose or direction, and now I have both of those things in a really big way and it’s been noticeably affecting my mood, confidence, and overall attitude.
Yaay for making good decisions, Stephanie.
Oh, la, what to say. Here’s where I am now.
I somewhat recently had some malware infect all the wordpress sites I had going. Which were my own site, my mom’s site, my step mom’s site, and my partner’s site. This happened shortly after my computer had some funky shit going on with it and my having dealt with that whole mess (Coincidence? Well yeah, probably just a coincidence. But no doubt spurred by my lack of taking serious measures to protect these kinds of things.) When I reset my computer I backed up almost all my files, but I did not backup my Xampp directory. I originally intended to back it up, but my external hard drive was full and I figured, “Well, those files are all online so I’ll just back them up from there once my computer is reset.” I did not get around to this before the malware nonsense happened. I was able to salvage the databases, and I have all of the images/content from all the sites in my other files. It’s just the whole wordpress file structure was wiped out to the point that it would have taken forever to get it back in order.
Before any of that even happened, I was already pretty bored/fed up with using wordpress because it was such a pain to keep updated when I wasn’t using it all the time. I took this all as a sign and an opportunity to start fresh and simplify a lot of things. I wasn’t even all that stressed out about it. It was just like, “Ah. Okay, so that just happened. Time to move on I guess.”
I decided that most of those websites didn’t really need to be on wordpress anwyay, or any kind of content management system at all. I think when I set them all up originally, I had this romantic notion that by putting them on wordpress I would enable the people who I was making them for to make some simple updates down the road. But my step mom and partner are both Ludites when it comes to computers, and of course they’re not going to learn any kinds of anything to do with wordpress. Then I thought, since I’m going to be the one forever updating their sites for them, why not make them super simple one page websites. I know HTML and CSS and all that crap, so why am I adding all this complicated database stuff to websites that are 1)rarely going to be updated and 2) when they are updated, the update consists of adding maybe a few portfolio images? No reason to deal with all that mess, so bam, simplified. Small. Fast. Easy. Yessss.
My mom is way more with it, and she was working out the wordpress thing just fine. But after getting her website totally up and running and ready to go, something got fucked up and wordpress stopped finding the database and I was just ooooveeerrr iiiiitttt. I had such wonderful experiences with the other websites that I decided to go ahead and do the same thing for her. I’m not sure if she’s really all that into it yet, because I think she was probably getting into the swing of things with wordpress (after I had talked her out of using Wix or Weebly or whatever she had originally wanted to use) and here I am emailing her html files. But I figure it’s a good trade off, because it will be so quick and easy for me to help her get it fixed up if she tells me what she wants.
Now for my own site, I had at least had something to put up while deciding what direction I wanted to go in because I had made a very simple portfolio site about a year ago, which was the original site for this domain. It was an alternative to my blog website, Un Petit Squab, and my then project website, 100 Baby Sweater Patterns, that I could point people to to get an idea of what I was all about. Eventually I had replaced this website with a wordpress site that was pretty much a combination of all three of those things, and that was just fine and dandy for a good while. I had all those files still on my computer from this simple portfolio website, so I just uploaded that as a place holder while I decided what to do about my crashed wordpress enterprise.
Sometime either before the malware deal or shortly after I found out about Jekyll. When I started reading the page it was like it was written in an alien language. I barely knew what github was (confession: still barely understand it, but I’m sure that in about six months from now I’m going to look back at myself and laugh at my pitiful ignorance) and while I feel like I’m pretty savvy about a lot of web development stuff, it just wasn’t making sense to me. What I did understand, though, was that this was some kind of bare bones content management system, and it was very intriguing. I couldn’t stop thinking about it and going back to see if I could figure out what was going on.
I wasn’t sure if I wanted to even deal with having a blog anymore, because I hadn’t blogged in over a year when my site crashed. I thought maybe I should just make a better portfolio type website, and I was thinking about a lot of different ways to do that. I kept going back to jekyll, reading a little here and there before thinking, “nope, still have no idea what this is”. Then about a week ago I decided to settle in and figure that shit out, and to design my damn website already.
Jekyll is definitely one of those things that’s way easier to understand if you just dive in and start doing it. (As, I imagine, github will be.) All of the sudden it just clicked, and oh my god I freaking love it. It’s totally up my ally. Such a stripped down way to do things! Everything just text files, everything so organized. I suddenly became inspired to revive my blog. I can write blog posts without having to deal with crappy TinyMCE, don’t have to sign into some slow loading wordpress site to do it, don’t have to sign into ANY slow loading website to do it… this is just like, writing in a text editor diary! SO SIMPLE.
But of course, now that I’d decided I want to give blogging another shot, I didn’t want to just abandon all my old blog posts. Unfortunately, since none of my shit besides the database was backed up, the only way I had access to most of those old blog posts was in one giant XML file.
So that was fun.
I pretty much went through each blog post by hand, put it in a very handy HTML to Markdown converter, (I really like the markdown format for blog posts–it makes so much sense!), saved it with the properly formatted filename, and after three days, voila! Lovely blog posts, easy to back up, all in simple markdown text files. SO BEAUTIFUL. With a few typos fixed here and there and a few embarrassing moments edited out to boot. (But only a very few, there is still plenty of embarrassment to be had reading over some old posts.)
Albeit a slow process, it was a really good experience. It forced me to actually read over my whole blogging past. It made me realize a lot of things about myself, and recognize a lot of patterns. Like–I am really, really good at trying out new things and getting really excited about new ideas, only to do them maybe once or twice, and then abandon them forever. I also used to be really good at writing a lot of posts talking about how “it’s been so long since I last blogged! I swear I’m going to do it more!” Only to not blog for another month and do the same thing. Like anyone fucking cares! Thankfully I eventually realized that it was stupid to do that kind of thing and stopped, but man, in the early days.
I didn’t import most of my posts from 100 Baby Sweater Patterns, because most of those posts were posts about the individual patterns, which is all info that can be found on ravelry, serves a purpose there, and has no real need to be repeated here. Or generic ass “five faves!” or “resource roundup!” nonsense posts. I mean, whatever, they made sense at the time, and they make sense for a lot of blogs, but it makes no sense to import that kind of thing to a website where it has no context that is now a lot more personal. It would just be a total waste of time importing all that crap. The only thing I brought over from that website were the tutorials, because I still think they’re probably useful to anyone who might stumble upon them.
Another thing I realized in reading over all my own posts was how, pretty much over the course of my entire blog spanning all the way back to 2008, the tone on my blog is sooooo bad. And by bad I mean just phony as hell. It’s kind of hard to read. I get why I always wrote that way, it’s because I have a lot of fairly conservative and older family members, and I did a lot of blogging with the idea that it would be a way to share what I was doing with my family. I did a lot of cross posting on facebook, and I did a lot of self-tone-policing based on the assumption that most of my readers were going to be my grandmas.
Now that I’m blogging again, I kind of have it in my mind that I’m going to be a bit more casual about it (like in the early days) and I’m not going to be throwing any more “oh my goodness!”es into my posts ever again. (I mean what the hell is that. What is that.) I don’t really have an idea of what direction I’d like the blog to go in at this point. I’m not trying to do it in any kind of professional or entrepreneurial manner. I kind of like the idea of continuing to post crafty things. I’m getting into computer programming more and more now, so I’d like to start writing about that, too. I also really like being able to photo dump on my blog whenever I’m feeling more photographer-y. I kind of just like the idea of journaling and writing about the things I’m doing as I’m doing them, posting projects that I’m excited about, and not feeling very pressured about anything in particular or feel like I have to be particularly organized about the whole thing. I like the idea of having it as a form of self expression again. (Maybe I should archive all of my old livejournal posts on here, guys! Then you can really see me embarass myself. Like, reeeeally. I started that shit in middle school and I didn’t stop until about 3 years ago.)
I mean, realistically, the most likely scenario is that this will be the last blog post I’ll get out of me until 2016, given my track record, so all of this is kind of a moot point.
So here’s to new horizons. I’m starting school again in 2 weeks. I just ordered some yarn for my next sweater pattern. I have a lot of vague ideas of projects I’d like to start in the next year or two related to both knitting and programming. Here goes nothing.
I have published three Tunisian crochet patterns. Two of these feature the Tunisian Knit Stitch as opposed to Tunisian Simple Stitch. There are several wonderful tutorials already in existence for Tunisian simple stitch, but I thought I’d go ahead and make this quickie for the knit stitch (which is very similar, but still just a little special.) In addition to Tunisian Knit Stitch, I’m gonna show you how to do what I like to call “TKS2Tog,” which is a very simple decrease you can do on the forward pass. It’s pretty intuitive, but because I don’t think the abbreviation exists outside of my patterns, I thought I’d go ahead and cover the technique here.
How to do the Tunisian Knit Stitch
It’s really easy. All you need to do is take your hook (by the way, you should be using a long, Tunisian hook… you can sometimes get away with using a regular hook, as long as it doesn’t get too wide at the thumb grasp to move your stitches over, but a longer hook makes it easier to make bigger pieces) and insert it in through the middle of the stitches towards the back of the work on your forward pass.
Then pull up a loop.
You do this into every stitch across to the end. On the very last stitch, you pretty much just do a Tunisian simple stitch because going “through” the stitch ends up being going under the bar anyway.
TKS2Tog (How to Decrease in Tunisian Knit Stitch)
The only thing you have to do to decrease is to go into two stitches before drawing up a loop. However, it’s impossible to go through the first stitch to the back and then go through the second. So on the first stitch, you just go under the bar (as with Tss) and then you go through the next stitch to the back.
Then you draw your loop up through both of those stitches, creating a single loop out of two. Tada!
The Return Pass
This is just to remind you that on the return pass, you draw your first loop up through only one stitch…
And then you draw loops up two stitches at a time until you get to the end.
It’s also important to remember (for stitch counts and such) that the last loop on your hook after the return pass always counts as your first stitch for the next row.
A few more helpful hints (especially if you’re using my patterns.)
On Chaining at the Beginning
I’ve seen some websites say that you should chain 1 at the beginning of each row. This is lies. If you chain one at the beginning, you will have a really wonky right edge to your work. The edges in in Tunisian knit stitch tend to be wonky anyway, but they’ll be a total mess if you add all that extra chaining.
Other ways to Decrease (specifically at the beginning & end of rows)
In my patterns I also have you decrease at the beginning of rows by working slip stitches–you just insert your hook the same way as you would to create a TKS stitch, but you pull the loop all the way through to slip it.
You can also decrease multiple stitches at the end of a row by simply not completing your forward pass–just leave however many stitches you want left at the end, then work your return pass.
Working decreases like this at the beginning & end is similar to binding off stitches in knitting, or just slip/not working stitches in crochet. It’s really handy for underarm shaping, or for any time you need to abruptly lose a bunch of stitches.
And that’s it, a fairly straightforward technique that creates a very sturdy, knit-like fabric using a crochet hook. Huzzah!
I wrote a guest post over on one of my favorite blogs, How to Hair Girl. Go check it out for some sweet hair tutorial action.
More hair news coming soon.
I have published several patterns that utilize sewn bind off around the neckline. While probably best known for it’s use in binding off sock cuffs, this bind off method is also a very handy one to know for baby sweaters. Babies, of course, have gigantic heads in comparison to the size of their necks, which presents some unique design challenges. While most baby sweater designs (both in the hand knitting world as well as in manufactured baby clothes) handle this fact by way of simply being cardigans or utilizing buttons or other fasteners on the shoulder, raglan edge, or back. Another way to handle it is to simply have a slightly wider neckline that is also nice and stretchy.
This is a nice way to work around the big head situation because in the long run it makes baby easier to dress (no buttons to fuss with), cuts down on any worry one might have of choking hazards, and makes for sweaters that don’t fall back on the traditional “button on the shoulder” design. Not to mention it means you don’t have to fuss with knitting button holes. All in all, a pretty good way to go.
It’s a really easy technique to learn and memorize, so if you haven’t tried it out before here are the simple step by step instructions.
Sewn Bind Off Tutorial
Cut your yarn tail 3x longer than the knitting to be bound off, + a little extra
Insert your yarn needle into the next two stitches purlwise
And pull the yarn tail through until it is snug, but not too tight.
Insert your yarn needle into the next stitch knitwise…
And pop it off the knitting needle.
Repeat from Step Two
until all but the last stitch have been bound off. Then simply pop this last stitch off knitwise.
You’ll have a nice, stretchy bound off edge. PS: You don’t have to work this on a ribbed edge. It works great on stockinette, garter, whatever. It’s important to tug your yarn snug on each “purl through” for a consistent, non lumpy edge.
And that’s it! A mantra to remember the steps is, “Purl through two, knit off one.” If you can remember that, you can remember this bind off.
I probably won’t totally be turning my back on button closures because, lets face it: they’re super cute. But using sewn bind off to create nice stretchy necks does open up a lot of great baby design possibilities. (Not to mention it’s a super useful technique to have in your pocket.)
subscribe via RSS