Posts Tagged ‘lists’

h1

Brother gifts

December 24, 2015

Another Christmas Eve is upon us so it must be time to get gifts for my brother. As usual, I’ll be getting kindle books and, as usual, I don’t really know what he likes. I know he very much enjoyed The Martian last year and was pleasantly surprised by Ken Jenning’s Maphead (so was I, actually).

This post makes more sense if you understand that I don’t really know my brother. Sure we grew up in the same house but had a very Bart and Lisa Simpson vibe: sibling rivalry at its worst. But I do care about him even though I suck at showing it; I fret about how to show that through books.

There have been some Kindle sales so I bought a few books earlier in the year when they were cheaper and set them to deliver today.

  • Statistics Done Wrong by Alex Reinhart: Statistics are really important in today’s world. It isn’t just about scientific significance, reading the newspaper without being able to see how to lie and hide information through stats is critical. I thought this was a good intro book, quite amusing for a topic that is usually a slog.
  • The Annotated Build-It-Yourself Science Laboratory: This was written in the sixties by Raymond Barrett, a teacher and museum exhibit developer. It is a great book but showed its age (you can’t go to the local pharmacy and pick up mercury anymore). So Windell Oskay updated it to reflect modern safety practices and some different resources for trying out the experiments. I was trilled to see this book on sale since it is a pretty amusing read and because I had Windell on Embedded.fm (124: Please Don’t Light Yourself On Fire) so I could mention my podcast to my brother.
  • The Quantum Story: A history in 40 moments by Jim Baggott: I almost always buy books I’ve already read so I can believe I’ve done the due diligence to know he’d like them. But this one was on sale and so I got one for him and one for me. I’m about half way through and put it down… it is a good mashup of physics, characters, and history but the short-story-like nature makes it easy to put down and pick up. I’m glad I got it ($2!) but it isn’t Maphead.
  • Code Name Verity by Elizabeth E. Wein: This was the best book I read this year. Don’t read the summary, don’t read the reviews about it being sad. Just go read the book. I hope he likes this one though it is a bit of an outlier as far as genre goes.
  • 10% Happier: How I Tamed the Voice in My Head, Reduced Stress Without Losing My Edge, and Found Self-Help That Actually Works–A True Story by Dan Harris: I picked up this book about meditation earlier in the year, having heard Dan Harris on an NPR show being open about his recreational drug use. It was a good book. I liked many parts of it and was only irritated by a few. It didn’t make me start meditating but it might have made me more mindful, at least for awhile.

Now I have to wade through my ideas to figure out what else to get him.

I think yes to Boneshaker by Cherie Priest. It was my introduction to Cherie Priest and still probably my favorite of her books (though I Am Princess X was fantastic but it is a young adult book targeted at women).

I just started The Moth, written versions of some of the stories told on The Moth Radio Hour. I really like the radio show, whatever they are about they are good stories. The ones I’ve read so far share the same level of goodness so I’ll take a chance that it continues despite the preface, forward, and introduction chapters all being long and less interesting.

In that same vein, I noticed that Terry Gross’ All I Did Was Ask: Conversations with Writers, Actors, Musicians, and Artists is also on special this month. I’ve been wanting to read that so one for him, one for me.

So that covers all the on-sale things. But I can’t buy only on-sale gifts. You can return Kindle Gifts and get the credit. And I’ve told him I don’t mind him doing that but it seems like all <$4 is odd. Despite the amount of time (and, seriously, all sorts of fretting), I should get a couple books that maybe come out of the normal bin.

I quite liked Brandon Sanderson’s Steelheart, a sci-fi/dystopian/superhero book. I got him the Mistborn trilogy last year. The packing is different enough that if he hated that, he still might like Steelheart (though if he liked that he’ll probably also like Steelheart).

I haven’t read The Peripheral by William Gibson but it people have been saying it is the best thing he’s written since Neuromancer. I’ll send this as a little cyberpunk to balance out the steampunk.

