Adriano C. @_Croco

Eu acho aqui melhor que a outra rede social. 42bits.medium.com ABC - São Paulo Joined February 2011

Tweets

3K
Followers

158
Following

1K
Likes

346

Téo Calvo @teomewhy

4 months ago

q imagem boa

1 11 103 3K 6

View Details

Sush @2sush

2 years ago

Apple air, Amazon fire, Google earth. now, It's time for Microsoft water

376 1K 12K 448K 332

View Details

Software estimates are one of the oldest lies we tell ourselves. We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan. I focused a big part of my undergrad on software estimation. After graduating, I wrote plenty about the topic. Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built. I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom. Here is the most important lesson I learned: People can't estimate software. It doesn't matter who they are or how much experience they have. Estimating software reliably is science fiction. And the best part: They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable. And then they will. They always do. There are two solutions for this. Let's start with my recommendations for those who don't have a choice: 1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work. 2. Never volunteer an estimate. Everything you say will be used against you. 3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours." 4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours. But we all know your manager will force you to give an estimate. Here is what you should do: 1. Estimate how long you think it will take you to complete the task. 2. Multiply the number by 3. This will be the lower range of your estimate. 3. Double the lower range of the estimate. This will be the upper range. Example: If you think something will take you 1 day of work, say "between 3 and 6 days." Here is the funny part: It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of. The true solution for this problem: Work for a company that doesn't care about estimates.

501 2K 10K 1.9M 5K

View Details

Marcin Floryan 🇺🇦❤️, 🌍 🇪🇺🇸🇪🇵🇱🏳️‍🌈 @mfloryan

4 years ago

"If the train leaves every 5 minutes you don't care about a timetable. If it leaves every 2 days you want to know *exactly* when it leaves" Great analogy from @hamrin reflecting on planning, estimating and software delivery.

2 78 263 20K 35

View Details

Samir Duarte @eusousamir

4 years ago

Olá! Hoje é sexta-feira e eu vim estragar toda a magia do cinema pra vcs! Estão prontos? Então sigam o fio!

40 118 2K 0 65

View Details

Dr. Shuchi Grover 🇮🇳🇺🇸🌎 @shuchig

5 years ago

What does it mean to be human? 😂 (h/t @BrianBroll)

0 22 74 0 4

View Details

Wes Kao 🏛 @wes_kao

5 years ago

Most people suck at giving feedback. Here’s a framework for feedback that creates behavior change:

175 2K 12K 0 8K

View Details

Adriano C. @_Croco

5 years ago

@alberto_souza @mauricioaniche Eu li o artigo. Talvez o que explica um pouco esse fenômeno é o efeito Drunning-Kruger. Fica a sugestão desse tópico para exploração posterior, acho que ajudaria

0 0 1 0 0

View Details

Daniel Cukier @danicuki

5 years ago

Topologia de Times - Team Topologies youtu.be/Ad0nyeVpD-M

0 1 0 0 1

View Details

Adriano C. @_Croco

5 years ago

42bits.medium.com/o-que-%C3%A9-a…

0 0 0 0 0

View Details

Pedro Tavareλ @ordepdev

5 years ago

Sometimes people ask me which computer science papers they should read and I can't really answer that question, but I can list the papers I've enjoyed reading over the past years.

6 80 315 0 168

View Details

Kent Beck 🌻 @KentBeck

5 years ago

"When engagement is your only metric you're going to end up re-inventing addiction" -- @keithmadams

6 227 759 0 40

View Details

Zeno Rocha @zenorocha

6 years ago

Alternative Big O notation: 🤘 O(1) = O(yeah) 😎 O(log n) = O(nice) 👌 O(n) = O(ok) 🤐 O(n²) = O(my) 👎 O(2ⁿ) = O(no) 🤯 O(n!) = O(mg!)

9 92 374 0 22

View Details

EximiaCo @eximiaco

7 years ago

[CONTEÚDO TÉCNICO] Dívidas técnicas de naturezas similares podem ter impactos muito diferentes na produtividade dos times de desenvolvimento. É importante que tenhamos bons critérios de priorização sobre que dívidas pagar primeiro. buff.ly/2R4VMJ3