So there you have it, fellow authors.

Phase 1 of our investigation is over…

I have a few underlying questions though…

If we find magic and rhetorical concepts in the bible and classic iterature (Emma), then why are we not putting more of an emphasis on fiction in learning? Can’t it be just as powerful, just as educational, just as important?!

Have we found our next investigation?! Leave me your thoughts and let’s discuss!

Learning to Read is Inseparable From Teaching to Read.

I’d like to close out Phase 1 of my investigation with a little breakdown (not mine, I already did that this year!) of language, of fiction, of rhetoric… Where do we stand with language, with fiction, with education of language and fiction, in the 21st Century?

Language is powerful. From arguments, to political speeches, from science textbooks, to novels, language is incredible. The way a historian might describe how the telephone was invented will be mostly, if not all, factual – but the way a novelist might describe how the telephone was invented could be a fantastic story of blind witches needing a way to communicate across a world without drawing attention to their power. I don’t know… My point is, language can be literal, factual, nonfiction… but it can also be lyrical, silly, and beautiful (not that facts aren’t beautiful). As Michael Holquist says in his article about Language and Fiction, “Language has a dual nature: it can be logical and useful and provide valuable information, but it can also be literary and thus unconstrained by facts and logic” (Language of Fiction, Fiction of Language).

If we, as students, as writers, as educators, don’t learn the multi-faceted world of language, how are we to teach it to the next generation? What kinds of novels will hit the shelves in fifteen to twenty years if kids aren’t able to deeply explore the Fiction world alongside of the Nonfiction world? According to the Commore Core State Standards Initiative, between grade 4 and grade 12, the percentage of time spent on fictional and nonfictional texts drop from 50%/50% to 30%Literary/70%Informational. With such a high emphasis on nonfiction/informational texts, it’s like we’re trying to limit the way our students are exposed to language. “Fiction is a category the framers of the ELA standards either ignore or treat as merely a set of techniques with a mysterious abilitiy to enhance the truth”  (Language of Fiction, Fiction of Language).

“We are the teachers of students who in increasing numbers will come to us trained in the shadow of the CCSSI’s restrictrive conception of language” (Language of Fiction, Fiction of Language). 

“Go back, each of you, to your mother’s home.”

I honestly never thought I’d put “logic” and “bible” in the same sentence. There’s a first for everything!

Pre-K Pause. This is not a religious (for or against) blog post, so much as a “persuasion techniques in a book in the bible?!” blog post. Get off your high horse, I’m not coming for your religion.

I have not read the bible academically in many moons… if ever… Having said that, yes, I have read the bible. Also yes, it has been years. So bear with me on this one… I no longer even own a bible. So I’m investigating persuasion modes/techniques in fiction. I found an interesting article about the art of persuasion in the book of Ruth! WHAT! My first thought was “I’ve never heard of a book called Ruth.” #Heathen. So in this article, Matthew Michael (wow, two Judeo-Christian names) brings attention to a few literary devices. 

For those of you (*ahem, us*) who don’t know this story, here’s a quick synopsis: The Book of Ruth is about Ruth and Orpah (two women of Moab) who marry the two sons of Elimelech and Naomi (Judeans) who settled in Moab to escape a famine in Judah. All 3 husbands die; Naomi plans to return to her native Bethlehem and urges her daughters-in-law to return to their families. What tickles me about this, is there were many persuasive techniques present in this book of the Bible – from repitition, to rhetorical questions, to emotive language, to metaphors, to oath-swearing – all of these devices being “foundational to the characterization, plot, and the crafting of its narrative space” (Art of Persuasion).

We see the use of logical argument when Naomi tries to convince her two daughters-in-law to “go back, each of you, to your mother’s home.” One of Naomi’s logical arguments is that “staying with Naomi would mean abandoning all hopes of remarring because [Naomi] is too old to bear more sons” (Art of Persuasion).

Bottom line, whoever wrote the book of Ruth clearly used logos – but intentionally or unintentionally is the real question. Did they even know about logos? Was their ability to utilize logos an independently developed concept, completely separate from Aristotle’s appeals?! Did they speak to Aristotle about the appeals?  You know that ice-breaker question of “who, alive or dead, would you invite to dinner”? I think the author of the Book of Ruth might be in my top 10… What are your thoughts?!

 