Realistically, this is probably enough books for my brother. Though I asked a friend for suggestions and he suggested Microserfs, The Peripheral, and Suarez’s Daemon. That’s the second person to suggest Daemon to me in the last two weeks. You know, I think I’ll just get that one for myself instead of my brother. And given the news that Microserfs was better than Ready Player One, well, that’s going high on my wish list.

Clearly I’ve stopped buying gifts for my brother and devolved into something else.

One more for him because I think it is neat: Thing Explainer: Complicated Stuff in Simple Words by Randall Munroe. The creator of the truly excellent xkcd comic and the hilarious What If blog wrote a book explaining complicated things in the most common thousand words. It is a strange blend of “huh” and “neat!” so I’m hoping he enjoys it.

h1

Women-in-tech activities

July 17, 2015

I go to the occasional women-in-tech things. I’ve been to Grace Hopper, once as attendee, once as a speaker/manager bringing her team. I read Systers for years but don’t currently, it is just too much sometimes.

Actually, that sums up my feelings about women-in-tech events pretty well: it is just too much sometimes.  And yet.

I like to attend women-in-tech things because it is nice to see women happy as engineers. Too many times, I hear the horror stories. But there are many people, many women, untouched (or only slightly touched) by the trolls, stalkers, and jerks of the internet. I like to be reminded that it isn’t always awful.

And I go because I get a little lonely in my job sometimes. I like to connect with people who might be in the same boat, maybe offer some advice to those more junior in their career, maybe receive some advice from those more senior.

I also go to find podcast guests. I’m not shy in trying to get a gender balanced podcast despite the lack of gender balance in embedded systems. That means I have to search a little more, work a little harder to get women guests. So I go to women-in-tech meetups hoping to find people.

Though, I’m fairly terrible (stressed) in crowds and I find that seems to be getting worse as I get older. I can pretend to be an extrovert for about 4.5 minutes (8 with alcohol). Then I get jittery and want to throw up. Reeeeallllly Jekyll and Hyde-y.

I went to an event this week. It was ok. There was no alcohol. And the demos (from the hosting company) were done by men (though they were nice, it just seemed like a missed opportunity to highlight some women’s achievements). At least the talks were done by interesting, engaging women… though they were a little long. As someone there for the networking (4.5 minutes of it anyway), I don’t want detailed technical presentations.

It got me thinking about what I’d want to do if I was putting on a women-in-tech event. So let me write these ideas down, maybe it will plant a seed for later.

1. There shall be alcohol. All networking events should have beer and wine.

2. Food will be primarily vegan. Because, crap, I’m tired of not being sure what is safe for my socially-nervous and vegetarian stomach to eat. Maybe steak strips or meatballs too, but everything else will be vegan. Sometimes at these things all I want is a little peanut butter and jelly sandwich. And there will be dessert but it will served later (halfway through), not set out with the food. Dessert doesn’t have to be all vegan.

3. There will be seating but not quite enough of it.

4. For a 3 hour event, there will be four to six 5-minute talks, three at T+30min hour, three at T+65min. The goal of the talks is to create discussion and getting people to talk to each other, not to give speakers platforms. The talks act as ice breakers, the speakers will know that.

5. Badges will have first names only. There will be small stickers for different interests. If it is hosted by a company, they will have small stickers so it is easy to pick out people who work there.

6. There will be different themes in different parts of the room. They will be clearly marked: “I’d love to meet you” (seating and food), “We’d love for you to join our conversation” (seating), “We’re happy in our conversation, give us a minute” (tables but no seating). People won’t have to declare themselves, just stand in the right place. Ok, this one is sort of dumb. Maybe scratch it out and put in a networking/mixer game thingy.

7. It will be a women in tech focused event but open to anyone who wants to support getting more women interested and retained in engineering, math, technology, and science. You do not have to identify as female to come.

