That Manifesto Thing

Someone at work last week pointed out the whole Google Manifesto shenanigan over the previous weekend. As a woman in tech, this is something I hear about all the time, but I’m too busy to give them the time of my day. I try to be a positive person, so instead of dwelling on all the lame comments that peppered social media, I’m just going to focus on those who have rebutted the manifesto with much better articulation that I could ever have.

A Brief History of Women in Computing: What I love about this article is that it pointed out exactly what the biggest problem was in the Google Manfiesto. The manifesto presented several biological research and used it to try to justify why women could be less suited for computing. However, as this article points out, the jump was too big. The biological components pointed out may explain certain traits, but not how those traits exactly cause an interest (or lack thereof) in computing specifically. As it is, the manifesto (and yes I read it) to me sounded like it was motivated by the author’s deeply held stereotypes about women and tried to back up his beliefs retroactively. Additionally, the manifesto does not address how modern computing environments were shaped by men and optimized for their own behaviour. Because let’s face it: a profession’s environment affects its workers, while workers in turn affect the environment. The relationship is symbiotic. Several of the manifesto’s points pertain more to computing environments rather than the actual task. For example, it said that computing is a high-stress profession requiring less empathy and social interactivity. Is it possible that women, with their different biology, could thrive in a different, yet equally productive, computing environment? I don’t know, and I think it would be more productive to conduct research on it than to rely on stereotypes to make leaps in conclusion.

So, About this Googler’s Manifesto: What I like about this article is his explanation about how engineering isn’t an isolated endeavour. This was a misconception I had when I was younger, and it’s actually something that attracted me to the field, because I like doing solo work. I’ve grown out of that misconception though, and I love computer science enough to also appreciate its collaborative and social aspect.

Tech’s Damaging Myth of the Loner Genius Nerd: This article expands a little bit more on the misconception of engineering as a solo task. What’s even more important is that it points out one of the things that really annoy me in the Artificial Intelligence / Deep Learning sector today: engineers seem to be developing tools for things that I don’t think many people will use. Take for example, machines that beat other players in a very particular game. What is this doing for the world at large? For people who are not gamers? For people from low-income households or third-world countries? What is this doing for the environment, for our healths, for improving society in general? As a computer scientist, making a positive impact in the world is my life goal, and it can be puzzling to hear that advancements in my chosen concentration mostly serve such a tiny niche. Every week you hear about that new deep neural net that can now replace a writer or an artist, but how about helping marginalized creators reach the audience who want to read their work? When did voices of machines become more important than the voices of humans? Especially when you know that these machines have been trained on a very particular subset of work that are most likely mainstream already. This article explains a little bit more on why empathy might be the key to averting this trend.

Anyway, that’s all I have for now. Like I said, I don’t like to dwell on this kind of situations. If you have any article you’d like to share, let me know. Or if you have thoughts about computer science or AI and what you think they can do for society, let me know too!

Sci-Fi and Fantasy Week on Goodreads: Or Adults VS YA VS MG

So, so, so, I found out today that it’s Science Fiction and Fantasy Week on Goodreads. I was excited to see what lists of books they recommend, when I made a mistake of reading through the comments section. Yeah, unfortunately. Who reads the comments section, these days, on anything? Those who are incredibly healthy, who aren’t in threat of keeling over due to high-blood pressure, that’s who. And while I think that would include me, a pretty hale 25-year-old… I’m not so sure anymore.

See, if you take a peek at the comments, you’ll find it infested with the usual classical champions arguing with trash defenders. I’ll make my position clear and say that I am very much a trash defender, mostly because I find it very difficult to have any affinity with classical works (especially since they’re so Eurocentric). And let’s face it! While I love reading books that are exhilarating and poignant just as much as the next reader, I do have times when I just want some cheap, brain candy. Sometimes I want my mind to take a break from the hassles at work and life, and if that means resorting to easy entertainment, it’s actually not bad for my health. It’s certainly not going to be any worse than getting all worked up, with arteries bursting and veins popping, hating on books that are written after the 70’s.

