Tonight I’m giving a lightning talk at PyLadiesATL called “Five Things I Learned at PyOhio”, and I wanted to share it here in case you weren’t able to make the meeting, or are curious about what I covered!

PyOhio is an amazing FREE conference that was held this year in Columbus, Ohio at the Ohio Union. The dates were Saturday August 1 and Sunday August 2, with sprints on Friday July 31 and Monday August 3. Thanks to the organizers and sponsors for making this unforgettable experience possible, and to each of the speakers for taking the time to prepare and deliver such thoughtful, helpful talks. Below, I highlight a few of them.

1) Diversity? You Gotta Want It

Stephanie Hippo’s talk “You Gotta Want It: Building Up Women in Computer Science” was possibly the most honest, critical, and at times damning talk I’ve ever heard about a group’s journey towards becoming more inclusive, welcoming, and ultimately, diverse. What I loved about Stephanie’s delivery was how very much she owned the fact that her group hadn’t been welcoming. It reminded me that the first step in recovery is admitting you have a problem. But to even be able to admit that problem, Stephanie had to critically look at the way her group was doing things – starting with the data – and have hard conversations with her colleagues about why things should change.

It’s not enough to simply say that you want things to be different. Like Stephanie’s family’s motto: you gotta want it. When you realise that you don’t like the diversity distribution of a given team/organization/project, admitting you have a problem is only the first step. It must be swiftly followed by a commitment to examining critically how things got the way they did, and a resolution and plan to address the issues structurally. And hey, if you can find time to tell the rest of us how you did it, all the better! Thanks, Stephanie, for your amazing talk and actionable suggestions.

Stephanie wrote up her talk and shared it on Medium. You can also follow her on Twitter.

2) The Pomodoro Technique

I thoroughly enjoyed Ann Schoenenberger’s talk “Learning to Learn Python”. Ann covered the challenges and opportunities confronting the autonomous learner from a personal perspective and from many conversations with other women coming to STEM from non-traditional backgrounds. One of the most helpful takeaways I got from her presentation was the description of the Pomodoro Technique. Now, if you’re a Pomodoro devotee and I’m totally butchering it, I apologize in advance. But the gist of the technique, as I understood it, is to work without distraction for 25 minutes, and chase that work with a 5 minute break. Another 25 minute session can come next, with a 5 minute break after.

Ann shared how budgeting time like this had been really helpful in keeping on her track as she learns Python. And while 50 minutes a day of concentrated study isn’t going to turn you into a programmer overnight, over time – and with discipline – it can be a helpful step towards reaching your goal. I have been employing the Pomodoro technique since I learned it from Ann on a near-daily basis and have seen huge gains in my personal study.

Read Ann’s abstract and follow her on Twitter for more.

3) That cool project? It took a lot of time, and there were plenty of bumps in the road.

Learners suffer from a lot of ailments, and discouragement at slow progress can be right at the top of the list.

But the fact is, complex projects do take a lot of time, even for experienced developers. Doug Hellman’s talk “How I built a power debugger out of the standard library and things I found on the internet” was, as he said, less about the actual code, and more about the process of building his project Smiley. When he got started, he asked himself, where do I start? What do I do first? What do I want to accomplish? And then: well, what do I know? He emphasized that throughout the nearly two-year period of building Smiley, he continually checked in with himself about what he already knew and what he wanted – or needed – to learn to make it happen.

In Allen Downey’s book Think Python, he draws a comparison between the act of debugging and programming itself:

For some people, programming and debugging are the same thing. That is, programming is the process of gradually debugging a program until it does what you want. The idea is that you should start with a program that does something and make small modifications, debugging them as you go, so that you always have a working program.

In Doug’s presentation about building Smiley, I heard all of this. So whether you’re a Python expert building a power debugger out of the standard library and things you found on the internet, or a new coder trying to solve a Codecademy puzzle, follow this same process. Start with what you know, make a list of what you want to learn, and continuously be open to the dynamic process. And, importantly: be patient with yourself!

4) Data Science Resources

Since Atlanta PyLadies said they were really, really, really interested in data science topics, I tried to attend as many of these talks as possible. Michael Becker’s “Data Science: It’s Easy as Pyǃ” was one of the standouts. I wanted to include an image of his resources slide since I thought it might be of interest to our PyLadies.