8. There will be a few people who are asked specifically to act as hosts, who spend the evening meeting people then introducing them to each other.

9. We will make some horrible mistake against feminism (giving out lipstick, having men do demos, handing out hot pink rape whistles) so that everyone can be aghast at something.

Oh no! We’ve reach the cynicism level. Don’t go deeper, it gets very dark in there.

I’ve been to great meetups, both gendered and not specific. One GirlGeekDinner was fantastic, another one I was lost at. The OSHPark Bring a Hack Maker Fair after party is pretty amazing: Laen gets people there and mingling with each other. Some of that is because they are fascinating people and because we’re told to bring something which creates an icebreaker. But there is something else too.

I don’t know what that something else is. I suppose if I did, I’d bottle it and make millions.

Anyway, there are many women-in-tech things and something always goes oddly but I’m not ready to give up on them yet. Though I’m not ready to throw my own either.

 

h1

So many posts, so little time

February 2, 2015

I have been BUSY lately. And social. I’ve got so many posts in my head but not quite enough time to get them all down. So I’m going to write teasers in hopes that will force me to finish a few.

  • Design Con: fun or just connectors
  • Tindie meetup: I feel like I’m never going to catch up with all the nifty hardware out there
  • Being a Unicorn (my notes and reflections on this session)
  • Doing Self Evaluations (also from She’s Geeky)
  • She’s Geeky accidental session on asking a recruiter for money without seeming greedy (aka apologies to Twilio for what I did)
  • Snow White Introduction to Stock Options (part of previous, turned out to be pretty funny)
  • (On creeping:) Why I won’t meet you in a hotel bar to discuss business
  • Grading clients: why these clients get a C- while those get a D- and those others get a B+
  • Ideas for monetizing the podcast (well, one idea… which I really should discuss with Christopher…)
  • Thoughts about disagreements with guests on the podcast
  • Getting interviewed by a ten year old (Arduino Alarm blog)

Ok, I’ll finish my to-do list (and my paying work) then start writing one or more of these.

h1

Tinkering for dummies

January 24, 2015

I received an email:

I’ve listened to a few podcasts and now am officially a fan. I’m curious about “tinkering” for dummies

I realize that I like to tinker but always run into the reality that my technical skills don’t match up with my creativity.

I am wondering if you would suggest a pathway of least resistance for someone who is interested in tinkering. 

Time is always a constraint but I am serious about learning how to code and also learning about embedded systems but not sure if learning python for example is the best way to start.

This seems like a great question, one I’m sure other people have.

However, I’m a terrible person to answer it because I come at the problem of tinkering from exactly the opposite direction. Since programming is my job, tinkering can be difficult because it feels like work instead of play.

Still, I want to encourage the writer so I’ll try to answer. I invite you to suggest other things in comments.

I think the the very short answer is buy a kit. A kit means you’ll get something that probably works and some instructions. Then you can tweak it to be more along the lines of what you want.

And, in general, I think the path of least resistance is Arduino. Their community and system is set up to teach you things (and to hide the tricky details). It started out as a way for educators and artists to approach technology so they don’t expect you to know a lot of coding. There are many Arduinos (the UNO is my fav) so the next question is what do you want to tinker?

Learning by doing is great but difficult to maintain if you don’t have a direction. Self motivation is much easier if you have a goal, ideally an achievable, amusing, and share-able goal.

Say you want to make a watch or small desk display, start with the MicroView (and programmer). If you want to go all out (or you really have no idea where to start), get the Sparkfun Inventor’s Kit. With the MicroView, you get more tutorials with hardware in the inventor’s kit. Without the MicroView, you still get a wonderful grouping of sensors and lots of tutorials (and an Arduino board).

On the other hand, robots are awesome and seeing something move is deeply satisfying. The Parallax BOEBot (“Board of Education” Bot) is educational (and fun). It was designed for high schoolers so you’ll likely feel brilliant and idiotic in turns (c’mon, you remember being a sophomore, right?). You can get it from Parallax more cheaply but you have to build more of it yourself. (Also, you may need an Arudino UNO for those kits to add smarts to your robot.)