This blog post, or perhaps a better word for it would be rant, is going to be focused more on the divide between SFF Adult/YA/MG readers, because a lot of the comments in that Goodreads post is aimed at belittling younger readers.

Fact 1: I love children’s books. Yes, I’m 25, and I would unapologetically, unabashedly walk in the children’s (9-12) section of Chapters Indigo. I find children’s books to be so fresh and imaginative. They also often deal with themes that are central to my life even at this point in my mid-twenties: family, friendship, home, identity, finding your place in society, loyalty, and bravery. There are tons of other themes that I can’t pull off of the top of my head at the moment.

In fact, the majority of my favourite books are (or once were considered, since marketing ploys these days tend to push books towards the YA shelves) for children: The Queen’s Thief series by Megan Whalen Turner, The Goose Girl by Shannon Hale, The Lost Conspiracy by Frances Hardinge, and many more.

I love this a quotation by Diana Wynne Jones about the intellect of children and how they respond to books:

“Writing for adults, you have to keep reminding them of what is going on. The poor things have given up using their brains when they read. Children you only need to tell things to once.”

There are other people who have defended children’s literature in much more articulated fashion than I ever will, so I will just move on to the next point.

Fact 2: I like YA books. They’re dramatic, and they pull you in with a lot of shiny, mysterious allure, and when they get the romance right, they really get it right, if you know what I mean. In terms of themes, they might be a little more titillating with their handle on sexuality and morality; otherwise, I don’t think YA touches on themes that children’s books are not able to handle either. And I’ll get more to this a little later.

Fact 3: I like adult books. From their complex world-building to their flowy, detailed sentences, it’s a treat to lose yourself in different world so thoughtfully built.

Here’s my problem though. As someone who reads across all age-ranges, I don’t actually find anything that different in the thematic takeaway or profundity of books targeted for different age groups. I am forced to ponder about colonialism in The Lost Conspiracy as I am with Illusions of Fate. I am forced to ponder about spiritualism in Moribito as I am in Mistborn.

You know what I find to be the only thing that’s really different these days? The explicitness in sexuality and violence, and level of details in the writing. That’s all.

And so I froth at the mouth whenever people look down on books aimed for younger audiences, and because the lowest common denominator here are middle grade books, they unfortunately get the most flack.

Adults VS YA&MG

I’m not saying there aren’t bad YA and MG books out there. Oh there definitely are. But the bad books crop up equally in all three target age ranges. There are bad writers in all three tiers; there are poor plotters in all three tiers.

And each tier have their own set of overused, trite tropes.

Personally, I’m not a fan of love triangle at all; I almost refuse to read any book with a hint of love triangle in it, so that rules out a good lot of YA real estate for me. But you know what? I find a lot of love triangles in adult books too. And they’re not always better handled. If anything, a love triangle is a love triangle is a love triangle, and they’re just as tiresome in an adult book as they are in a YA book.

As someone who’s not that interested in romance, I do tend towards the children’s shelf more often than YA, because romance is such a central theme in so many YA books, and unless it’s handled in a tasteful way, I wouldn’t be that interested. Adult SFF books usually have tame romances as well, and even if they do get kind of explicit, the portion of the book that’s dedicated to romance is still pretty low, unless it’s jointly marketed as romance.

Also, I’m not a fan of gratuitous violence. The emergence of grimdark, I find rather unfortunate, not for its existence, since I know that there are people who find value and entertainment in grittiness and gore; but it’s unfortunate that people treat grittiness and gore now as an end in themselves, and not as a means to some overarching point. I don’t like how somehow if a book is “gritty” and “dark” that automatically entails maturity. Perhaps my definition of maturity is just different, because I think that finding hope and goodness in a world marred by evil is much more mature than succumbing to the bleakness of it all.

YA VS MG

You know, it’s strange because I feel like YA readers and MG readers would be better allies, but that hasn’t always been my experience. YA is sort of a new genre; fifteen years ago, there wasn’t a Young Adult section in the libraries and bookstores I go to. It wasn’t until Twilight came out that the books for younger readers became segregated into 9-12 and 13+. I have a little bit of a complex relationship with the YA community, because while I like some YA books, I find the YA community to be a little confusing.

