Page 1 of 1
Version 1.0 is missing
Posted: Fri Oct 07, 2016 8:51 pm
by voyta
I live in Prague, and last time I looked out of the window, it was obvious the summer is long gone. So
where's 1.0?
Yes, the page probably needs a minor review.
Re: Version 1.0 is missing
Posted: Fri Oct 07, 2016 9:00 pm
by Smarty
moved to general discussions
Keep the golden rule in mind
(golden rule: everything takes longer than expected)
Re: Version 1.0 is missing
Posted: Fri Oct 07, 2016 9:14 pm
by voyta
Smarty wrote:moved to general discussions
This was not meant as discussion topic, but as a bug report for contents of that page. (I'm happy with living in 0.1x land, as that means the awesome thins will keep coming, if you ask me)
Re: Version 1.0 is missing
Posted: Fri Oct 07, 2016 9:35 pm
by Klonan
Just a small typo... should read summer 2017...
Re: Version 1.0 is missing
Posted: Sat Oct 08, 2016 12:17 pm
by ssilk
I thought it wasn't a type, cause the first plan was summer 2015.
Re: Version 1.0 is missing
Posted: Sat Oct 08, 2016 2:46 pm
by sillyfly
Maybe it should just say "Next summer"
Re: Version 1.0 is missing
Posted: Sat Oct 08, 2016 6:24 pm
by ChurchOrganist
First rule of programming.....
Estimate the time the application will take to develop......
Then multiply by 3.
Based on what I've read so far - Summer 2017 seems about right
Re: Version 1.0 is missing
Posted: Sat Oct 08, 2016 8:45 pm
by HanziQ
ssilk wrote:I thought it wasn't a type, cause the first plan was summer 2015.
Nah, it's a continuous typo.
Re: Version 1.0 is missing
Posted: Sat Oct 08, 2016 11:34 pm
by ssilk
ChurchOrganist wrote:Estimate the time the application will take to develop......
Then multiply by 3.
We always multiply with π and if that is not enough we multiply with e. And if that is still too low then c.
We never need a fourth iteration.
Re: Version 1.0 is missing
Posted: Sun Oct 09, 2016 7:06 am
by Lee_newsum
Just multiply by Ɯ
(that the Greek letter Ɯ)
Re: Version 1.0 is missing
Posted: Mon Oct 10, 2016 1:36 pm
by eladmir
ssilk wrote:ChurchOrganist wrote:Estimate the time the application will take to develop......
Then multiply by 3.
We always multiply with π and if that is not enough we multiply with e. And if that is still too low then c.
We never need a fourth iteration.
I like the idea of estimating my work in Meters rather then time.
c is in m/s
time is in s
m/s*s=m
I estimate that this code will take 1,985,903,012,123 m to complete.
Or roughly 1 hr 40 minutes!
Re: Version 1.0 is missing
Posted: Mon Oct 10, 2016 2:06 pm
by Acarin
Hang on a minute... m/s*s = meters per second squared = acceleration. In which case, you could measure it in g
"Yeah, this module's gonna take 6g to finish. I may pass out while it's compiling..."
"That's ok, the new rail tanker sprite is gonna take 1000g to complete. It's just a black hole!"
Re: Version 1.0 is missing
Posted: Fri Oct 14, 2016 3:28 pm
by Deadly-Bagel
Why is it we can measure distance with time, but not the other way around? I live 15 minutes from town. Quick, the show starts in half a mile!
Joking aside, whose summer are we talking about? =D
Re: Version 1.0 is missing
Posted: Fri Oct 14, 2016 5:48 pm
by Lehona
Actually all you need to explain the needed time is Hofstadter's Law:
https://en.wikipedia.org/wiki/Hofstadter%27s_law