Mauricio Panelo

Mauricio Panelo

/maupanelo

Mauricio Panelo

Welcome to my Social Blog

User Avatar

Mauricio Panelo

March '22 Cohort

4y ago

How 3 Actions Saved My Desire to Pursue a Career in Software Development
Mauricio "Mau" Panelo

In 2015, I almost quit coding.

At the time, I was learning Java and basic coding concepts at my junior college. But I had no motivation to code or build applications outside of the classroom. I had my doubts about pursuing a degree in computer science.

Did I really want to become a software developer after I graduated?

In the same year, I transferred to a 4-year college and decided to give computer science one more chance

Best. Decision. Ever.

A new college gave me a new outlook on coding, computer science, and software development. There were three major factors that helped me crush my doubts:

1/ I made friends and coded with them in my free time

Coding with friends is fun.

We created (unofficially) a mastermind group for coding, and we learned a ton. We studied together, we shared knowledge, we gave each other feedback. It was perfect.

I found myself wanting to code more and more because friends + coding was the perfect mix.

2/ I Learned a New Programming Language

I learned basic coding concepts through Java, but I wasn't a big fan of Java.

It never occurred to me to try other programming languages. My friend introduced me to Python and I instantly fell in love. Python's syntax is simple and straightforward to learn. Once I had a grasp of Python, my creativity was off the charts.

It was clear I liked programming, but I was using a tool I disliked.

3/ Start Explorin'

There are so many paths you can take with a software development career.

When I found out I liked Python, I knew I needed to explore other areas. I tried Android development but I didn't like it. I tried web development and I enjoyed it.

I explored all the things to make sure I wasn't doing things I didn't like.

7 years later I'm still coding and I still enjoy it.

User Avatar

Mauricio Panelo

March '22 Cohort

4y ago

10 Things I Rather Do Than Write This Essay
Mauricio "Mau" Panelo

Today was a long day and I'm all out of energy.

I don't want to spend too much time writing this essay because I need to recharge for tomorrow. So I thought I'd make it easy for myself and write 10 things I rather do.

Gotta keep the streak alive. In no specific order:

  1. Watch Star Wars: Rebels with my baby boy. Somehow I persuaded my son to be a Star Wars fan.

  2. Sleep

  3. Learn front-end development. I'm learning Next.js, TypeScript, and TailwindCSS right now.

  4. Play Risk of Rain 2. I love this game, and a DLC recently released so I'm hooked again.

  5. Watch a movie on Netflix. I'm not sure what to watch though.

  6. Clean the kitchen

  7. Pack up my stuff for this weekend's move

  8. Watch a live stream of someone coding

  9. Sculpt something out of polymer clay

  10. Play League of Legends

User Avatar

Mauricio Panelo

March '22 Cohort

4y ago

Stuck in Tutorial Hell? Here are 3 Ways You Can Escape It
Mauricio "Mau" Panelo

It’s tempting to jump straight to the next tutorial as soon as you finished one.

But it’s the quickest way to get stuck in tutorial hell. You might believe that you're not ready to embark on your own because you have more to learn from tutorials. The truth is you’ll never be fully prepared if all you do is consume tutorials.

So here are 3 things you can do to escape tutorial hell:

1/ Apply What You’ve Learned

Use the skills you’ve acquired to create something.

It’s the quickest way to test yourself on what you’ve learned. It’s OK if some things didn’t stick from the tutorial. Return to the tutorial and jump to the parts that didn’t make sense.

Repeat the process until you’re not referencing the tutorial anymore.

2/ Learn to Problem Solve on Your Own

The tutorial won’t have all the answers.

That’s when you need to exercise your problem solving skills. Research the problem on Google. Experiment with different solutions and compare the tradeoffs.

If you’re not struggling, then you’re not learning.

3/ Write About the Things You’ve Learned

I find that writing helps me solidify what I’ve learned.

When I can transform thoughts into a written piece, then I know I learned something. The written piece also serves as documentation for your future self. And if you publish it online, it can also help anyone who is a few steps behind you.

Writing helps you grow, and the community grow.

User Avatar

Mauricio Panelo

March '22 Cohort

4y ago