See, YA readers would be the first to argue with adult readers about how YA books are meaningful despite being aimed at younger audiences. However when I was just getting into YA, there were a lot of YA readers who, ironically, turned up their noses on MG books in the same way adults turned their noses up at YA books. Since I was just transitioning between MG books to YA books at the time, I found the flippant attitude to really repel me from the community. Readers were bashing children’s books that I love, simply because they were for younger audiences, and I can bet that many of these readers had read those same books just few years prior.

Go to Goodreads now, and you will see a myriad of reviewers who say things like, “Oh, this book was bad. It must be written for younger audiences” on some YA books. What is that even supposed to mean? That the poor quality YA books are reserved for children? A bad book is a bad book regardless of what age it’s aimed at. I don’t understand how reviewers can think that if a book doesn’t cater to their taste, it automatically means that they’re too mature for it.

My other pet peeve is when high quality children’s books are repackaged and marketed for YA. It’s great that we’re encouraging teens to read books that work for younger audiences, but what I don’t like about this is that it reinforces the idea that MG books are of poorer quality. Because every time that a good-quality MG book is taken out of the MG shelf and placed in YA, then the only things that are left in the MG shelves are the ones that are not so good, which only supports the belief in the first place.

It’s the same story when we pull out a “cleaner” adult book and repackage it as a YA book. Again, great that we’re diversifying the YA shelves, but it only reinforces the idea that the books that belong in the adult shelves are the ones chock full of dirty and gritty stuff. I don’t like the implications of that… that to be considered mature, you have should be into darker or saucier things altogether. No, that’s not nearly sufficient nor necessary for maturity.

Well, This is Getting Long…

I think part of the problem really is that these categorizations are pretty arbitrary. Books are subjective in general. I think it’s better if we just encourage the idea that no matter what age we’re looking at, there will be bad books and there will be good books. It’s up to the reader to discern what works for them.

Oh, and let’s not even get into these classicists…

Writing Wins: Re-outlining

Wow, I realize that I’ve only ever had “Writing Woes” posts, where I talk about everything that goes wrong in my writing. I didn’t actually have a positive writing post until now, which is kind of sad now that I think about it.

Anyway, “win” is probably an overzealous word for what happened, but small wins are still wins in my book. Nothing dramatic happened, except that I managed to untangle the big hairy plot that I talked about in my previous Writing Woes post. Not only did I manage to do it, but I did it in 7 days. That’s… impressive by my standards, considering that I’ve been straining against this plot since the beginning of the year. Is it super-polished? Hah, no, I don’t think I’ll get to that stage until I’ve gone through 3 drafts at least. But the good news now is that I can move forward with my 1st draft without wanting to pull all my hair out.

I took a 3-week break from my story, and when re-outlining, I considered every plot point up for debate. And that worked out so well for me. When I considered that some of the determining plot points didn’t need to happen, or did not need to happen the way that I envisioned it would, it was much easier to tease out the tangles in the plot. I still lost a considerable number of characters, but I think it’s for the better. (Remember Nasi, the tarsier? I don’t know why I didn’t nuke him out of the story from the get-go. The poor animal had no speaking lines, had very little motivation, and didn’t contribute to the plot. But as attached as I had become to this useless character, I wound up giving him the pink slip as well.)

I believe there’s another Camp NaNoWriMo coming up in July, and I am going to try and finish the 1st draft then. I know it’s an ambitious goal, seeing it’s taken me 7 months to write the first half. But I think it’s also pretty telling that this children’s book is only halfway done at 70,000 words. I think I need to tell the story with much less words. Considering this is the first draft, I’ll resort to ‘telling’ rather than ‘showing’ if I need to move the plot along.

My hope is to be able to churn out a complete 2nd draft by the end of the year. It’s actually this goal that prompted me to re-outline my plot. My initial plan was to push through the first draft and figure out the changes to the plot as I go along, but it was causing me to lag behind my goals. I’ve read many writers advice that when you’re writing a draft, you shouldn’t go back and edit right away, but keep writing with your changes in mind. This wasn’t enough for me. I really had to revisit the entire story. It was disorienting for me to keep writing without addressing the issues from the parts I’d already written. It’s hard to build upon the story without knowing what events happened previously.

