Mauricio Panelo
/maupanelo
Welcome to my Social Blog
Mauricio Panelo
Jan '22 Cohort
4y ago
I started reading through The 12 Week Year by Brian P. Moran and Michael Lennington.
So far it’s ok. The book should cut out content because there’s a lot of fluff. But there’s one thing I found worth sharing.
The 4 keys to successful commitments:
Have a strong desire for the end result
Do you have a strong desire for the end result of your commitment?
A strong desire will keep you on track to fulfill your commitment. When challenges arise, your strong desire will help you push through them. If there’s no strong desire, then there is no successful commitment.
A successful commit requires a strong desire of the end result.
Identify the core actions
What are the core actions that will help you achieve the desired result?
Once you’ve started the implementation of your commitment, you will take many actions to reach the desired result. But only a few actions are your core actions. These core actions produce the majority of the desired result.
Identify the core actions that will help you reach your desired result, and focus on them.
Consider the costs of the commitment
There’s a cost to making a commitment.
No, I don’t mean just money costs. Costs include time, money, relationships, social life, risks, comfort, and so on.
Consider the costs of your commitment, and choose whether it’s worth paying the price for.
Do the things you need to do
We’ve all had those days where we don’t feel like doing something.
They’re difficult to ignore. But you need to act on your commitments instead of your feelings. If you don’t, you might risk giving up your commitment entirely.
No matter how you might feel in a given day, learn to do the things you need to do.
Mauricio Panelo
Jan '22 Cohort
4y ago
I miss Santa Barbara, and I can’t believe it’s been more than a year since I last set foot in the city. So many wonderful memories. It feels like yesterday I was walking on State Street.
I don’t know why I got “homesick” today, but here’s hoping I get to re-live the memories by writing about Santa Barbara.
Here’s what I miss the most:
Stearns Wharf. I miss parking at the Funk Zone and walking to the iconic landmark. I miss the sensation of walking on the wharf. I miss the fantastic ocean view at the end of the wharf.
The Funk Zone. I miss hanging out with friends at Lama Dog. I miss eating at Mony’s and Shalhoob’s during lunch. I miss eating McConnell's ice cream after a long walk through East Beach and Stearns Wharf.
My go-to restaurants. I miss eating shrimp tacos at East Beach Tacos. I miss the mixed shawarma at Zaytoon. I miss the carne asada tacos at Lilly’s Tacos. I miss the Boathouse at Hendry's Beach.
Hiking. I miss Inspiration Point--my first hiking trail in SB. I miss the amazing waterfall at San Ysidro Falls. I miss trying to find the trail to Seven Falls, but ultimately failing.
Beaches. I miss walking my golden retriever at Summerland Beach. I miss the off-leash area at Arroyo Burro Beach. I miss Campus Point Beach and walking around the UCSB Lagoon.
Surrounding Cities. I miss Isla Vista. I miss Goleta. I miss Carpinteria. I miss Oxnard. I miss Solvang.
I miss the people I met and the friends I made.
One day I’ll be back, and I’ll get to reminisce about all the great memories I made there.
Mauricio Panelo
Jan '22 Cohort
4y ago
Yesterday, I re-discovered Bob Nystrom’s Long Names Are Long blog post.
When he was doing code reviews at Google, he noticed a lot of code creating “identifiers that were too damn long.” So he wrote this blog post to provide guidelines on how to create better identifiers.
Here’s my summary of Bob’s four rules:
1. Omit words that describe the variable’s type or the method’s parameters
It’s redundant to put the type in the variable’s name.
Doubly so when you’re using a statically-typed language. If you’re using a dynamically-typed language, it doesn’t take long to scan the code and infer the variable’s type. Don’t make the reader sound like an echo.
// Bad variable name
var userNameMap map[int]string
// Better variable name
userNameByID := make(map[int]string)The same advice holds for method names. Don’t describe the parameters in the method’s name.
// Bad method name
func mergeUsers(users []User)
// Better method name
func merge(users []User)2. Don’t cram everything you know about the variable into its name
The variable name shouldn’t describe everything. That’s the role of the variable definition. For example, ultimateRareBossSword is a bad name, but sword is a better name.
In this example, I’ve named a variable “sword,” but I can look at its definition to see it has a rarity score of 10.
type Sword struct {
rarity int
name string
}
sword := Sword{rarirty: 10, name: "Tri-tip Dagger"}3. Use the surrounding context to your advantage
Variables and methods are always used within some context. There’s no reason to repeat the information already defined by the context. Use the context to your advantage to create shorter names.
// Bad: "dog" is redundant in dogName and dogAge because of the
// given context
type Dog struct {
dogName string
dogAge int
}4. Say no to fluff and jargon
Calling something a “manager” doesn’t convey any image to the reader about what the thing does. Does it do performance evaluations? Give raises?
Fluff and jargon provide no valuable information about the thing we’re naming. They’re too vague, so avoid using them in names. Some words to avoid: manager, data, value, instance, and object.
Bob’s rule of thumb is, “Ask yourself ‘Would this identifier mean the same thing if I removed the word?’ If so, the word doesn’t carry its weight: vote if off the island.”
Mauricio Panelo
Jan '22 Cohort
4y ago
My parents cook their rice on the stove.
It’s what their parents taught them. They’ve been using the same pot to cook their rice for decades. When I moved out of my parents’ place, I took their rice cooking tradition with me. But I sucked at it. Somehow I always managed to burn portions of my rice.
I never questioned the process though. It’s what my parents did, and so I must do it as well.
Thank you person who gifted me a rice cooker
Years later, someone gave me a rice cooker as a wedding gift.
When I saw the gift, I thought, “I don’t need this. I can cook rice on the stove." But my perspective changed as soon as I tasted the rice cooker’s very first batch. It blew me away. No burnt rice. No mushy rice. Just perfect delicious rice.
If I hadn’t received a rice cooker as a gift, I’d probably still be cooking rice on the stove.
I didn’t know I could cook rice using a rice cooker
I was doing a thing because that’s how I’ve always done that thing.
Jakob Greenfeld calls this situation an “invisible script.” Invisible scripts predetermine our decisions. They’re decisions ingrained into our subconscious. Decisions that we don’t question or reflect on because it’s how we’ve always done it.
It made me wonder, what other invisible scripts am I stuck in?
Being more conscious of invisible scripts
Jakob's newsletter was a good reminder to challenge the status quo.
Reflect on your most recent decisions. Are there any decisions you’ve taken because it’s what you’ve done in the past? Do alternative decisions exist? Experiment with the alternative decisions, and find out which one is the most optimal.
I’ll leave you with this blog post Jakob shared in the newsletter. It’s a list of “things you’re allowed to do that you thought you couldn’t, or didn’t even know you could.”
Mauricio Panelo
Jan '22 Cohort
4y ago
Last week, I invited Perry Yang—a software engineer at eBay—to a Zoom meeting.
Perry is the most curious and intelligent person I know. I needed to know why he chose software engineering as his career. After our meeting ended, I learned more about my friend’s past. But when I revisited my meeting notes I realized something.
Perry’s life events were important lessons on how to be successful. Here are the things I learned from our meeting:
Curiosity is powerful, and having a mentor can make a huge difference.
One person sparked Perry’s passion for electronics and computer systems—his uncle.
When Perry was a child, his uncle dropped off a DOS computer at his house. At first, he had no idea how to use the computer, but his dad showed him how to use it to play games. He needed to run specific commands to play the games. But he couldn’t remember them all, so he started documenting them in his notebook. He started getting curious. “What do these commands mean?”, he wondered.
So he called his uncle, and his uncle was very supportive. His uncle answered any questions he had about DOS, and taught him things he didn't even know about.
Mauricio’s Takeaways:
Mentorship is important. Mentors help you grow your skills. They’re a source of knowledge. A good mentor will always provide encouragement. Find a mentor.
Curiosity is powerful. Adopt a beginner’s mindset. Always ask questions and be open to new things. Be curious.
Find people with similar interests and experience, and grow together.
When Perry was in high school, he wanted to compete at a programming competition.
But he had no programming experience. In fact, almost nobody at his high school had any experience. Perry found a group of eager classmates who also wanted to learn programming and compete. They studied together and challenged each other to become better programmers. From this study group, he learned C++, Visual Basic, and basic data structures and algorithms.
Perry earned a spot on the team to represent his school at the competition. And he wouldn’t have done it without the help of his group mates.
Mauricio’s Takeaways:
Learn in a group. If you're trying to learn something new, why not form a group of people who are trying to learn the same thing? You'll learn faster when surrounded by like-minded individuals. Look how much we've grown since starting the Ship 30 Jan '22 cohort.
Mauricio Panelo
Jan '22 Cohort
4y ago
I don’t feel like writing today, but I also refuse to lose my writing streak.
Last Sunday, I wrote about things I learned from other Ship 30 members. But there’s a whole list of things I learned I didn’t get to write about. Since I’m not in the writing mood, I’m going to list out the things I left out.
Without further ado, here are the other things I learned last week:
Thai tapioca coconut milk dessert is delicious. Enough said. Go try it.
I have a soft spot for shōnen anime series. Sabikui Bisco just started releasing episodes on Crunchyroll. First episode deserved a chef's kiss. Excellent. Now to wait for more episodes to release, so I can binge it.
I can’t believe I’m watching the final episodes of Attack on Titan. It’s been over a decade since I started reading the manga.
Crunchyroll. Please, please, please fix the damn buffering issues 😞. It’s breaking my immersion.
I stopped watching The House on Netflix after the first story because it was super eerie. The film description mentioned “dark comedy,” but I promise there are no funny moments. Only sad moments. Or maybe I didn’t understand the humor.
I learned of Jakob Greenfeld and his Bootstrap MBA education. Look at at all the projects he has launched since July 2020. So cool.
What to Tweet is a great resource if you run out of ideas to tweet about.
Beagle puppies are so cute. My golden retriever is usually a brute. She surprised me when she started being gentle with the beagle puppy.
I’m not invested in my day job, but I don’t know what to do with that realization.
I'm a terrible driver in Tijuana. But I still ❤️ TJ.
Mauricio Panelo
Jan '22 Cohort
4y ago
Mothers know best.
Ignacio Ampuero grew up in Iowa—not Silicon Valley. No opportunities to learn programming at high school. No local programmers to meet. The programming path wasn’t in his sights.
But his mother pushed him to take the first steps on the programming path.
Ignacio enrolled to the Washington University in St. Louis as an undeclared major
He wanted to explore his options first.
Besides, there was no rush to declare a major until his sophomore year. He started his freshman year taking political science, math, and economic courses. He ended up enjoying math, especially when he entered his sophomore year. The math courses were more advanced and theoretical, and he was excelling in them.
But he wasn’t convinced that math was his major. He discussed it over with his mother.
Ignacio’s mother suggested he take a computer science course
And so he enrolled in CS 101.
He loved it. He loved putting logic into computer words. Programming had opened an infinite number of possibilities for him to create things. He became a creative monster. One of his earliest creations was a Chrome extension for Reddit. It was genius. The extension allowed him to view the Reddit comments on a post without having to click on it.
By the time Ignacio graduated college, he had built up an impressive (and funny) list of projects.
One small decision can have a gigantic impact
Ignacio is now CTO at Pasito.
Before Pasito, he held different engineering roles at Amazon. Roles such as Software Developer Manager, Senior Software Engineer, and Security Certifier. He’s accomplished many great things in his career. But it was one simple decision that put him on the path to success.
His mother’s decision to suggest he take a computer science course.
Special thanks to Ignacio Ampuero for setting time aside to do this interview. And for making me laugh.