Thiago Ghisi Profile picture
Apr 21 14 tweets 4 min read
The Counter-Intuitive Nature of Software Engineering & Product Development, A Thread:

I had a 1:1 meeting with @jgehtland a couple of weeks back, and I'm not sure exactly how we landed on a weird topic and a message behind a famous "Programming T-Shirt."

🧵 🧵🧵 Image
Funny enough, when Justin was trying to remember the exact T-Shirt's quote during our call, he said the following:

--> "Hours of Typing can save you Minutes of Thinking." instead of "Weeks of Programming can save you Hours of Planning."

Close enough!
He also mentioned a great quote he learned since he started to work with Brazilians at Nubank:

--> "Devagar, que tenho pressa."
It took me a while to fully digest that and understand the underlining message behind those quotes, but a few minutes later.

Bingo! I got it. 💡
So, I decided to start a thread - that went 'somehow viral' - to ask other folks for equivalent sentences they have lived in their professional experiences:

Below are The Top 15:
(remember, if these sentences don't make sense to you, try reversing them! 🙃)

1- Weeks of writing design documents can save you days of building a prototype.
2- Weeks of debugging can save you Seconds of automated testing.
3- Weeks of planning and estimating can save Hours of rescoping

4- Months of debate can save Hours of pretotyping.

5- Millions of dollars on hiring can save Thousands of dollars on retention.

6- Days of problem analysis & debugging can save Minutes writing tests
7- Hundreds of back and forth emails can save Seconds of phone calls.

8- Days of debugging can save Hours of testing.

9- Weeks of stress and awkwardness can save you Minutes of uncomfortable conversations.
10- Spending days on a new microservice/database can save Minutes of bash scripting

11- Hours of slack thread discussions can save Minutes of zoom calls.

12- Days of PR Review/Commenting back and forth can save you Hours of Pairing & Mobbing.
13- Years of banging heads against the wall working on one thing can save Weeks of experimentation.

14- Hours of sending cold LinkedIn messages can save you Minutes of asking for employee referrals.

15- Months of product development can save you Weeks of product validation.
Question: What are some other examples of the 'Counter-Intuitive Nature of Software Engineering & Product Development' in your experience?

#softwareengineering #programming #productdevelopment
I hope you've found this thread helpful.

Follow me @thiagoghisi for more.

Like/Retweet the first tweet below if you can:
You can read the unrolled version of this thread here: typefully.com/thiagoghisi/3d…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Thiago Ghisi

Thiago Ghisi Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @thiagoghisi

Apr 22
🇧🇷 🇵🇹 Os 4 Ps da Engenharia de Software: Um Framework para crescer na Carreira em TI

Demorou 1 ano e meio, mas estou muito feliz de disponibilizar hoje a tradução em Português do meu artigo com os meus maiores aprendizados dos últimos 15 anos trabalhando no Brasil e EUA.

🧵🧵🧵 ImageImageImageImage
Foram muitas horas, e muitos finais de semana nos últimos 3 anos trabalhando nisso.

Compartilho aqui algumas das minhas melhores ideias sobre como pensar de forma ampla e profunda sobre crescimento de carreira como Pessoa Desenvolvedora, Tester, TechLead ou na Trilha de Gestão.
Esta é uma versão expandida da apresentação que dei no The Conf em 2019 com um novo título: Os 4 Ps da Engenharia de Software: Um Framework para crescer na Carreira em TI.

Feedback crítico é muito bem-vindo.
Read 11 tweets
Apr 21
Got this question: ‘Could you give me some tips about becoming a Staff+ Engineer?’

(inspired by many ideas from @VicVijayakumar, @whereistanya & @kelseyhightower)

The number one thing is to define what a Staff+ Engineer is:
• 1- I believe this person knows how to help, motivate/encourage/empower/and lift other people. It’s a positive influence in the organization.
• 2- This is a person who knows how to make an impact beyond their own individual contributions. It is someone that build Bridges & Paving Paths to Enable Effective Collaboration & Execution.
Read 10 tweets
Apr 10
Enough about Behavioral interviews, let's talk about some practical tips to help you on Coding Interviews:

Solving Algorithm & Data Structure Problems

The best ideas from an old & almost forgotten book: Programming Interviews Exposed.
(from some old notes of mine from 2015)
Solving Coding Problems:

When you begin solving a coding problem, don't start writing code immediately.

First, make sure you completely understand the problem. It may help to work through a simple, concrete example and then try to generalize the process to an algorithm.
When you're convinced you have the right algorithm, explain it clearly. Writing the code should be one of your final steps.

The Basic Steps:

The best way to solve an interview problem is to approach it methodically.
Read 32 tweets
Apr 9
This thread by @austinbelcak on Behavioural Interviews is just so good. A masterpiece in my opinion.

A lot of what I've been trying to share here for the past 3 months.

Just absolutely loved it!

Below my Three Favorite Tips:
Yes yes yes!

I talked about this multiple times, the bad answers come in all kinds of structure, shapes and size, but the good and great answers all have many things in common: a clear and logical structure & framework is the number one.
I wrote about this on my very first article on Behavioural Interviews and I still see folks completely messing the super predictable questions answers.

Create a story bank.

Outline your main points.

Ask peers and mentors to review on Google docs.
Read 4 tweets
Apr 9
Yet another great interview passage, this time from @Lethain on:

The Core Challenge of Engineering Leadership Roles & The Three Most Common Leadership Pitfalls of Staff+ and Director+ People.

<Link at the end>

🧵🧵🧵
Brian: People should be playing to their own strengths and what is really important to the organization at the time. But some common pitfalls you identified in the book might blow people off course, maybe make them less effective in the role. Could you go through those for us?
Will: I think one of the core challenges of leadership roles is that, early in a career, you know the most important thing is getting this migration done or launching this product feature. Someone will tell you that.
Read 36 tweets
Apr 6
Tech Lead Journal Podcast interview with @laffra & Google's Project Tempo.



My Three Favorite Passages:

1️⃣ The Importance of Communication
2️⃣ The Controversial Rule about becoming a Senior Engineer:
3️⃣ What Do the Most Impactful Engineers do?

🧵 🧵🧵
1️⃣ The Importance of Communication for Engineers [00:13:18]
Henry Suryawirawan: [00:13:18] I like the way that you said that we should probably think about reversing the hard and the soft. I kind of resonate (with) that as well. Having been an engineer all my life, as well, sometimes yes, communicating is hard.
Read 104 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(