Learning is Intangible

For this post, I’m refocusing for a moment on my full-time job. I know that this blog is mostly filled with my hobbies and personal projects, so it might seem like those are the only things I do. However, most of my life actually revolves around my career in tech.

I started my internship as a data scientist at the beginning of the month. It’s my 2nd full-time job as a computer scientist, and in some ways, I cannot help but compare it to my 1st full-time job. I worked as a front-end software engineer for over two years in a smaller company. Both companies are great, filled with talented people I get along with. More importantly, in both companies I am doing work that I am passionate about even though they are different.

And that’s what I want to focus on in this post: the difference between my experience as a front-end software engineer from a small start-up(-ish) company, and my impression so far as a data science in a much, much larger company.

I knew that the work would be different. And yet, I think I naively assumed that the job would be similar enough that I could measure my productivity in the same way. In my old job, I knew I was being productive when I managed to finish my assigned tickets. Depending on the tasks, I could finish about five moderate bugs in a day; for new features, I could at least get some new code out to code-review within a day or two at most.

In my new job, the process is entirely different. We’re working in Kanban style, rather than sprints. My tasks are a little more vague. Instead of having a specific goal I could measure, like changing the header background from white to grey, or adding a pop-out to a link, I’m assigned tasks like visualizing the clusters of similar items. As you can see, this task is less measurable. For one thing, the end goal isn’t to just have a nice visualization, right? Underneath that statement, I know that my goal is also to analyze the visualization, to obtain insights from the clustering. And this means that I have to find out a clustering algorithm that can actually give me a good visualization; it means that I have to find the data that can work with such an algorithm; it means that I have to find a visualization that can actually give me insights. And in the end, how do I know if the insights are meaningful or not?

For the past four weeks, I have struggled a little with this vagueness. Yes, I know I could ask, but I get the impression that it’s also part of the job of a data scientist to figure out these things. Whenever I’m assigned a task, it’s no longer up to a product manager to break down that task for me. It’s up to me to figure out what’s involved in that process.

I think this is the biggest difference between my previous job and the current one. As a junior software developer, my job was to implement whatever the product managers told me to. This is in contrast with a research position, where my job is to discover what must be implemented.

I worry that I’m not being as productive as I can be, and my worries are compounded with the fact that I don’t actually know how to measure my productivity as a data scientist. Which leads me to this passage from The Lean Startup by Eric Ries.

When I worked as a programmer, that meant eight straight hours of programming without interruption. That was a good day. In contrast, if I was interrupted with questions, process, or — heaven forbid — meetings, I felt bad. What did I really accomplish that day? Code and product features were tangible to me; I could see them, understand them, and show them off. Learning, by contrast, is frustratingly intangible.

Wow. This book is required reading for my Technical Entrepreneurship course that runs alongside the internship. I don’t have much of an entrepreneurial spirit in me, but when I read this, I thought, “Aha! This is why this book is required reading!” I never realized what it was that bothered me as I started my career in data science, until I found this passage in the book. I could have never put it in a better way.

Learning, by contrast, is frustratingly intangible.

I realized much of what I do in my new job as a research intern is learning.  When you’re researching, what you’re doing is learning. You’re learning what works and what doesn’t. I was so used to measuring my productivity in terms of how much code I write or how many tasks I finished. Now I have to figure out a way to measure my productivity in terms of learning and the return value from what I learn.

Filipino Tech Words?

In our generation, many people,especially teenagers,are not aware of some uncommon words in Filipino.That’s because of modern technologies and stuff.Today,Im gonna show you the 10 uncommonly used Filipino Words with meanings and correct usage in a sentence.So get your vocabularies up and read attentively. 1.Haynayan (Biology) -A branch of Science that deals with life. Example […]

via Ten Uncommonly Used Filipino Words — Site Title


I never knew! What a shame!