Here are those links:

• Jupyter.org
• pandas.pydata.org
• web.stanford.edu/~mwaskom/software/seaborn
• scikit-learn.org
• github.com/jakevdp/sklearn_pydata2015
• github.com/EducationalTestingService/skll

5) It’s okay to bring exactly who you are to the experience of writing Python

My dear friend Anna recently asked me for a quote about why I love the Python/Django community for her sure-to-be-amazing upcoming DjangoCon talk. There’s so much to love about this community, but perhaps my favorite thing is that we can bring exactly who we are to the experience of building software together. From a non-traditional background as a cook, I’ve felt nothing but enthusiastic welcome from each of you. And I’ve also seen this diversity modelled in my colleagues, who play e-bassoons – like Lars pictured above – sew quilts, bake cupcakes, bring their families to conferences, and more.

It’s important to me that we don’t just have lives beyond our work, but that we share our lives *within* our work. To me, that makes all the difference.

When I was invited to give my first talk at a Python conference – PyTennessee – I knew that I really wanted to bake cookies and have them available before my talk. When I mentioned this to a friend, she discouraged me, saying that I shouldn’t. She was worried that I wouldn’t be taken seriously, or that it would somehow make me look bad.

I know she meant well, but after thinking on it a moment, I decided that I would bring eight dozen cookies. And not only would I bring them, I’d wear a flouncy Betsey Johnson dress while giving my talk. And you know what? Aside from my outrageous nervousness, it could not have been a better experience! I met amazing people, and we ate cookies and talked Python together. What more could you want?

So, please feel invited to bring exactly who you are to this activity. If the recent #ILookLikeAnEngineer debacle taught us anything, it’s that you can look like an engineer, no matter what you look like or what you do in your spare time! And don’t let anybody tell you differently – especially if cookies are involved.

Bonus Round: PyLadies are Everywhere!

Okay, so this one was mostly just for fun. But I wanted to share this image to illustrate that we PyLadies are all over, and we’re doing good things in our community to help women learn Python.

So, one of my responsibilities as a co-organizer of PyLadiesATL is determining a new regular date for a our monthly meetings! I reached out to some folks via Twitter to get a sense of Atlanta’s existing social opportunities across a variety languages. I figured why not go ahead and share what I’d learned, in case anyone else is interested?

Numbers below refer to the first, second, third, or fourth instance of a given day in a month. For example, Atlanta’s Clojure meetup, Atl-Clj, meets monthly on the second Tuesday. Let me know if this is unclear, or if there’s a better way of organizing!

Our PyLadiesATL Meetup page will be updated when we’ve picked our new date. Links to Meetup pages, where applicable, included below.

Monday
1: AllTheNerdyLadies.com monthly social hour
2:
3:
4:

Tuesday
1: PyATL Jam Session monthly meeting
2: Atl-Clj, Atlanta’s Clojure Meetup, monthly meeting
3: WomenWhoCode Atlanta monthly meeting
4:

Wednesday
1:
2: ATLRUG: Atlanta Ruby Users Group, monthly meeting
3:
4: Rails Girls Atlanta monthly meeting

Thursday
1:
2: PyATL: Atlanta Python Programmers monthly meeting
3:
4:

Friday – Saturday – Sunday
No meetups on these days!

Please let me know if there’s anything that should be added. Thanks so much in advance!

Do you ever find yourself writing a to-do list, and in the top line, instead of writing something to do, you write something you’ve already done… just for the satisfaction of immediately making a mark beside it?

I do this a bit more often than I would like.

I did it this morning, in fact.

To the right, you see my (actual, today) to-do list. I write it like a letter, with the date at the top, in a beautiful book. To the left is something I started today in response to feeling overwhelmed by all that seemed ahead of me. Not a list of to-do, but a list of things done.

As a learner, I often feel as though I am in a transitory period. I’m in one place, and I’d like to be in another. The process of getting there is one of growth, change, and transition. It’s also often painful.

This liminal space – unsatisfied with the here, and certainly not yet there – can feel very vulnerable. Perhaps you’re impatient for signs of progress, tempted to give up when they come too slowly, or not at all. Or maybe you feel that the road ahead is too long, the journey too arduous: there’s just too much to learn and do, so why try? For an extra dose of demoralization, try comparing yourself to others who have already accomplished what you’re still trying out. Is it even more insidious? Do you lack confidence in your innate abilities, your potential to learn, your stamina, or find it hard to ask for help?

As someone learning to code, I have felt all of these feelings a dozen times or more. I become dispirited and feel disempowered: there’s too much to do, I’m too behind, I’ll never catch up, I’m not good enough.

And yet I’ve noticed that part of what informs this hopelessness is not taking stock of the small, incremental steps I’ve taken towards my goal. I focus so much on the to-do, that I fail to acknowledge what has already been done.

It sounds trite, acknowledging that a journey of a thousand miles is made up of steps. But for some reason, it’s all too easy to lose sight of those steps.

By writing my dones today, I bring awareness back to the ways I am moving towards my goals, even when progress seems achingly slow, or depression and anxiety creep in and tell me I’ll never make it. This blog post is another sign of that, an embattled cry against those forces.

I hope that if you’re struggling with a project, you’ll take comfort in these words, and perhaps even a few moments to write down all that you have (already) accomplished today. A few deep breaths and cup of tea can help, too.

When you return to your work – and you will – I hope you return with new energy, clarity, and hope.

Looking for more inspiration? I highly recommend checking out my friend Anna’s blog. She’s got a few great posts up right now: Understanding Computer Words: What Is A Decorator?, Coding Made Me a Better Problem Solver, and My Favorite Python Learning Resources.

Also on the learning journey? Your best read today will certainly be Aubrey Howell’s post at Keen IO’s blog: “Don’t Let Anyone Tell You That You Can’t Be A Developer.” Seriously.

PyTennessee was last weekend and it was amazing! I was privileged to meet so many incredibly bright, kind people, hear great talks, and was honored to give a talk of my own. Below I share highlights from the weekend and a round-up of all the conference resources I’ve collected thus far: links to talks, slides, video, etc. Hope you enjoy and find this useful!

First things first:

The venue was gorgeous. The food was delicious. The hotel was cozy, clean, and convenient. Conference check-in was easy and quick. The “red shirts” volunteers were helpful and kind and always there when you needed ’em. Organizer Jason, his delightful wife Denise, and his lead volunteer coordinator William put together an incredible event. Thank you.

Friday night EventBrite treated the PyLadies to dinner and conversation at their Nashville HQ. Lynn Root gave an inspiring, heartfelt version of this talk entitled “I’m faking it.” If you didn’t get to hear her speak, I highly recommend reading the post.

Probably the funniest slide from PyTennesee weekend. From Ian‘s “Cutting Off the Internet: Testing Applications that Use Requests” Saturday afternoon.

Also hilarious (and fascinating, informative, and generally fun): Kyle Kelley’s keynote on Docker for Ephemeral Workloads. His slides are here.

Chris and Ashwini gave a thoroughly engaging, beginner-friendly talk: Introduction to HTTPS: A Comedy of Errors. Love how expressive Chris is! Here are the slides.

Folks really loved Chris‘ talk “Purely Functional programming in Python“, but I was at Becky‘s so I missed it. Thankfully he shared slides. Hopefully someone will eventually see fit to record him giving this one – looks like a lot of fun!

Bill Israel gave a thoughtful, accessible talk entitled “Function Decorators: How Do You Even“. His slides are here.

It was a privilege to hear Becky talk about her passion for languages as she persuaded us all “Why Your Next API Should Be Designed By a Linguist“. I love it when people bring their whole selves to Python. Her talk was recorded, but has not been posted… yet!

Photo (and creation!) by Kevin Cox, @VintageBinary

Legos all weekend with Lamp Post Group! Lamp Post was PyTennessee’s champion sponsor, not only providing funds to make the conference happen, but making an additional donation of $500 to PyLadies! I’m certain I’m not the only person who got goosebumps when Lucky made the announcement before Lynn’s keynote Sunday evening. It was a total treat to spend time building and chatting with Lamp Post Group’s Lucky and Ben.

Dear Ian, thank you for your long arms, Sincerely, me & my love of selfies. With Ian and the loveliest lovely Anna.

Anna’s talk Django Girls: A Success Story! She has inspired me to host a Django Girls workshop in Atlanta! She shared her slides here. And you’re already following her on Twitter, right?