As you start to tinker, decide what you want to do with your limited time. Building from the ground up is an advanced exercise, often leading to frustration. Toddling, baby steps are more fun.

But what if you want light up shoes (or bike helmet)? Lights are an awesome way to get hooked on tinkering,* there are so many beautiful blinking patterns. For that, you probably want to look into the Flora system (oh! they also have a budget pack). It is designed to be wearable which is pretty neat.

Do you have annoyances in your house? Something that would be better if you could assure yourself from work or phone? Maybe knowing that the garage was down, the stove off, or the door locked? For this, I’d suggest Electric Imp (and you’ll need the breakout board as well). It connects to WiFi well and is straightforward to program. It isn’t quite Arduino easy but there are lots of tutorials.**

Finally, do you want to make a big system? Like a balloon that can take pictures and use a GPS and then connect to your home network? While I like BeagleBone Black for engineering use, I’d suggest starting with a Raspberry Pi. These are both little computers, cheap enough that you can blow one up without feeling too guilty. The Pi is designed to be a learning environment and there are many excellent tutorials. The Beagle has an excellent community as well so it may be a toss up between them. And if you’ve already started to learn Python, well, these are the boards for you. They’ll let you use Python, explore Linux, and get some hardware experience without ever worrying you’ll run out of RAM or processing power. If you get a touchscreen (like this one for BBB), these small computer feel like, well, small computers: infinitely flexible.

Which brings me to my next point, once you have a direction, look for  a tutorial for something similar. Even if you aren’t building something exactly the same. For example, if you like the look of MicroView and want to try making a watch, even though Wordy is a ring, my tutorial on building it may give you ideas.  Look at the “Learn” sections on Adafruit and Sparkfun for ideas if you don’t have a project in mind. These companies (as you may have noticed from the above links) sell tinkering hardware. They write tutorials to keep you engaged (so then you buy more hardware). You may also find inspiration from Hackaday and Make. You can document your project on Hackaday.io, I’ve been pleased at the niceness of the community there.

Tinkering from scratch without a guide is a like baking cookies without a recipe. If you are experienced, it is completely possible to start with a blank slate. I know from experience and reading cookbooks that cookies should usually have between 1 part butter, 2 parts sugar, and 3 parts flour to 2-3-4 (b-s-f). I can make almost any cookie I can think up. But as you start out, some guidance to success is hugely important. Otherwise you end up with Strawberry-Mint cookies*** and everyone is very disappointed that the lovely promise turned into, um, that.

My final word on getting started tinkering: don’t feel guilty when you stop for a weekend or two. This is for you, it is your hobby. It might be educational but it isn’t required for life. The less guilt you feel, the more likely you are to come back to it when you get interested again.

*  My first tinkering project involved lightup high heels. The second involved halloween pumpkins lights (blue to purple flickering “candles”).

**  Heehee, I wrote that tutorial so total bias there.

*** Yes, that happened, ok? It was an accident with the mint and vanilla bottles looking similar. Quit laughing. Aw, to heck with it.

 

h1

2014 Year-end Review

January 4, 2015

I read Cation Designs blog and she did a year-end review. It made me think about my advice that people who often feel like impostors should do self-reviews. Creating a well considered analysis requires us to consider (and focus on) the real accomplishments instead of the failures (real or imagined).

Cation is a sewing blog. This is not. Reviews are reviews though.

I suppose that means I’d best get started.  While the categories are top 5, there is no ordering within the buckets.

