A coding kata is a way to practice something to get better at it — just like the karate counterpart. I also use katas to get familiar with new tools and approaches.
One of the last tasks on the agenda before shipping my books is to make the formatting support the material instead of making it harder to understand.
Softcover is nice because it lets you stay mostly in Markdown, but you can drop in LaTex for more advanced formatting needs. I started by using inline code formatting for everything from function names, API calls, code snippets, to file paths. For UI instructions, I was using double quotes and a mixture of inline stuff.
In 2013, I learned I could take a break. In 2014, I learned to set my own course.
I led a team of Android developers, started a consulting business, ventured into startup land, joined the board of a non-profit (we opened computer labs in Mexico and Morocco), expanded the Google Developer Group (GDG), and started hosting on AirBnB.
I was free to spend most of June abroad and saw the northern lights in October. I spoke in Stockholm and Amsterdam. I attended Droid NYC, Google I/O, and two GDG conferences. I mentored at LadyHacks and inspired others to speak at conferences.
Excited to see this foundation grow in 2015.
If you are already a programmer by trade, an excellent resource is Professional Android 4 Application Development.* It set a high bar and teaches Android in an approachable fashion.
I got my start with version 2, in the time before
Fragments and tablets. The book was updated for Ice Cream Sandwich, but a lot has changed in the last few years. Hopefully there’s a new version on the way.
Have you wanted to get started with a conference speaking career but don’t know how? It’s a lot easier than it appears on the outside!
Own Your Expertise. We are all experts of our own experience. Sharing our path, passion, and knowledge inspires others. We don’t need to know everything about a topic to have something valuable to say!
I was inspired by three different sources to give a talk at Barcamp this past Saturday.
First, I attended the inaugural Write/Speak/Code conference last year. During the Write day, we learned how to own our expertise and write op ed columns (something that’s on my short term goal list). The Speak day was all about the mechanics of drafting and submitting talks. (Pam Selle and I spoke on the Code day about feminist models for open source participation).
Continue reading Barcamp Philly 2014
I gave a workshop today at Barcamp Philly that heavily drew from Julie Pagano’s workshop and slides. I reorganized the time frame (her workshop is a whole day and walks you through many more steps of conference presenting) and made it fit in a 45 minute time frame.
Have a short deadline? Boss breathing down your neck?
Don’t start prowling github just yet! Work through the following steps first.
1. Determine what you need.
Sounds simple, but so often we skip this basic step.
When Women Stopped Coding is a (mostly) non-depressing look at what was happening in the 80’s and 90’s to contribute to the plummeting number of women in computer science. In particular, I hadn’t thought deeply about the emergence of computing have and have nots.
My parents didn’t buy a computer for the home. Luckily I had access to computers at my friend’s homes and was on the Internet pretty darn early via Tallahassee Freenet & BBSes in 1995. I went to nicer middle and high schools that had technology classes (though not programming, just typing). I often frequented the library to get online. I loved finally having 24-hour access to the computer lab in my dorm during my first year of college (1998).
Frustrated by fragments? Intrigued by dependency injection? It may be tempting to switch approaches to solve your current pain.
Don’t throw away that code just yet! Think through the following questions first.