I’m sure you’ve already heard about my adoration for Anna, but I’ll share again, here: she was a huge inspiration for my talk and has been instrumental in my Python learning journey. She is inspiring, kind, and an amazing mentor. I’m so glad she’s in my life!

Photo by Aubrey Howell (@simplyaubs)

Ed Finkler’s talk “Stronger Than Fear: Mental Health in the Developer Community“. I’m so thrilled to share that you can watch it here! The slides are here. Ed’s talk is particularly meaningful to me because, as I shared during my talk, I also struggle with depression and anxiety. I am glad PyTennessee was the kind of conference where we could bring our very real struggles into the room in a tender, compassionate, and constructive way.

Meeting James Dozier and learning that my talk was an inspiration for his new blogging project, Think Code Make! He was also inspired by Aubrey Howell’s (hilarious/amazing) talk “Shitty Code Leads to Pretty Code: Reconciling Development with Reality“. I was SO BUMMED to miss it, but thankfully they were able to record. I’ll post the link here when it is ready! It’ll be one to watch, y’all, for sure.

Meeting Elizabeth Wickes and learning about her Guided Self-Study Lesson Plan for Python. She has put a LOT of thought and effort into teaching Python to folks from non-technical backgrounds and would make a great future speaker (hint hint, conference organizers!).

Lynn‘s keynote Sunday evening. It was great to hear more about her journey and how Spotify uses Python and open-source tools. Plus, she keeps us smilin’.

PyTennessee resource round-up

Since I wasn’t able to attend every talk, I made a list of resources gathered from Twitter for future reference. Let me know if there are others, and I’ll add them!

Resources for fellow Atlantan Daniel Rocco‘s talk “Clean and Green: Pragmatic Architecture Patterns” are here! Includes links to the screecast, slides, and clean architecture resources. I’m glad I got to hear his talk at PyATL, cuz he was up against me at PyTN!

“How to really get git” by Susan Tan: slides here!

A. Jesse Jiryu Davis gave an inspiring talk called “Dodge Disasters and March to Triumph as a Mentor“. I’m so glad he shared a written version of his talk here!

“Analyzing Data with Python” / “Twitter Network Analysis with NetworkX” by Sarah Guido!

Slides and a post for Michael Herman‘s talk “Docker In Action: fitter, happier and more productive“. Oh, and while we’re at it, some helpful resources and tutorials from the RealPython.com team.

Matt O’Donnell‘s slides for “Behavior Driven Development with PyQT“.

A little bit of video of the intensely charming K Lars Lohn during his talk “The Well Tempered API”: Baroque Cooperative Multitasking

Here’s a great blog post from Jamie Phillips about his PyTennessee weekend.

I also made a Twitter list of some of the folks I heard/saw/met at PyTennessee. I’m sure it’s incomplete, though – please let me know if there are others who should be added!

Finally, I had a great time sharing my own story – and cookies! – Sunday afternoon.

Thanks to everybody who came out to listen, eat cookies, ask questions, and just generally be supportive. I enjoyed connecting with all of you!

For those who are curious, my next post to Coding with Knives will be a written version of my talk. Stay tuned!

And we’re back!

I had to take a couple weeks’ break from Coding with Knives and other creative projects because I’ve been dealing with some things in my personal life that have demanded just about all of my available energy. Awesome friends and deliberate self-care means I’m slowly getting back to a place of relative normalcy, but like all things, it’s a process… and there are bumps in the road, plenty of ’em. The key is to stay present and keep moving forward.

LPTHW’s exercise four introduces variables. In this exercise, we print simple phrases with variables inserted:

Zed also has us run Python from the terminal as a calculator, using variable names to do calculations.

Really just not a big deal at all.

So what else is not a big deal – at least, once you have the right stuff? Chopping things. That’s right, today I’m talking my namesake: cutting boards and knives.

First, cutting boards. What are you currently using? The countertop? Decorative glass? The plate you intend to serve your food on?

Over the years, I’ve seen all of the above – and each time, I shuddered. If YOU answered YES to any of the above, you should not feel ashamed or judged, but you should stop cutting things immediately, run to a store with a home goods department, and purchase a set of bamboo cutting boards.

I love bamboo because it’s renewable, cheap, sturdy, and easy to clean. Bamboo is also incredibly strong! I have been using the same suite of bamboo cutting boards for years with a very sharp chef’s knife and they are in fantastic condition. As an added bonus, I’ve found that bamboo does not seem to retain as valiantly as my solid wood cutting board the odorousness of things like garlic, onion, and ginger. This is helpful when you use these ingredients frequently.