I have found logos to be the hardest mode of persuasion to utilize in writing. I think too many people in this world think their own logic and reasoning are sound… and that makes it hard to feel comfortable trying to appeal to logos. Is that just me? Am I totally alone on a canoe in the ocean on this one?

“Evil to some is always good to others.”

Let’s start with a classic I share a name with… Jane Austen’s Emma.

We all know (or at least should, by now!) that ethos is the appeal to an audience’s value or character – the good, the just, the credibility, the reputation, you get it. If we are susceptible to an ethos persuasion, we might be more likely to relate to a character who is of a social status or wealth that we find attractive or appealing. Ethos, as it relates to rhetoric, is when a speaker (or writer!) must work to understand the values of her audience in order to persuade most effectively (Ethos in Austen’s Emma). I think one of the fascinating parts of the way Emma is written is that “instead of demanding that the reader simply ‘learn this,’ the narrator implies, “Of course you (reader) alread know this (whether the reader knows it or not) because you share in my ethos'” (Ethos in Austen’s Emma). Again, there’s this connection to the audience…

In order to write a book, a story, a poem, a speech, what have you – one of the first steps is to know who your audience is. The universal audience? An audience of one? Yourself? (shout out Perelman and Olbrechts-Tyteca! IYKYK) 

So, if I understand what you value, what you find reputable, I’ll be able to make you feel whatever I want you to feel… Interesting. You know, I have a friend who is in the midst of writing an incredible book about a world similar to ours but also…immensely dissimilar? The world he has created is beautiful and magical, without going anywhere near Harry Potter magic. It’s the feeling of magic, more than the doing of magic. Whenever we get a chance to talk deeply about his book (which is not as often as I’d like!) he says his one goal with his book, if nothing else, is to be able to make the reader feel exactly what he wants, when he wants. He wants those feelings to be universal. I’m curious to find out which modes of persuasion he ends up using to accomplish this… But alas, a task for another day!

Starting something new…

Hello Fellow New Authors!!

I am investigating the relationship of Ethos / Pathos / Logos persuasion in fiction! Maybe exploring it with specific authors or books? 

Thoughts? Concerns? Where will this go?! What will we find?! 
I lay it down as a general rule, Harriet, that if a woman doubts as to whether she should accept a man or not, she certainly ought to refuse him.

Well – pull up a chair, put on your glasses, (grab a glass a wine!) and join me on this journey!

Stay On Top Of It!

I don’t know about you, but sometimes I struggle with deadlines. Procrastinators of the world unite! …tomorrow. As I’ve gotten older and been “out in the real world” as my parents like to say, I’ve definitely gotten better, but it hasn’t been easy. Here’s a few tips to help you stay on top of your assignments, projects, and work:

  1. Put it in your calendar.

Wherever you track your meetings or assignments (preferably electronic, so you can set reminders!) put an event on the due date and set multiple reminders (I like to do two reminders: 1 week in advance and 3 days in advance).

  1. Start. The work. Early.

When you start projects early, there is so much less pressure! Start early enough, and that 3-day reminder is just a “final touchups” reminder, and not an “oh no! I only have 3 days to do this project!”

  1. Set timers.

Sometimes it can be hard to sit at a computer and write a whole presentation/project/paper at a time. You need structure! Set an appropriate amount of time, and then work hard. 45-60 minutes of nonstop, non-interrupted (to the best of your ability) work, and then a 10 minute stretch your legs /get a glass of water break. If your presentation or project is in multiple parts, establish a rough timeline for those pieces and do the same thing – 20 minutes to write the introduction/opening slides; take a quick break; 30-45 minutes to work on the body/first few slides; take a break and walk your pet; 30 minutes to write a conclusion/closing slides; take a break.

Note: Be sure to stretch your legs and eye muscles – sitting and staring at a computer all day every day isn’t good for your body!

  1. Don’t be too hard on yourself.

Sometimes we miss deadlines. Sometimes we have to push proposals/presentations/meetings because we’re not as prepared as we’d like to be. Sometimes life gets in the way. That’s ok! We’re all human. As long as it’s not a repeated behavior, having to push a meeting here or there is not the end of the world. Don’t let it ruin your day or week. Apologize for any inconvenience and get right back into it – maybe after you play with/walk your dog for a few minutes to get some serotonin/dopamine!

  1. Celebrate the big ones.

And the small ones – who’s counting? When you turn in, publish, push send on that really important email, close out a presentation – celebrate. Take a moment to pat yourself on the back for completing it. I sometimes find myself ranting to my partner about a really tough project I’ve been working on and even if she doesn’t understand a word about it (and vice versa – she’s in finance, I’m in application services) when I tell her I’m finished, I get an “I’m so proud of you” that the sent, saved, or published icon never seems to get right.

 

Please feel free to reach out with any questions (in the comments section below)! And remember to subscribe (check out the widgets on the side)!

My door is always open.

Leadership: One Boss, Two Boss, Bad Boss, Good Boss

Leadership (noun)
Embedding the capacity for greatness in the people and practices of an organization, and decoupling it from the personality of the leader.

Please forgive my terrible pun of a title. One of my coworkers (shout out Iwan, leader of the Service Reliability Architects (SRA)) recently shared with me a video of Former-Captain David Marquet’s talk on Leadership. If you have an extra 24 minutes or so, please take the time to watch the video.

It’s one of those talks where, by the end of it, the listener is inspired – inspired to work, inspired to lead. I was working while listening to this the first time, and I remember chuckling at some of David Marquet’s anecdotes, and having a few really thought provoking moments. David talks about how when he was first promoted to Captain a submarine, he trained for 12 months on every detail of the USS Olympia, a very specific submarine, but at the last minute, was reassigned to the USS Santa Fe; he didn’t know the ins and outs of the Santa Fe the way he did the Olympia. But his crew knew their jobs. Instead of barking orders, especially since he wasn’t totally sure how everything on the submarine worked or ran, he let the crew take charge. He literally stopped giving orders. The crew stopped bringing him problems sans solutions; they stopped saying ‘I recommend…’ they stopped saying ‘I would like to…’ and they started saying ‘I intend to. . . .” Everything changed – this submarine went from the worst performing submarine in the fleet to the highest score for operating a submarine in the history of the navy. 

Iwan and I had just left an SRA Sprint Demo, where the SRAs show off the cool new things they’re doing/developing to improve our products and product Cloud Maturity (ability for products to function on the Cloud instead of on premise; Software as a Service). The first demo of the call was incredible to watch – the automation, the streamline, the problems it promised to solve. I can’t get into specifics (partially due to lack of understanding technical aspects), but suffice to say this demo was revolutionary for Infor. Iwan messaged me after the call and asked how I liked the demo – a lot of it went over my head, but I told him it was fascinating. Iwan then shared a piece of advice I will never forget:

This is what happens when managers don’t tell people how to do their jobs, but explain where they want to go.

 

Some of my favorite lines from David Marquet’s talk:

“Going into combat? Not scary. Admitting you don’t know something when you’re the Captain of a nuclear submarine? Scary.”

“I now think these words ‘I don’t know’ are the most important words a leader can say. Because those are the words that open the door to learning.”

 

Please feel free to reach out with any questions (in the comments section below)! And remember to subscribe (check out the widgets on the side)!

My door is always open.

Jira Processing – A Day in the Life

Some common abbreviations/acronyms used in this post:
JQL – Jira Query Language, the most powerful and flexible way to search for your issues in Jira; for everyone: developers, testers, agile project managers, and business users
RCC – Release Certification Checklist
BODs – Business Object Documents
GA – Generally Available
MSF – Manufacturing Solutions Framework; our product system of record – where we manage and maintain product, suite, and third party product information, as well as maintain product SKU information.

I log into my workstation generally between 0730 and 0800 every morning – most days with a freshly brewed cup of coffee, but if I’m running late, I opt for a Red Bull instead. 

My first task of the day: go through my unread emails, respond to anything I can, complete small tasks, add larger tasks to my calendar “To Do” list. 

My second task of the day: take my dog out for his morning walk and then feed him. He likes to sit on the recliner in my office during the day, supervising.

My third task of the day: log into our company Jira and open the “My Open Issues” filter, JQL query: “assignee = currentUser() AND resolution = Unresolved order by updated DESC” to see what’s on my agenda for the morning. For example, a typical morning will have multiple requests for Major and/or Minor RCCs and a few BOD tickets – and might look something like this:

There are other types of templates I deal with, like Admin and Rebranding, but those are generally once a year (Admin) or relatively uncommon (Rebranding, for when a product is being Rebranded). 

Now that I’m caffeinated and have my action items organized, it’s Go Time:

Our Release Certification Checklist has been refined over the years to continuously offer the most direct, succinct, and straight forward path to certification – in as few tickets or “tasks” as possible. When I open a request ticket, the first thing I do is click the “Start Progress” button, so the person who requested the RCC knows I’ve picked it up and started working on it. I read through any extra information they may have included in the description of the ticket – some teams ask for extra tickets. Then I open the attached Macro-enabled Excel spreadsheet (the RCC) and fill in the “Admin” cells:

(Jira) Project key, Product name, Fix version / GA Date, etc

Depending on their answers within the header of the template, I alter the amount of tickets that will get issued.

Release Type: Major (more tickets) / Minor (less tickets)
Deployment Method: Multi Tenant, On Premise, etc

I do a few housekeeping steps – ensure there’s a Fix Version in MSF that matches to the release; ensure the summary lines of the tickets are all identical (“Product A – ###”, where ### is the Version); ensure each ticket is numbered for the Macro. When all of that is done and the template is ready to go, I input the User ID and Password of the Jira Service Account we use for processing into the Macro and away she goes! I then grab the hyperlink of the Fix Version in the project (where the tickets just got issued!), and paste it into the Request ticket with a comment of:

Tickets have been issued: hyperlink.  Thank you!

And close the ticket. Then I move on to the next ticket until all tickets in my queue have been processed!

 

Please feel free to reach out with any questions (in the comments section below)! And remember to subscribe (check out the widgets on the side)!

My door is always open.

Jira Administrator – or as I like to call myself – “All-Powerful”

Some common abbreviations/acronyms used in this post:
RCC – Release Certification Checklist
RCM – Release Certification Manager
Dev – Development
BODs – Business Object Documents
MSF – Manufacturing Solutions Framework; our product system of record – where we manage and maintain product, suite, and third party product information, as well as maintain product SKU information.
GA – Generally Available

I work within Application Services, or more specifically, the Release Certification and Governance team at Infor*. We lovingly refer to ourselves as the “Gate-Keepers” or, more quietly, the “RCC Police.” As a unit, we “police” all product releases; we uphold and improve policies and processes that ensure we are able to meet commitments we have made to our customers, especially in regards to training, documentation, functionality, security, etc. My technical position is Business Analyst, and I work alongside Dev Project Directors, Dev Project Managers, Industry & Solution Strategy Directors, Quality Assurance Managers, and all manners of Product Development; when I describe my particular job to my friends, I like to call myself the “grunt” of my team – which is by no means a negative term. My main tasks, day-to-day, are processing RCC requests, processing BOD tickets, maintaining MSF data, and working on/improving current processes within Release Certification. I run reports, gather data, occasionally do data entry, and of course support the RCM’s in their endeavor to certify releases. 

The majority of the processing parts of my job are done within Jira, a project management tool developed by Atlassian. All of our products going through Release Certification must have an RCC for each release in their Jira Project. Each RCC has a number of tasks (the exact amount is dependent upon the size of the release: Major, Minor, or Maintenance) that must be completed well before GA, at GA, or sometimes post GA. Most of my coworkers, at least that I work directly with, are Jira Users, meaning they have basic privileges within the system. I was recently “upgraded” to Jira Administrator – so I have all kinds of power. I promise to not let it go to my head. I have become the go-to person within my team (and other teams) for help with Jira. Even some of the Education department and Information Development teams have asked me to help them with Filters (a way to view, categorize, and sort Jira tasks) and Dashboards (a page for gadgets that display Filters in more aesthetically pleasing ways than a list). While I am always learning better ways to utilize Jira, and still have a ways to go to becoming a Jira Master, this is easily one of the best things I can add to my resume: 

Emma VanDerLeest, Business Analyst & Jira Administrator.

 

*Infor is a global leader in business cloud software products for companies in industry specific markets. Infor builds complete industry suites in the cloud and efficiently deploys technology that puts the user experience first, leverages data science, and integrates easily into existing systems.