This topic is one of the best things I've seen on the forum recently.
+5%This topic is one of the best things I've seen on the forum recently.
Agreed. Updates like this on a semi-regular basis are exactly what investors are looking for.
+5%
not quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for? I know I'm going to get the "we don't like to give targets because we can't hit them", but it is something that real business that make real money do.
Everything in the update is very vague and this forum is full of posts about "This is happening soon and will make bitshares explode!!" that end up never happening. I'm very skeptical that any of these business development things actually coming to fruition.
I'd rather believe it won't be done , then once it's actually done , I would be more happy .
not quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
not quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
come onnot quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
come onnot quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
Do not believe this schedule,they can change it anytime.
come onnot quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
Do not believe this schedule,they can change it anytime.
Yea, it's more frustrating than anything to watch the milestones. All they ever do is get pushed back, past due, pushed back, past due, rinse and repeat. Some realistic ETA's would be nice.
come onnot quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
Do not believe this schedule,they can change it anytime.
Yea, it's more frustrating than anything to watch the milestones. All they ever do is get pushed back, past due, pushed back, past due, rinse and repeat. Some realistic ETA's would be nice.
Software development can be extremely difficult to estimate. I work in the industry and know first hand that sometimes the most trivial items take *much* longer to troubleshoot than items thought to be huge undertakings, sometimes one item may require another item to be re-worked in order to achieve maximum efficiency, etc. Sure, milestones can be changed or pushed back at anytime and I understand that could be frustrating but it's frustrating for the devs too and it's better to extend a deadline than implement an unstable version. As far as the devs are concerned, the milestones listed are probably *very* realistic but sometimes shit happens and you have to roll with it.
come onnot quite sure why this is worth a +5%orgasm... Basically all thats being said is that there are still people working on bitshares. Big deal, thats what they should be doing.
Some ETA's would be nice to have... is this stuff all a pipe dream, or is there an actual target date to aim for?
https://github.com/BitShares/bitshares/milestones
ETAs are:
0.9.0 = March 25.
0.10.0 = April 1
0.11.0 = April 8
Do not believe this schedule,they can change it anytime.
Yea, it's more frustrating than anything to watch the milestones. All they ever do is get pushed back, past due, pushed back, past due, rinse and repeat. Some realistic ETA's would be nice.
Software development can be extremely difficult to estimate. I work in the industry and know first hand that sometimes the most trivial items take *much* longer to troubleshoot than items thought to be huge undertakings, sometimes one item may require another item to be re-worked in order to achieve maximum efficiency, etc. Sure, milestones can be changed or pushed back at anytime and I understand that could be frustrating but it's frustrating for the devs too and it's better to extend a deadline than implement an unstable version. As far as the devs are concerned, the milestones listed are probably *very* realistic but sometimes shit happens and you have to roll with it.
Scotty Principle
(n.) The defacto gold star standard for delivering products and/or services within a projected timeframe. Derived from the original Star Trek series wherein Lt. Cmdr. Montgomery 'Scotty' Scott consistently made the seemingly impossible happen just in time to save the crew of the Enterprise from disaster.
The premise is simple:
1) Caluculate average required time for completion of given task.
2) Depending on importance of task, add 25-50% additional time to original estimate.
3) Report and commit to inflated time estimate with superiors, clients, etc.
4) Under optimal conditions the task is completed closer to the original time estimate vs. the inflated delivery time expected by those waiting.
The following situation is a simulation of the Scotty Principle in practice.
Kirk: "The ship seems sluggish today. When was the last time you did a tune-up on the warp drive?"
Scotty: "Aye, sir. She's due. Last maintenance was 56 days ago."
Kirk: (light chuckle) "Well, what are you waiting for? An ambush from cloaked Romulans?"
Scotty: "I'll need to check how much dilithium we have in supply, but she'll be better than new in no time."
Kirk: "And that will be...?"
Scotty: "Six hours."
--- four hours later ---
Scotty: "All done, sir. Care to test her out?"
--- Enterprise taken rapidly to warp 3, does a few doughnuts, comes to a smooth stop ---
Kirk: "Scotty, there's no finer engineer in this quadrant!"