Please note that while my cutting boards have seen all manner of plant matter, from kohlrabi to wakame, I do not handle raw meat in my kitchen (or ever) so I can’t speak to that experience.

Moving onto knives!

There’s a reason you see the same knife in all of my pictures:

Chiffonading collard greens

Slicing into spaghetti squash

Dicing roasted peppers

This is because for 98% of tasks – cutting, slicing, dicing, and mincing – I use the same high-quality chef’s knife: a 185mm Super Series MAC SA-70 Utility Knife.

A chef’s knife is by nature a multi-purpose tool, intended to help you accomplish a variety of tasks in the kitchen. It’s absolutely worth investing in one and paying to have a professional sharpen it. (Yes, I’m in the camp that suggests you don’t sharpen your own knives – deal.) I use MAC knives because once upon a time my friend Matt let me borrow his to prepare multi-course meals for two hundred people and I fell in love. I received my own as a gift in 2010 and have been using it almost daily since. Here’s a link to see the series and another to consider purchasing.

The MAC Knife is not inexpensive, and I’m convinced that anyone who cooks regularly should make the sacrifice of $100 or so for a decent tool. But if, for whatever reason, you are not able to spend that kind of money right now, I suggest a suitable alternative: the IKEA 365+ GNISTRA Vegetable Knife.

Compared to my svelte MAC knife, it is a bit heavier and clunkier, but make no mistake: this $15 bargain is a versatile knife that takes well to professional sharpening. And it’s better made than you might expect. The first time I had a professional sharpen my knives, he of course oohed and aahed over the MAC. But when I pulled out the IKEA knife, he admitted that it was much better quality than he anticipated.

So there you have it! Cutting boards and knives: essential. Make it happen!

Howdy folks. Today I’m writing to you from Dr. Bombay’s Underwater Tea Party (real name) where I just finished Exercise 1: A good first program.

To be honest, this is the fourth time I’ve worked through this exercise. I started in early 2012 and have had several stops and starts with LPTHW since. (But this time it’s stickin’.)

I was surprised when I actually made some mistakes! I realised I’d used the GUI to create a “Learn-Python” folder in my home directory but I hadn’t cd’ed into it before trying to run my “good first program”. But when I tried to cd into it, it wouldn’t let me! A-ha: “cd learn-python” won’t work, because Python is case-sensitive. Little slip-ups, but important to the learning process.

It feels weird to call ex1.py a “program” because all I’m doing is printing some lines. In the extra credit Zed has us comment out our working using #, but that’s really the extent of this chapter. I feel like a “program” should do something more exciting.

While we’re here, let’s chat about something similarly basic in the kitchen: roasting vegetables.* It’s easy and something you should feel empowered to do.

You can roast eggplant.

You can roast peppers.

You can even roast whole pans of stuff.

There are too many blog posts on the internet about roasting red peppers, heads of garlic, acorn squash, etc. I don’t intend to add to the bulk by making a simple concept fussy, or insisting that every vegetable deserves its own special treatment. Sure, you can do that if you’d like — and sometimes it’s appropriate. (Feel free to Google if you’re curious.) But for your average just-got-home-from-work, wanna-be-doing-something-else, need-vegetables eater, what I am about to explain is more than sufficient.

Roasting is not complicated. The most you’ll have to think about, really, is how long you want to roast a given food. By this I mean: tender foods (like eggplant, summer squash, very young fennel) will need less roasting time. Firmer foods (potatoes, winter squashes) will need a little more. If you’re just roasting a sheet pan of acorn squash, it’s going to take somewhat longer than a sheet of asparagus. Acorn squash takes about an hour. Asparagus takes about 25 minutes.

But here’s the thing! You can actually roast firmer foods with more tender ones, as long as you cut them into smaller pieces so they’ll cook faster. See the example above: those are fairly small potato pieces (they’re also an especially tender variety, hence my choice).

Cutting pieces of food uniformly is a basic cooking skill you should practice. Chefs don’t just do it because it looks good. It also ensures that your food cooks more evenly.

So! Roasting!

Here’s how I do it:

1. Prep vegetables. (Clean, core, chop uniformly, etc.)
2. Pre-heat oven to 400 degrees Fahrenheit.
3. Gather all vegetables in your largest bowl. Drizzle generously with olive oil and sprinkle with salt and pepper.
4. Spread the vegetables out onto a heavy-duty rimmed baking sheet (jellyroll pan).
   1. Note: you will not need to grease your pan because you have already generous coated all of the veggies with oil.
5. Roast for 35 – 45 minutes total, removing them from the oven every 15 minutes to stir (or in the case of large pieces, turn over).
   1. I recommend using the thinnest metal spatula you have to scrape up all the roasty goodness.
   2. Larger pieces (like halves of peppers) can be negotiated with tongs.
   3. Tender foods will take less time.
   4. Firmer foods will take more. Adjust as needed.

I like to play around with a combination of olive oil, soy sauce, maple syrup, and dijon mustard for potato-and-onion-based roasts. Try it!

*We are not having a conversation about how eggplants and peppers are technically fruits.

Recently I took off to Chattanooga to spend the day drinking coffee, playing cards, eating good food, and… learning Bash? Yep. Turns out craft coffeehouse Brash provides the perfect backdrop for making flashcards (henceforward known as bashcards) and gettin’ down the basics.

Featuring Android: Netrunner. I slay as Andromeda.

a few of the bashcards

I’d already worked through the Command Line Crash Course‘s terminal-based exercises, but I wanted some practice drilling. Thankfully my beau was willing on the long, slow drive back from Chattanooga. I didn’t have too much trouble, since I recognized many of the terms from my first attempt at Learning Python the Hard Way. Only xargs made me go argh! I definitely feel like I have a good enough handle on the basics to move on to the first chapter, so I’ll cover it in my next post.

For today’s cooking tip, I want to share a few cooking conversions and measurements that I use all the time. Like Bash above, just memorizing these will make your life so much easier. Say you’re making a salad dressing and it calls for all kinds of “tablespoon this”, “teaspoon that”… and you want to triple the recipe for a party. Are you really gonna stand there and carefully measure out 9 tablespoons of sticky tahini, when you could just do a generous 1/2 cup* and call it a day?

Here are the measurements I use all the time:

Dash = 1/16 of a teaspoon. This is nothin’. This like a dustin’. When you see a dash of something, consider that it’s basically an optional ingredient. …Just kidding. …sorta.

Pinch = 1/8 of a teaspoon. This is quite a bit more than nothin’, so don’t discount it. It’s okay to literally pinch a bit of the spice and toss it in (to your mise en place, remember?), but if you want to measure it out, that’s okay too. (If you’re working with cayenne or another pungent spice you might actually prefer to measure it.)

One teaspoon = 1/3 of a tablespoon.
Two teaspoons = 2/3s of a tablespoon.
Three teaspoons = 1 tablespoon.

It’s so helpful to know the above when you’re reading a recipe that says “5 teaspoons” (seriously, I hate that). If you see “5 teaspoons”, just think 1 tablespoon plus 2 teaspoons (or, if you’ve got some experience at eyeballing, a 2/3s-filled tablespoon).

Two tablespoons = 1/8 cup.
Four tablespoons = 1/4 cup.
Eight tablespoons = 1/2 cup.
Sixteen tablespoons = 1 cup.

When I see a recipe that calls for four tablespoons I know they need an editor. Quarter cup y’all!

Your 1/3 cup measure go missing? No big deal. Just measure out 1/4 cup plus 4 teaspoons (or 1/4 cup plus 1 tablespoon plus 1 teaspoon). Note: the internet believes that 1/3 cup equals five tablespoons. This is not true, but it works for most purposes. 1/3 cup is actually slightly over five tablespoons (hence the +1 tsp above).

Doubling a soup? Memorize these:

Pint = two cups
Quart = two pints (4 cups)
Gallon = four quarts (16 cups)

So there you have it: a beginner’s guide to some of the most common and helpful cooking conversions. While I highly recommend that you memorize the above, you can use Google if necessary. Just specify what you’re looking to convert (i.e., “How many ounces in a pint”) and Google will help you out.

Googling: not just for learning Python!

*technically 9 tablespoons = 1/2 cup + 1 tablespoon, but I’ve been in this gig long enough that I’m lazy. I do “scant” for just under a given amount and “generous” for just over.