3 Things I've Learned From Building a Daily Coding Habit
Mauricio "Mau" Panelo

“I don’t have time to code in my free time”

I convinced myself this was true until I joined Ship 30 for 30. I saw how having sacred hours to write an atomic essay was effective. So I applied what I learned from Ship 30 to building a daily coding habit.

Here's what I've learned since I started in mid-January:

1) Consistency doesn’t mean every day

It's OK to take a few days off.

I need the time off to avoid burning out or spending time with family and friends. Coding for an hour should never be my #1 priority. But I shouldn't develop a habit of missing days consistently.

As long as I'm being consistent over a long period of time, I'm happy.

2) The quality of work isn't important to me

If at the end of the coding session I create something trivial, then it's OK.

I care about putting the reps in, not the quality of the work. Today I might create something trivial. Tomorrow it might turn into something complex if I build off of it.

Just put in the reps 💪.

3) Give yourself permission to do things you thought you couldn't do

I thought I had to code for a full hour.

But there were days I didn't feel motivated to do so. I didn't want to miss a day, so I changed the rule from code for an hour to code for up to an hour. I gave myself permission to take it easy when I needed to.

Sometimes coding for 20 minutes brought back my motivation to code the full hour.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

3 Things I’ve Learned From Coding For An Hour Every Day
Mauricio "Mau" Panelo

For the past 11 days I’ve been working on a small project.

I do one hour coding sessions after work to focus on something I’m passionate about. The current project I’m working on is nearing its completion, and I’ve learned a lot. But there are things I wish I did differently.

Here are three things I want to do for my next project:

1. Identify the primary goal of the project

I don’t want to be stuck in development hell.

I noticed my current project’s scope is growing bigger and bigger as I think of new features to add. But how do I know when a project is complete? Setting a project goal should help me stay on track and be an indicator for when I'm done.

Once I’ve reached the project goal, I can either set a new goal or move on to a new project.

2. Break down the project into smaller tasks

I can create smaller goals out of the project’s primary goal.

Every smaller goal will represent a mini-project. These mini-projects, or tasks, should be super specific on what I need to get done. This should give me a complete overview of what I need to do to satisfy the primary goal.

But now that I have a bunch of small tasks, how should I organize them?

3. Create a project timeline

I can organize my smaller tasks into a project timeline.

This will help me understand how much time each task should take. I can also give a priority to each task. A project timeline will help me stay accountable on completing the primary goal.

And I love having a visual overview of my progress.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Don’t Be Afraid to Write Sh*t Code. Here Are 4 Things I Learned About My Sh*t Code Yesterday
Mauricio "Mau" Panelo

I love writing sh*t code.

Yesterday I wrote the most mom’s spaghetti looking code I had ever seen. It was the great. I couldn’t believe how productive and creative I was being.

Here’s what I learned about my sh*t code:

Writing sh*t code helped me understand third-party tools faster

Are you learning a new third-party tool like an API wrapper for your favorite language?

Read the documentation and start coding something. You’ll learn 100x faster when you start playing around with the tool. Don’t focus on the code quality.

Focus on answering questions and surfacing questions you might not have thought of.

I made corrections to my design after writing sh*t code

You wrote sh*t code and answered a lot of questions.

Leverage the results of your sh*t code to tweak the design. Is the new design not good enough? Repeat the entire process again until you reach a design you’re confident in.

Iterate. Iterate. Iterate.

Clean up your sh*t code

Congratulations you created a solid design by writing sh*t code.

It’s time to clean up your mess. Refactor your sh*t code and adhere to good software design principles. Think of the person who will have to maintain your spaghetti code—news flash it’s you.

For your future self’s sake, transform the sh*t code into clean and maintainable code.

There’s a technical term for sh*t code

Tracer bullets.

The primary goal of a tracer bullet is to figure out whether your design is viable or not. If it’s not, then you tweak the design. Tracer bullets are either discarded or transformed into production code.

The next time you begin a new project or sprint write sh*t code to test the viability of your design plan. Fire that tracer bullet.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Dear Shippers, You Achieved Greatness at the Start of This Journey
Mauricio "Mau" Panelo

Congratulations Shippers, we've reached the end of our 30-day journey.