Hits

  • Podcast: we did 50 episodes this year. Occasionally, it was a chore but more often it was a great way to meet interesting people. I’m pleased (and occasionally startled) at how it has grown.
  • I did a white paper for a client. It was a month of incredibly thinky work but not a lot of code (just the odd bit here and there to test ideas). I really enjoyed the in-depth thinking required.
  • Making Hugh and Maxwell are-you-ok widgets as a collaborative project. I liked working with Elizabeth.
  • The Hackaday Prize judging was extremely educational for me as well as being fun. This came about because of the podcast so that’s an interesting loop-back. It also makes me want to do more projects myself.
  • I’ve kept up the blog even though it is something I do almost exclusively for myself. This is where I practice writing and I’m happy with myself that I keep practicing. My output has been a bit uneven but there was at least one post every month. Note that there were some other posts: on element14 (paid), Sparkfun tutorial, and on Hackaday (recent projects).
Month Jan Feb Mar Apr May Jun Jul Aug Sept Oct Nov Dec
Posts 1 1 9 9 7 1 2 4 3 2 6 9

 

 Misses

  • I enjoyed building Maxwell but, as a monitor, he’s a failure. His network has been flaky since we got a new router (as have our other Electric Imp devices) and I ignore his whiney emails (exactly what I shouldn’t be doing). Plus, I forget to pet him. I’m not sure this is the right path for this sort of monitoring (maybe fridge mounted would be better).
  • I spoke in two sessions at EELive last spring, being the sidekick for Jen’s BIA teardown and then my own presentation on how the vaunted internet of things is not on a good path for consumers. Many things happened behind the scenes that made me nervous (“Your computer cannot work with our AV.” “No, no one is speaking here at that time.” “No, we don’t need to do a real run through.”). I’m a pretty crummy speaker when nervous.
  • We looked in to getting sponsors for the podcast. It wasn’t pretty. I’m not sure how monetization will change how I feel about it. Making hobbies profitable is a good way to lose a hobby.
  • I worked at PARC and found it to be very interesting. I hoped that the place and people would be interesting enough but routers hold no attraction for me. I missed the gadgets something awful.
  • There are several home improvement tasks that I really meant to do. For some reason, ignoring the things doesn’t make them get done.

Highlights

  • Last January, we rented a house in San Diego with friends to celebrate another friend’s birthday. It was not an easy trip for various reasons but it definitely qualifies as a highlight.
  • In the fall, Chris and I rented a house in Santa Cruz and had a very nice vacation filled with whales, dolphins, otters, delicious coffee, and sunshine.
  • Chris and I snuggle on the couch watching TV before we sleep. I like it.
  • I was matron-of-honor at a Las Vegas Halloween wedding. It was just as crazy as it sounds.
  • I had my first birthday party in years. It was fun.

Reflections

  • I need to be better at gauging things I actually want to do versus things I feel I have to. I’ve gotten better at the day-to-day form of this but I still sign up for things in the far future hoping to convince myself it will be fun.
  • People are more important. Even being an introvert, I know this but have trouble remembering. Looking at the Hits and Highlights, it should be apparent that those are there because of the people, not because of the event.
  • My husband is right and I should tell him that more often.
  • I hate it when people leave the area. I felt sort of abandoned. One set of friends had such a long “we’re leaving” time that I sort of stopped believing they were going. It was a sad surprise when they did. Another friend said “we’re thinking about it” and then suddenly (to me) was gone. I know it is good for them (and it isn’t about me) but missing them has made me sad.
  • I’ve been on a path toward focusing on being happy: taking responsibility for and thinking about how to accomplish happiness. I did pretty good this year: learning new things and accepting some things that are not mine to change. But I clearly need a lot more work as I find it difficult to recover from perturbations.

Goals

  • Be kind.
  • Be brave.
  • Be generous.
  • Advertise the podcast and book because they are worthwhile and useful so talking about them may help other people.
  • Do interesting work.

 

We often threaten the dogs with year end reviews but they know their extreme cuteness will mean no punitive action will be taken for their obvious badness.

We often threaten the dogs with year-end reviews but they know their extreme cuteness will mean no punitive action will be taken for their obvious badness.