Welcome to my blog! Please keep these three things in mind:
1. Everything on my blog is my point of view and does not represent the view of any company I've worked for, past, present, or future.
2. If you want to respond to anything I've written, use my Contact form.
3. The previous version of my blog is partially available online, but I put the best parts of it in my first book, Minority Tech: Journaling Through Blackness and Technology. You should buy it. It's fun.
I became a Certified Scrum Master (CSM) in 2013, and I am in the process of applying to be a Certified Scrum Professional (CSP). One part of the application is an essay about my experience using Scrum. I still need to gain more Scrum Education Units (SEUs) to qualify for the CSP, but I wanted to share my application essay:
Apple is widely rumored to announce a smartwatch at their event on September 9, 2014. If true, the company will join a market already crowsed with offerings from Pebble, Samsung, LG, and other players. However, Apple entered a crowded field with the iPod and almost immediately won the MP3 player market. Apple also entered a crowded field with the iPhone and soon dominated. The iPad faced a field with many tablet computers, but it essentially created the category. Do you see a pattern here?
I have the original Pebble, and I wear it every day. It's a great watch, robust (it survived my participation in Tough Mudder last year), and the notifications on my wrist are nice. However, I'm an early adopter so I know that Pebble style watches will never become mainstream. However, if companies can produce stylish smartwatches, I think those devices will catch on. The New York Times recently ran an article stating that kids going back to school are more interested in their tech gear than clothing. Millenials and Generation Z are starting to see tech as a statement of who they are, and I think style will win the day in the smartwatch category. I think Apple is well positioned to compete on style.
A friend recently asked about things to do in Maui, and, since my family was just there a few months ago, here's my reply to her:
I wanted to share the list of places my family and I visited in Maui when we went a few months ago. I hope it's helpful for your upcoming trip.
* I'm not sure where you're staying, but you'll probably drive a lot. If you're not staying in Lahaina (on the West side of Maui), then you will probably drive to Lahaina often.
* If you like nice pools and beaches, then the resort hotels in Lahaina are a great option for you. We wandered from hotel pool to hotel pool, and no one harassed us or asked if we were guests. Several hotels have spas if you're into that sort of thing. :-)
* Whale season had ended so Maui had just started letting water activity companies (wave riders, para-sailing, etc.) resume operations when we were there. If you're into water sports, then they may still be available if whale season hasn't started again by the time you travel to Maui.
* We started the "road to Hana", but my wife gets car-sick fairly easily and the switchbacks were too much for her. So, we had to turn back. Also, Hana is on the East side of Maui so the road is usually a cloudy and rainy drive to a cloudy and rainy part of the island. If you don't mind road trips (where you sometimes fear for your life), then it may be worth doing. If you do try the road to Hana, stopping every few miles and hiking or visiting one of the beaches is a good use of the time you'll invest in the trip. Hana is the destination but the journey is the point.
* There are certainly more restaurants and places than I listed below. These are simply the food establishments and locations that I personally experienced and enjoyed.
* Da Kitchen (very close to the airport; not a bad place to have your first meal in Maui; large portions - 425 Koloa St. #104 Kahului, HI 96732)
* Mama's Fish House (expensive but great food, location, and atmosphere - 799 Poho Pl, Paia, HI)
* Flatbread Company (great natural pizza; near the airport - 89 Hana Highway, Paia, Maui, HI)
* Dazoo (71 Baldwin Ave, Paia, HI 96779)
* Ululani's Shaved Ice (I recommend trying a Hawaiian shaved ice at least once if you've never had one - 819 Front St, Lahaina, Maui, HI 96761)
* Kimo's Restaurant (845 Front St, Ste a, Lahaina, Maui, HI 96761)
* Koa's Seaside Grill (839 Front Street, Lahaina, Maui, HI 96761)
* Maui Ocean Center (a surprisingly good aquarium)
I just transferred my domains from GoDaddy to Google Domains. I was invited to join the Google Domains Beta, and I am quite pleased to leave GoDaddy behind. Here's why I made the switch:
One important reason I made the switch was GoDaddy's exploitation of female sexuality in their advertisements. We've all seen their Super Bowl commericals, and I'm glad to do business with a domain registrar that doesn't use sex to sell their products.
I enjoy public speaking, and I have been fortunate to have many opportunities to speak on a variety of topics. A friend reached out to me for advice about giving her first talk. Here was my response:
Thanks for reaching out. First, I want to say how proud I am that you are speaking about technology, especially when it comes to getting more women in technology. The only way to have true innovation in technology is to bring diversity of thought to the industry.
I have a few quick tips that have worked well for me in public speaking:
Here's a video of a friend of mine named Adria Richards giving a TEDx talk about women building careers with code. I think she did a great job of using visual images in her talk, and she laid it out well.
I hope that helps. If you need more information, please feel free to reach out. I know you'll do great!
I have 658,287 lifetime flight miles (and that's just with United Airlines) so I know quite a bit about travel. As a techie, here are my must-have travel gadgets:
Clamcase iPad Keyboard Case: When I'm not travelling, I use my iPad as a media consumption device to watch movies, play games, or keep up with the news. However, when I'm on long flights, I've found that encasing my tablet into its Clamcase Keyboard Case lets me use it to produce content. The keyboard is comfortable and gives me the ability to navigate complex spreadsheets, respond to emails, and, of course, work on my Great American Novel.
Wacom Bamboo Stylus: While the iPad is responsive enough to not need a stylus, I like to doodle in the air every now and then. So, I've found that travelling with a stylus lets me nurture my inner artist even when I'm 30,000 feet in the air.
Mophie Juice Pack: I travel with a lot of gadgets, but my phone is the one device that I can't afford to let it run out of juice. The Juice Pack functions as both a protective case and a power source for my Samsung Galaxy Android phone. The Juice Pack has allowed my phone to even survive an eight hour flight from Houston to Honolulu!
NapAnywhere: I used to use those U-shaped travel pillows, but I recently switched to NapAnywhere. It's so much better! It even makes sitting in a middle seat enjoyable! I've even been tempted to give it to the person napping next to me when their unconscious head starts slipping toward my shouldar.
Uber: This is an app that makes arranging a car safe and easy. I simply display my location and a car arrives within minutes! Since Uber stores my credit card information, I can just get out of the car at the end of the ride.
I routinely hear performance reviews from managers that sound something like this:
"This team member is doing a bad job. I constantly have to give guidance, monitor, and make corrections to their work."
My response, although rarely spoken out loud is, "Yes, that's your job." The job of a manager is manage, but most managers prefer to report. Instead of managing a resource, they report on the resource's performance. Few managers understand this. Let's use the analogy of a car. If you pressed on the brake pedal, and a number popped up on your windshield displaying your current speed, would that be an effective braking system? Or, if you pressed on the accelerator, and your dashboard displayed your current compass direction, wouldn't that be considered a malfunction? However, despite operating like defective brake and accelerator pedals, we let managers off the hood for failing to govern the performance of their teams.
Managers are supposed to decrease the weaknesses of their teams while increasing their strengths. Far too many managers I've encountered simply let their teams function in the way that they received them. Therefore, if a manager gets a great team, then the team produces great work, and we think that the team had a great manager. However, that is often not the case. Great teams tend to produce great work irrespective of the manager in charge of the team. Conversely, if a manager receives a poor team, then the team, unsurprisingly, produces poor results. Managers, in this situation, tend to blame the team and almost never admit that they are bad managers.
Effectively managing a team (instead of simply reporting the team's performance) requires the ability to deeply analyze each person on the team and understand how to make improvements. This is hard work which is why most managers avoid it. You have to understand how each person receives feedback, create performance improvement plans, and conduct regular checkpoints to measure progress. While every team member has to own his or her career, the manager has to be fully invested and accountable for the improvement of everyone on the teams they lead.
Far too many managers are content to simply be reporters. The only way to improve the number of great teams in the workforce is by teaching managers how to steadily improve the greatness of their teams no matter the condition in which they were received.
I finished Learn Python the Hard Way, and it was a good book. However, it is indeed the hard way to learn Python. Zed minces no words in voicing his disdain for other ways of learning how to program, and the text often says, "Go learn about that" for any subject in which the author has no interest. However, that subject may be critical to helping a student understand computer programming.
I started another book called Think Python: How to Think Like a Computer Scientist by Allen Downey, and it is a much softer way of learning Python. The author introduces concepts and then builds upon them. As someone who has taught technical courses, I am a big believer in the need to understand core concepts before trying to create something. So, I am enjoying Allen's book more than Zed's, but I appreciate Zed's approach to getting things done.
Some people teach swimming by throwing students into the pool while others get into the water and swim alongside the people they're trying to teach. I much prefer the latter so I'll recommend Allen's book to others who want to learn Python.
I recently decided to dust off my programming skills and learn a new language. My undergraduate degree in electrical engineering required me to take courses in languages like C, and I've programmed during my career in languages like Perl, PL/SQL, and some proprietary languages. However, after being promoted to management several years ago, my programming responsibilities dwindled. Instead of being a programmer, I had to manage teams of programmers.
Despite not needed to program as a job requirement, I have found that knowing how to code is extremely valuable when working with coders. First, you gain a measure of street cred if programmers know you have walked in their shoes. Second, you can know if a programmer is overestimating or underestimating how long it will take to finish a feature if you have experience implementing similar features. Finally, knowing that I can, if needed, roll up my sleeves and contribute to the code base is immensely empowering.
I didn't think that returning to the languages I knew was the right way to go because several more modern languages have emerged since I last had to seriously program. After doing some research, I narrowed it down to three: PHP, Ruby on Rails,or Python. I chose these three because they were widely used, could solve a variety of different problems, and could quickly get me to my main goal: working code.
I felt that PHP lacked the structure I wanted in a language, and I was concerned about the numerous security vulnerabilities. Ruby on Rails almost won me over, but I eventually selected Python because of its power and readability. Some may not like its reliance on white space for formatting, but I see this as a feature instead of a flaw.
I'm working through Learn Python the Hard Way by Zed Shaw, and I'm up to Exercise 42. I've enjoyed writing Python code because it is very straightforward. Instead of trying to find clever or elegant ways to accomplish a goal, Python encourages the most reasonable approach. I'm an Occam's Razor kind of solution finder so Python works well for me.
I just finished a Google Hangout with the students in a course called Leadership in Digital Contexts that my friend Kaia Shivers teaches at Rutgers University. I shared these points:
1-10 of 13