Derek Corcoran

Spreading the R word, Linux and Python enthusiast, wildlife scientist

[Derek Corcoran @DerekCorcoranB]

¡Mi canal de YouTube ya tiene más de 1000 suscriptores! #1kcreator https://t.co/pGkm5qZ9bq Gracias a todos por el apoyo #rstats #rspatial

[Derek Corcoran @DerekCorcoranB]

@NPHard @oelma__ 28 for me

[Derek Corcoran @DerekCorcoranB]

A traditional Irish rebel song reimagined as folk metal by a Patagonian musician of Irish heritage living in Denmark, with bouzouki, heavy guitars, bodhrán and Irish flutes.https://t.co/VB96w6p5Wo

[Derek Corcoran @DerekCorcoranB]

@SheaSerrano That would be amazing! 10 seconds to score?

[Derek Corcoran @DerekCorcoranB]

@SheaSerrano Hey @SheaSerrano coukd you tell me what were the best you saw/heard? I have a small kid at home, cant listen to all of it

[Derek Corcoran @DerekCorcoranB]

@SheaSerrano Which was the best podcast you listened too, so far Zach Lowe was for me, but maybe you have a mor fun answer

[Derek Corcoran @DerekCorcoranB]

Hey @SheaSerrano, @ZachLowe_NBA and @BillSimmons I think this might be a possibility what do you think? #NBA #KawhiLeonard

[Derek Corcoran @DerekCorcoranB]

Hey @metalsucks, new folk-metal single “I Am the Wind” premieres Sep 2. Preview: https://t.co/sZfBpBZixj #metal #folkmetal

[Derek Corcoran @DerekCorcoranB]

I Am The Wind – Glacial Light (Concept Album Chapter) #Shorts' #folkmeta... https://t.co/ZfP32pUnN6 through @YouTube

[Derek Corcoran @DerekCorcoranB]

After 4 composed songs, yesterday my 6 year old son while we are listening to an awesome rock song asks, did you write this song dad? I think I reached the top

[Derek Corcoran @DerekCorcoranB]

Dear @KLM Customer service, I need to send a message in order to ask a question about the baggage for my flight

[Derek Corcoran @DerekCorcoranB]

@ZachLowe_NBA It was so good to hear you again

[Derek Corcoran @DerekCorcoranB]

@SheillDaniel @NateSilver538 Not at all being sarcastic, what would you say is a true city? Coming from a small town anything north of 100,000 I inhabitants is a city to me, but I am guessing population is not in your criteria

[Derek Corcoran @DerekCorcoranB]

@netw3rk and @SheaSerrano, I really need a picture of Jason's mom's christmas town, can we get it?

[David Robinson @drob]

Academia has higher standards than industry for “is this true?”

Industry has higher standards than academia for “is this useful?”

[Derek Corcoran @DerekCorcoranB]

@simonthenorth Si pasas por missouri @ShakesPizza pensaré lo mejor de california

[Derek Corcoran @DerekCorcoranB]

@Martin_A_Nunez I guess this might be very useful for people with osteoporosis? That is of global concern right?

[Santiago @svpino]

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.

[nixCraft 🐧 @nixcraft]

Lmao. why Linux is safer than other oses?

[Derek Corcoran @DerekCorcoranB]

🆘 Urgent plea to @FlySWISS 🆘 Parents-in-law had ordeal flying your partner airline. Father-in-law broke hip, had surgery in Paris layover. Shared docs, no help/refund. 💔 Not seeking sympathy, just fairness. Please assist with refund/rescheduling. 🙏 #CustomerService