We’ve accomplished so much within the span of a month. Let’s take a moment to celebrate all the wins—big or small—we’ve made since the start of this journey. But is reaching the end of the journey and the wins you’ve accumulated the moment you achieved greatness?

No, you achieved greatness long ago.

You achieved greatness when you published your first essay.

“Results are not the attainment of greatness, but simply confirmation of it. You become great long before the results show it.” — Brian P. Moran

The moment you decided to make a commitment to build a writing habit was the moment you chose to be great. You achieved greatness within an instant. It happened when you clicked “Publish” on your first atomic essay.

The results you’ve achieved over the past 30 days confirm it.

Whether you’ve consistently shipped the past 30 days or not doesn’t matter.

You fell off the ship a few times, so what?

You continued to get back on the ship, write, and publish essays. This already sets you far apart from the majority of the internet population. You continue to do the things you need to do to be great.

It’s been a helluva journey, and I’m glad I got to be a part of this community. Where will you greatness take you next?

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

This Millennial Doesn’t Know How to Mail Things and Lost an Opportunity to Act On His Value
Mauricio "Mau" Panelo

Yesterday, I went to the post office to mail forms to my medical insurance.

I walked into the post office and realized I had no idea what the fuck I was doing. I can count the number of times I’ve physically mailed something on one hand. I looked around for the first thing that looked like an envelope, and filled it out.

I got in line and waited for my turn to speak to a postal associate.

I saw the line behind me getting longer when the associate called me up next.

I handed him the envelope. He inspected it, saw everything checked out, and said it was going to cost me $26.95 USD. Holy shit?! I’m not paying that much to ship 3 pieces of paper. I asked if he could show me the envelope that’s a tier below the one I picked out.

He said the new envelope would cost $8.95 USD.

I didn’t want to be an inconvenience to the associate and the people behind me, so I said ok.

I filled out the new envelope, and got back in line.

I felt like a dummy. Not because I didn’t know what I was doing, but because I wasn’t courageous enough to ask for help or an explanation. Brené Brown introduced me to the mantra “courage over comfort,” and one of my two values in life is courage.

But why didn’t I exercise courage in this situation?

I want to build a habit of reflecting on my choices.

I have two values, but how do I know I’m staying true to them?

Here’s what I want to do:

  • Do a daily and/or weekly reflection

  • Identify the choices where I didn’t practice my values

    • What can I do next time to practice my values?

    • Why didn’t I practice my values?

  • Identify the choices where I did practice my values

    • How can I apply this to situations where I didn’t practice my values?

    • Did I consciously or unconsciously practice my values?

    • Celebrate 🎉

If you have other suggestions on how to practice your values, please let me know.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Studying for a Software Developer Interview? Here Are 4 Tips to Help You Prepare
Mauricio "Mau" Panelo

In 2020, I spent 5 months studying data structures and algorithms.

Within that time-frame, I learned 4 valuable tips that could have reduced my study time down to a month.

Here are the 4 tips I wish I knew before I started studying for interviews:

Mentally prepare yourself for a difficult interview

The interview will be hard.

You’ll have 40-50 minutes to provide a working solution. And on top of that, you have someone evaluating your work in real-time. It’s going to be stressful.

Stay calm, and be confident in your abilities.

How long does it take you to solve a technical interview question?

Practice time management.

A typical interview lasts 40-50 minutes, but you won’t have the entire time to solve the problem. Introductions take up a few minutes at the beginning.. Another 5-10 minutes explaining the problem and clarifying any questions. This leaves you with about 25 minutes to fully write and test code.

While you’re studying algorithms and data structures, time yourself. Make sure you’re not going over 25 minutes.

Think of test cases for your solution

When you finish solving a question, don’t just stop there.

Ask yourself, what inputs should I use to cover all cases of my solution? Think corner cases. Interviewers want to see that you’re thinking about this. It’s a big mistake to write the code and claim you’re done.

Think of the inputs your solution should handle.

Find a buddy to do mock interviews with

LeetCode isn’t a perfect representation of a real interview.

Interviewers are going to ask you follow up questions. They’re going to change up the original problem. Find a buddy who’s willing to be your mock interviewer.

Mock interviews are great for getting a taste of the real deal and receiving valuable feedback.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

3 Tips on How to Learn More From Tutorials
Mauricio "Mau" Panelo

How much are you actually learning from tutorials?

Tutorials are a great way to learn new things. But you need to balance guided learning with unguided learning, or you won’t learn anything at all.

Here are 3 tips on how to get the most out of tutorials:

Re-create the tutorial in a different context

Let’s say you’ve created a Facebook clone by following a tutorial.

You can use what you’ve learned to build a Twitter clone. The benefit to this is you’re not completely on your own. Since the products are alike, you can always refer to the tutorial when you get blocked. But it also has different features which allow you to learn new things (e.g. how to impose a 280 character limit on posts).

Re-creating a tutorial is a good mix of guided and unguided learning.

Try to complete the tutorial without looking at it

How far can you get without looking at the tutorial?

When you’ve reached a point where you need to pull up the tutorial again, you’ve identified a knowledge gap. Ask yourself why you couldn’t replicate X on your own. Did the tutorial not do a good job of explaining it? Do you need to spend more time learning X?

Redoing the tutorial is a great way to quickly identify knowledge gaps you need to focus on.

Extend the tutorial with your own features

Don’t abandon what you’ve created as soon as you finish the tutorial.

Extend it with features you’re interested in learning. You’ve already created a solid foundation, why not add to it and give it your own unique twist? Not only are you learning new things, but you’re also creating a product you can call your own.

A tutorial can never cover everything. Identify core or interesting features and implement them.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

The 4 Keys to Successful Commitments
Mauricio "Mau" Panelo

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.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

WTF Git?! 3 Things That Confused Me When I Started Using Git
Mauricio "Mau" Panelo

When I was a university student, whenever I fucked up my local repository I instantly deleted it and re-cloned it.

I hated git as a student. But once I started investing time to learn git, things finally clicked. I was no longer blowing up my local repository to fix my dumb mistakes.

Here are 3 things that confused me as a newbie:

WTF does origin mean?

You’ve probably seen the word origin frequently when working with git.

There’s nothing special about it. Origin is an alias of the remote repository URL you cloned from. Git creates this alias by default when running the git clone command. If for whatever reason you want to rename origin, you can run the following command:

# Rename origin to myNewAlias
$ git remote rename origin cheddar

# Verify the new alias
$ git remove -v

cheddar	git@github.com:maupanelo/coolRepo.git (fetch)
cheddar	git@github.com:maupanelo/coolRepo.git (push)

WTF is the difference between git fetch and git pull?

The commands git fetch and git pull are similar, but one is the safe and nondestructive version.

Both commands download the latest content from the remote. But git fetch doesn’t explicitly integrate the fetched content into your local repository. Running git pull, however, doesn’t ask for permission to merge the fetched content into your local repository.

This makes git fetch the safer command to run.

With git fetch, you can view what others have worked on before merging them into your working changes. This lets you scope out and address any potential merge conflicts before running git merge.

Tl;dr: git pull runs git fetch then git merge.

WTF, git checkout does too many things.

Too many damn things.

It can create and checkout branches, checkout commits, and discard un-staged changes on a file. It can be overwhelming. Even more so when trying to explain the command to junior devs. The Git team is working to split up the many use cases of git checkout into other git commands.

Be aware that these commands are still experimental, and may change in the future.

# Change branch
$ git switch <branchname>

# Create branch
$ git switch -c <branchname>

# Undo unstaged changes on file
$ git restore <filename>
User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

7 Things I Miss About Santa Barbara
Mauricio "Mau" Panelo

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:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. Surrounding Cities. I miss Isla Vista. I miss Goleta. I miss Carpinteria. I miss Oxnard. I miss Solvang.

  7. 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.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Bob Nystrom’s Four Rules For Better Naming in Programming
Mauricio "Mau" Panelo

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.”

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Oh My God, Can You Fucking Stop Trying to Make Me Productive 24/7?
Mauricio "Mau" Panelo

The voice in my head (a.k.a Morris) is trying to shame me again.

“You’re not being productive.”

I’m trying to watch the latest episode of The Book of Boba Fett. Can you shut the fuck up?

“You’re reading articles instead of writing your own.”

I’m enjoying the read. Can you shut the fuck up?

“You’re playing video games.”

I’m trying to win this ARAM game. Can you shut the fuck up?

We can’t be hyper-productive every day

And that’s ok.

We have other responsibilities. We have family and friends that need us. Unexpected errands might pop up. We can’t invest every second we have to meet an unrealistic productivity metric. We're not machines.

We need breaks too.

Take a break

It’s ok.

Take a break today. You’ve earned it. Do absolutely nothing or hang out with someone. Binge watch something or play a video game (I recommend playing Path of Exile next week). You'll be doing everything except wasting your time. Recharge yourself.

Tomorrow your energy reserve will be ready for maximum productivity.

My favorite "unproductive" moments

Here are some moments I recall being "unproductive," and it was an absolute blast:

  • I once binged watched the entire Game of Thrones show in a few days

  • I later found out my wife hadn’t watched Game of Thrones before. I binged it again

  • I’ve played 257 hours of Duck Game. It’s still my most played game on Steam since 2015

  • Chasing a 1 year old around like a zombie during work breaks

  • Photoshopping my friends in funny scenarios

  • Re-watching Star Wars: The Clone Wars for the 3rd time

  • Asking my wife to explain the latest K-Drama she’s watching on Netflix

What’s your favorite “unproductive” moments?

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

“Wait I can cook rice using this thing called a ‘rice cooker’?”
Mauricio "Mau" Panelo

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.”

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

What Makes This eBay Engineer So Successful?
Mauricio "Mau" Panelo

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.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

Who Put This Guy in Charge of My Writing?
Mauricio "Mau" Panelo

Writing isn’t hard. It’s fucking hard. Did I set myself up for a Michael Scott joke?

When I write, it feels like someone else is in the driver’s seat. Let’s call him Morris. I’m in the backseat watching hopelessly. Anything I say to Morris is completely ignored. It sucks. This is how I’d imagine a conversation would play out:

Morris: I’m going to sit here and stare at the computer screen for twenty minutes.

Mau: Um? What are you doing?

Morris: Would you look at that. Twenty minutes are up. What should I write about today? What will earn me the most internet points?

Mau: Are you seriously asking yourself that just now? Who cares about internet points. Just hit the keys and make words appear on the screen.

Morris: Wait a minute. This sentence doesn’t look right to me. It’s not perfect enough. Let me re-write this. Oh and this. This too.

Mau: Come on...we’re an hour into this. Can we not edit now, and focus on getting a draft done first?

Morris: I can’t write. I can’t transfer my thoughts into complete sentences. Me feel frustrated.

Mau: You’re trying too hard to be perfect. Drop the perfectionist attitude and the sentences will start flowing. Allow yourself to create junk.

Morris: Wow I can’t believe it’s already been two hours, and I’m not even close to shipping.

Mau: Fuck. Who put Morris in charge of writing? Can we fire this guy? Do we have HR approval?

Welp. I’ve made it this far with Morris. But I really should be allowing myself to create junk. No more Mr. Perfect.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

I'm not in the writing mood today. Here's a mixed bag of my learnings from last week.
Mauricio "Mau" Panelo

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:

  1. Thai tapioca coconut milk dessert is delicious. Enough said. Go try it.

  2. 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.

  3. 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.

  4. Crunchyroll. Please, please, please fix the damn buffering issues 😞. It’s breaking my immersion.

  5. 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.

  6. I learned of Jakob Greenfeld and his Bootstrap MBA education. Look at at all the projects he has launched since July 2020. So cool.

  7. What to Tweet is a great resource if you run out of ideas to tweet about.

  8. Beagle puppies are so cute. My golden retriever is usually a brute. She surprised me when she started being gentle with the beagle puppy.

  9. I’m not invested in my day job, but I don’t know what to do with that realization.

  10. I'm a terrible driver in Tijuana. But I still ❤️ TJ.

User Avatar

Mauricio Panelo

Jan '22 Cohort

4y ago

How a Mother’s Instinct Created a Programmer Son
Mauricio "Mau" Panelo

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.