Lunch at Work: Bento Boxes and Meals
When I started working an honest-to-goodness full time job, I bought lunch - a lot. I ate at the on-site dining room or went out to nearby delis and restaurants for a bite to eat. Eventually, however, that wore off. I couldn't afford, and didn't want to spend, $30+ per week on lunch-time meals. So I began bringing lunch - turning to leftovers and pre-packaged meals from the grocery store. None of these options factored in calories - and I liked less and less what my scale reported back.
Then an article in the New York Times covered a method that has been catching on recently: the bento box. I won't get into the history of bento, but one of the interesting ideas behind bento boxes is that if you fill your box with normal food (for example, not with chocolate fudge), the size of the bento equals roughly how many calories you are eating. It's an interesting way to control caloric intake.
Another thing that a bento does well is food separation. Why carry three tupperware containers of various sizes because you don't want to mix strawberries with chicken teriyaki? A bento box with dividers will keep your food separated, either in different sections on the same "level", or in a different tier if you have a multi-tier bento box.
Personally, I use a two-tier bento box that fits approximately 580ml of food, or just shy of 2.5 cups worth of food. So, my meal each day is about 580 calories.
What do I put into a bento? I generally go for laziness over creativity - I make a little extra for dinner the night before, pack the bento and let it cool on the countertop, then refrigerate it overnight. I try, however, to pack foods that will do well in a bento: small pieces of chicken, miniature burgers (I love Just Bento's meat and tofu recipe), small-cut vegetables, small fruits, etc. Liquid-based and very heavily sauced items can leak out if your box isn't water-tight; extra sauce can be kept in little bento sauce bottles.
Loving Someone You Hate
Like I explained in the Noir and Urban Fantasy blog, I'm a member of the Prose Challenge livejournal community. Challenge 032 was to create a piece of prose about hating someone you love.
The prompt immediately reminded me of IRON KISSED by Patricia Briggs, where Mercy is tricked into drinking from Orfino's Bane (a goblet that lets someone rob the person who drinks from it of their will). In IRON KISSED, the bad guy, Tim, has stolen a bunch of fae artifacts, including bracers that make him very strong and a Druid's Hide, which keeps his enemies from finding or harming him.
One of the things that Tim makes Mercy do is to fall in love with him. It's a very disturbing scene, and it's emotionally wrenching to watch Mercy fight with the compulsion to maintain a sense of self. In the end, though, Mercy is able to beat Tim--precisely because she loves him. She wasn't his enemy because he told her not to be, she says after she attacks and kills him.
This is not, however, a review of IRON KISSED.
It should seem obvious that it is easier to love a good person than a bad one. I'm not speaking of romantic love here, but rather platonic love--the love you have for a friend or relative. However, in my experience, friendships don't grow up because of admiration between two people about the strength of their consciences or the saintliness of their decisions. Most people don't pick their friends based on how much they donate to charity or how many puppies they've saved from the pound. It more usually has to do with things such as time spent together in a school or work environment or compatibility of interests, i.e. liking similar music, movies, sports, etc.
Most of my close friends are people that I've known for over five years. "The girls" I met in high school, and we were in the same extracurricular group. For 9th and 10th grades, we had all of the same classes together, and every year, after school we would stay after for at least an hour every day, and there were days when we were at school until five or ten o'clock at night working on sets, practicing lines. Some years, when we won State competition, we met on weekends to work on fundraising to pay for our trips to Globals in Tennessee. Other people I'm close to, I met in middle school and have been friends with--despite occasional blips where we fell out of touch, like when I went to college--ever since.
Around the time when I went to college, though, my mother got sick, and my college was about 2 hours from home. So I came home on weekends to do housework and spend time with my family, which meant that while I was attending classes, I didn't spend a lot of time socializing. I was friendly with people, but now that I've come back home for law school, there isn't anyone from college who I talk to, other than the occasional e-mail to or from a professor. The same is true of law school; I have acquaintances here, but there are only a handful of people here who I would invite to a party or out to the bar, and of them, I doubt I'll still talk to them after the bar exam.
What does this have to do with the topic?
Care and Feeding of Your Database – Fundraising Solicitations
As I mentioned in an earlier post, the care and feeding of one's fundraising database is important. It helps to keep your NPO running like a well-oiled machine.
Just as important as keeping your contacts straight is keeping your funding solicitations well-organized. One way to do this is through the use of the "Proposal" system. Keeping track of the proposals or funding requests you send to people or organizations will help you to track where your time is spent, not to mention the "life cycle" of the proposal in question.
Again, consistency is key when it comes to keeping your proposals in order. If you know you will have a lot of proposals, develop some guidelines as to how these should be entered into the system. Should you indicate the calendar or fiscal year in the proposal's name? What kind of giving this proposal falls under?
An example of codes you might develop for the database:
FY10: Operating = A Fiscal Year 2010 proposal for operating support.
FY10C: Astronomy Building = A Fiscal Year 2010 Capital support proposal for the astronomy building.
Your "naming" system should be as simple as possible while still allowing other employees to see, at a glance, what the donor or potential donor's solicitation history looks like.
The rest of the proposal record should be filled in as appropriate. Make sure you have the "Sent" or "Asked" date filled out when you actually ask the donor for a gift. Add in the amount of the ask - did you solicit Jane R. for $500, or for $5,000? Do you expect to receive the amount you asked for, or a smaller gift?
Similar to the "relationship" post, here too I counsel anyone designing a database entry system to keep it as simple as possible. Drop down fields should have as many options as necessary to get the job done - without being overwhelming. Avoid redundancy as much as possible; an employee shouldn't have to edit three parts of a proposal when one will suffice. This is especially important if you want anyone to actually follow your guidelines!
Dialog Tags
Part of being an aspiring writer is receiving feedback, and a big part of getting feedback is giving it. I've belonged to several critique sites over the years, including but not limited to deviantART (which, while a good site, leaves much to be desired if your goal is useful feedback on lengthly prose), Critique Circle (which is a great site, but I started to have trouble keeping up with the queue), and Scribophile (which is useful, but unfortunately much of the useful bits for novel-writers require that you sign up for the premium membership).
However, the point of this post isn't to analyze the various websites out there, but rather to emphasize a piece of common advice I've found myself giving lately. It's about something that should be simple, but isn't: dialog tags.
Something that should really be as easy as she said gives a lot of people trouble, sometimes because they don't understand the nature of the dialog tag, and sometimes because they try too hard. There are a couple of common mistakes that, while technically grammatically correct, should be avoided by anyone who wants their work taken seriously.
While technically "wrylies" is a bit of screenwriting jargon referring to parentheticals in a script, it's the one that's stuck with me over the years. They're also called "Tom Swifties," but I prefer the screenwriting term. An example is:
MAGIC IN THE BLOOD, Devon Monk — Review
MAGIC IN THE BLOOD is the second book of the Allie Beckstrom series by Devon Monk. I bought the paperback some time ago, but in honor of book three coming out November 3rd (next week!), I thought it would be a good idea to take the opportunity to re-read the series. I've already reviewed book one, MAGIC TO THE BONE.
The first thing I noticed when I got this book was how different Allie looks on the cover in comparison to MAGIC TO THE BONE. She's still clearly recognizable--same hair, same tattoos, even the same clothing style, but this Allie looks emaciated and a little fae. Her eyes are almost too big for her face, and she's clutching a bloody knife. I don't say any of this as a critique of the artist, Larry Rostant, but rather in many ways as a compliment. Allie is in a different place in her life in this book--and MAGIC TO THE BONE took a lot out of her, emotionally and physically. It makes sense that she'd look a little tired and lost.
I'm going to skip giving a summary of the book, since you can find one anywhere and it's not a brand new book, and just talk about the stuff I liked and didn't like about it.
In the last review, I mentioned how much I love the consequences that Allie has to go through, such as potentially losing her memory, massive bruising, etc. for using her magic. She has ways of coping--recording things that happen to her, directing backlashes so that she can prepare for the pain to come--but in MAGIC TO THE BONE, we never really saw her write much down in her book, so it's great to see that come back to bite her in MAGIC IN THE BLOOD, where she has no memory of her Happily Ever After, which also changes my perspective on how easy it seemed to attain; now, in book two, we see that there are still difficult things left for Allie to face.
Noir and Urban Fantasy
Awhile back, I joined a fiction community at livejournal.com called Prose Challenge. The community's "blurb" is
This is a community for those of you that enjoy creative writing. Every one - two weeks a new challenge will be posted. As an example, we might give you a title, an opening sentence, a picture, or something completely different. It is then up to you to write a story of up to 5000 words that links to the prompt we gave you. You do not have to enter every single challenge, it's up to you which ones you feel like doing.
and while I can't come up with something for every challenge, I usually try. It's a good community, and the prompts help keep me inspired to write, and I enjoy the practice of having to actually finish pieces every week; endings are much harder to practice than beginnings, after all.
I bring this up because this week's (week 33!) challenge is to write a film noir piece that takes place in an unusual location. While I often describe myself as an urban fantasy reader primarily, the truth is that my absolute favorite niche of the sci-fi/fantasy genre is what I like to call "noir fantasy." The Dresden Files (beginning with STORM FRONT) by Jim Butcher are a good example of this, as are Glen Cook's Garrett, P.I. books (beginning with SWEET SILVER BLUES), the Cal Leandros (NIGHTLIFE) books by Rob Thurman, The Vampire Files (BLOODLIST) by P.N. Elrod, and the Nightside (WELCOME TO THE NIGHTSIDE) books by Simon R. Green.
Care and Feeding of Your Database – People and Organizations
If you work in the fundraising department of any NPO, that department most likely has a database with which to keep track of its donors and prospects. Many NPOs use The Raiser's Edge, a Blackbaud product; others use eTapestry, Microsoft Access, and other, similar programs. The Chronicle of Philanthropy has a list of different companies and their software programs.
Databases like Raiser's Edge (RE) are extremely powerful, but they require "care and feeding". It isn't enough to create a record and drop your donor's information into the document with no regard to consistency. If you're starting up an NPO, you're lucky: you can design "best practices" now, and while you'll need to make sure your volunteers or employees stick to it, you'll be making a clean start.
If you're part of an established organization, your job is a little more difficult: not only do you need to develop best practices; you should change your pre-existing and active records to the new system, and you'll need to convince your fellow employees to follow the system. This post will cover tips for your database records involving people and organizations; funding requests will be another post!
Grilling, Sophisticated and Easy
As a general rule, I'm a terrible cook. Unlike Charity, it's not one of my talents. Although I'm capable of making decent-tasting food, usually I'm too bloody lazy to bother. Most times, if my food tastes good, I'm content. I don't insist on a lot of variety, either; 3lbs. of spaghetti or taco meat or catchatori will last me for a week and I'm content to eat it for three meals a day. I can't eat TV dinners, but I'm totally fine with pot pies, pre-made bbq ribs (they only take 10 minutes in the oven!), and other frozen foods that go into the oven.
Despite this, I love to grill. Most of my parties are outside, where my family has a big, elevated fireplace that we made out of cinderblocks and firebrick, a brick oven (made by us of the same material), a nice big cinderblock grill with two heights for the coal, and a smoker (which we didn't make, but it's still awesome). In my family, we take grilling seriously. Hotdogs and hamburgers are not allowed at my parties; I grew up on venison bites, made from deer shot by the next-door-neighbors who came to the pitfires my dad hosted (which were the center of the neighborhood). Nothing compares to the baked beans my mother makes on the grill, and the best apple pie I've ever had was made in the brick oven right beside it.
Now that I'm older, I host my own parties out on that patio. It's not the neighbors who come, but friends of mine (though neighbors are always welcome, we tend to stay out later than the retired folks who live where I grew up), and we don't cook my parents' food. We cook mine. There still aren't hotdogs, though, and I'm not the kind of person who cooks with a recipe; I cook by eye. On the grill, it's the only way to be sure.
I had never really cooked before I hosted my first party, but I had a friend who was vegetarian and I love(d) chicken, so we started from there and raided the garage cabinets for stuff to season with. Here's what we use:
Quick Meal: Peasant Chicken Pasta
It's 6:30. You've faced traffic or the subway to get home, and now it's time to make dinner for one. Resist the urge to order in, and cook up a quick meal, with leftovers that you can bring to work for lunch the next day, or freeze for a later dinner. This dish is healthy, flavorful, and can be cooked and on the table in twenty minutes. I call it "peasant" chicken pasta because it's good for emptying out the vegetable drawer and pasta boxes.
Ingredients
1 large chicken breast, cut into bite size pieces
1/3 lb short pasta, such as penne or farfalle
2 cups chopped vegetables of your choice - I like to use carrots, broccoli, red peppers and cauliflower or asparagus
4 large sundried tomato slices, julienned
1 shallot, chopped fine
2 cloves garlic, chopped fine
2-3 Tbsp olive oil
1/2 cup prepared pesto sauce, or 5-6 Tbsp homemade pesto
A few pinches of salt for the pasta water
Salt and pepper to taste
Grated Parmesan or Grana Padano (optional)
Instructions
Heat a large pot of generously salted water, and add the pasta when boiling. Heat a nonstick frying pan on medium, and sautee the chopped shallots and garlic, then add the chicken and sautee until almost cooked through. Add the vegetables and sundried tomatoes; cook until tender. When the pasta is al dente, drain, rinse, and add to the frying pan, then pour the pesto sauce or homemade pesto on top and mix thoroughly to combine and heat the sauce. If using homemade pesto, add a few tablespoons of chicken broth to keep everything moist. Add salt and pepper to taste, and top with grated cheese.
Vegetarian? Substitute very firm, well-drained tofu for the chicken, use vegetable broth, and a Parmesan with vegetable or microbial rennet.
Game Design Philosophy: Lockpicks?
Around the beginning of the year, I became involved with Lithmeria, first as a builder, then, eventually as the head of building and one of the lead developers (of which there are currently two; Selkrener is the head coder and top boss. We also have a small staff.). To give some background, Lithmeria is a MUD
In online gaming, a MUD (multi-user dungeon), pronounced /mʌd/, is a multi-user real-time virtual world described entirely in text. It combines elements of role-playing games, hack and slash, interactive fiction, and online chat. Players can read descriptions of rooms, objects, other players, non-player characters, and actions performed in the virtual world. Players interact with each other and the world by typing commands that resemble a natural language.
-- Wikipedia
with a high fantasy setting. There are two factions, which are engaged in an on-going, long-term conflict, that players will be able to be part of. Characters can be one of eight classes, two of which are based on the rogue archetype (one for each side of the conflict). As developers, Selkrener and I encourage discussion on the forums about what potential players want to see in the game. One of the threads on the forums is the Skill Ideas and Suggestions topic, and a discussion about locks and lockpicking came up. We were presented with simple question with complex underpinning: Should rogues be able to pick locks?
There are a couple of issues with implicit in the question: