Hacker Newsnew | past | comments | ask | show | jobs | submit | mrosethompson's commentslogin

These are generally written as k2, k6, etc. -- is there a reason why you reversed them?


Oh, good point, I might swap them. I think you're right.

I sometimes print something like "8(K P)" where I think putting the number in front makes more sense. But yeah, I think if there are no parentheses, I should just print it as you suggest.

Thank you!


OK, I've adjusted the output accordingly (https://github.com/alefore/knit/commit/b08f1d1957acf7b37c2cf...).


While your point about knitting patterns being largely unchanged by computers is true, there are a few very good software-enabled knitting tools out there:

- KnitCompanion is a complex but extremely powerful app to take PDF patterns and turn them into very efficient, effective digital patterns. You can designate specific steps, walk through steps and charts with voice control, extensively reformat a pattern, etc. I use this for all moderately complex knitting.

- TinCanKnits is a pair of pattern designers who have recently released an app for their own patterns that customizes the pattern (showing only your size, changing chart colors to match your yarn, etc.)

- CustomFit by Amy Herzog is a tool with a collection of sweater designs that can be fully customized to your own gauge, measurements, design preferences, etc.

- There are a number of calculators out there for sock knitting (how many stitches/rows for heel flap, gusset calculations, etc.).


Another HNer and I have created an app for knitting and crochet, with customisable counters, pattern import in many format, possibility to annotate, draw on pattern... as well as other knitting & crochet tools (chart creator, unit converters, glossaries, swatch adaptor...). If you want to give it a try, your feedbacks are very much welcomed, especially as you are already using an app for knitting. https://rowcounterapp.com/


This looks very nice! I'm definitely going to give it a try--thanks for mentioning it


Not necessarily. I'm not presenting this as fact, but merely as a a possible situation and counterexample to what you describe:

Your reasoning would hold if you could assume identical skill distributions between men and women graduates. However, it seems somewhere between possible and likely that women graduates are of higher average skill than the men graduating. With so many barriers and cultural impedances for a woman pursuing tech, it takes at least the same skill (to pass the classes) as their male classmates, plus enough extra competency to ward off the detractors and skeptics that men don't have to deal with.

Again, I'm not saying this is reality, I certainly don't have the statistics to back it up. But it fits my experiences pretty well, and I think your analysis probably is too simplistic to be useful.

And, in regards to your second point, about starting much earlier: I absolutely agree. The more the culture changes, the less this will be an issue.


As a possible countereffect -- not one I necessarily believe to be stronger, but one to consider -- is that women might be weaker due to the culture they're coming from. Plenty of males have been encouraged to play with computers from the age of 8 or 10, and so will have large amounts of [at least some kind of] experience coming in to the workforce. Women are far less likely to have had this experience. Additionally, males (who will have more male friends) will quite possibly have plenty of coder friends whom they have learned from. Females statistically will have less, and have less exposure this way.

i.e. the culture not only makes it harder for women to get through learning compsci, but they'll also have less exposure to it in the process. This could potentially make them weaker candidates.

I don't know to what degree that actually happens.


Not related to the concept, but your font choice seems suboptimal. Raleway's a beautiful typeface, but as small, thin gray letters on black background, there's a lot of subpixel rendering artifacts that make it really difficult to read. Example: http://i.imgur.com/Ips6rng.png?1


I also found it going very well or very, very badly.

For instance: "In most cases, before beginning to listen, the browser will ask permission to monitor your microphone."

Came out as: "In Las Cruces, f listen, permission to monitor your microphone."


I think in the future, when computers are 100 times more intelligent than they are, we'll laugh at these examples. But no one should doubt the difficulty of interpreting continuous speech without prior training for a given speaker. It's no wonder that speech interpretation on telephones tend to be limited to understanding a handful of possible responses: "Yes", "No", "Let me speak to a human!"


http://www.fishnet.in - Bookmarks with annotations. They're grouped into folders that you can make public/private to use as personal bookmarks, to assemble a portfolio, build a reading list, save your thoughts on articles, etc.

It's my first web app, built on Flask, and driven by my own need for such a tool.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: