Topic: [ANN] Syscoin- FINAL 2.0 LAUNCHED! *ENCRYPTION, MARKETPLACE, BTC INTEGRATION* - page 192. (Read 582967 times)
September 22, 2014, 01:28:11 PM
I want some of whatever the guy above me is on!!!
September 22, 2014, 01:24:56 PM
These people are making it up as they go along. Maybe they will learn to program and test properly before the marketplace release but I highly doubt it.
Don't fall for their RC BS. Its a sly way of covering up their nonsense coding and testing techniques.
Pathetic.
Don't fall for their RC BS. Its a sly way of covering up their nonsense coding and testing techniques.
Pathetic.
September 22, 2014, 11:00:44 AM
Just catching up on all the posts- are people having issues posting items on the feedback thread on Syscoin forums? We are trying to consolidate the feedback there so we can address everything and not have items duplicated across channels or omitted. We also want to discuss some of these items- that is why we pushed people to Syscoin Forums for feedback.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed but thats what an RC is for. The quirks will be fixed soon.. As you know software is a complicated beast with multi variables input and output.. its good to get out a working package and then iron out issues as a bigger userbase uses and finds them. As a long term professional developer im surprised there arent more bugs.. in the workforce you can expect dozens of new bugs on RCs off the bat so to me the quality is good and
is improving. This is a technical field so its not going to get all sparkly clean and super intuitive all of a sudden.. takes a few iterations to get there. Those who so not see the forest through the trees do not habe experience in the field of r&d to know any better. Those that do well you will see inherint value in what has beem given to you and can extrapolate on possibilities to come which are practically endless.
Both excellent points and to be honest we're aware of this issue- we have an entirely new (as in- from scratch) wallet UI and experience coming around the time of the 0.1.6 release. Part of the problem with the current wallet is that its foundation was established long ago (via Bitcoin) and its programming language (QT) is extremely slow to program in and develop clean and engaging experiences in efficiently. To remedy this we will are working on a new wallet for 0.1.6 more on that later.
@Shadowduck you raise valid points I'm following up with you on PM. We are most definitely not ignoring your pull requests its already been merged into the master branch and has been for some time with no reported issues. I need to cherry pick the commit back into devstaging-0.1.5.
I want to re-emphasize this is a RELEASE CANDIDATE AKA PUBLIC BETA, and RC1 at that. If you have been watching github overnight a number of changes have already been pushed for an RC2 and more are being pushed tonight. We will probably have an RC2 release candidate update later tonight- USA/PST time, not sure exact time yet.
I agree with people's comments regarding a technical writer and better documentation around aliases in general in parallel with their release. Again this is something we're improving as we move forward and something we have not yet released. Seeing as how this was released as an "RC" we didn't publish a lot of the marketing and help materials we have related to aliases because we didn't want to confuse people still using the 0.1.4c wallet with interfaces and actions that didn't exist there. When 0.1.5 is promoted to a production candidate these help files will be available on the website.
Please keep the feedback coming, we're listing the items being reported in the OP here http://syscoin.org/board/discussion/55/syscoin-0-1-5-release-candidate-feedback-thread#latest
-minus the negativity-
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed but thats what an RC is for. The quirks will be fixed soon.. As you know software is a complicated beast with multi variables input and output.. its good to get out a working package and then iron out issues as a bigger userbase uses and finds them. As a long term professional developer im surprised there arent more bugs.. in the workforce you can expect dozens of new bugs on RCs off the bat so to me the quality is good and
is improving. This is a technical field so its not going to get all sparkly clean and super intuitive all of a sudden.. takes a few iterations to get there. Those who so not see the forest through the trees do not habe experience in the field of r&d to know any better. Those that do well you will see inherint value in what has beem given to you and can extrapolate on possibilities to come which are practically endless.
Both excellent points and to be honest we're aware of this issue- we have an entirely new (as in- from scratch) wallet UI and experience coming around the time of the 0.1.6 release. Part of the problem with the current wallet is that its foundation was established long ago (via Bitcoin) and its programming language (QT) is extremely slow to program in and develop clean and engaging experiences in efficiently. To remedy this we will are working on a new wallet for 0.1.6 more on that later.
@Shadowduck you raise valid points I'm following up with you on PM. We are most definitely not ignoring your pull requests its already been merged into the master branch and has been for some time with no reported issues. I need to cherry pick the commit back into devstaging-0.1.5.
I want to re-emphasize this is a RELEASE CANDIDATE AKA PUBLIC BETA, and RC1 at that. If you have been watching github overnight a number of changes have already been pushed for an RC2 and more are being pushed tonight. We will probably have an RC2 release candidate update later tonight- USA/PST time, not sure exact time yet.
I agree with people's comments regarding a technical writer and better documentation around aliases in general in parallel with their release. Again this is something we're improving as we move forward and something we have not yet released. Seeing as how this was released as an "RC" we didn't publish a lot of the marketing and help materials we have related to aliases because we didn't want to confuse people still using the 0.1.4c wallet with interfaces and actions that didn't exist there. When 0.1.5 is promoted to a production candidate these help files will be available on the website.
Please keep the feedback coming, we're listing the items being reported in the OP here http://syscoin.org/board/discussion/55/syscoin-0-1-5-release-candidate-feedback-thread#latest
September 22, 2014, 10:42:55 AM
Whatever guys. The release was a disaster like the others. I have over 2 million in sys. They hopefully fired the guy who claims to be a programmer.
Look at them using ICO money to prop up the price on mintpal. That 320 order is BS.
Look at them using ICO money to prop up the price on mintpal. That 320 order is BS.
Haha.. register forum today, and FUD Syscoin from the first post, and claiming to hold millions of Syscoin. i love smart people
Ok..for the report, i have to rebuild block every time i upgrade wallet from 0.14 to 0.15, tested it in 3 PC/Wallet.
Jumping to PM for clarification.
September 22, 2014, 10:35:55 AM
Whatever guys. The release was a disaster like the others. I have over 2 million in sys. They hopefully fired the guy who claims to be a programmer.
Look at them using ICO money to prop up the price on mintpal. That 320 order is BS.
Look at them using ICO money to prop up the price on mintpal. That 320 order is BS.
Haha.. register forum today, and FUD Syscoin from the first post, and claiming to hold millions of Syscoin. i love smart people
Ok..for the report, i have to rebuild block every time i upgrade wallet from 0.14 to 0.15, tested it in 3 PC/Wallet.
September 22, 2014, 10:22:48 AM
Development Release Update!
Introducing the Syscoin Release Candidate Program with v0.1.5 RC1
Release Candidate Program: Feedback | Release Candidate Wallet Download
We have created a thread to hold all the FAQ items for this release, 0.1.5 RC1 RELEASE FAQ
For the newcomers. Again to clarify, this is a Release Candidate (RC).
Do read the blog post above please.
September 22, 2014, 10:19:58 AM
Thanks for the giveaways SYScoin. great support..!!
September 22, 2014, 08:05:05 AM
Hold on, what now?
It's FUD. (pretty low grade FUD at that..)
September 22, 2014, 07:51:59 AM
Wow, I was right! MOOLAH is firing them! Holy shit!
Good for them! Maybe they'll get someone who has experience.
Good for them! Maybe they'll get someone who has experience.
Hold on, what now?
He's fudding... Ignore him.
September 22, 2014, 07:49:08 AM
Wow, I was right! MOOLAH is firing them! Holy shit!
Good for them! Maybe they'll get someone who has experience.
Good for them! Maybe they'll get someone who has experience.
Hold on, what now?
September 22, 2014, 07:47:23 AM
Actually going to leave this for now. I think you need it to get through your day.
September 22, 2014, 06:24:28 AM
cheapcoin, let's buy some.
September 22, 2014, 06:18:11 AM
I agree with everything you just said. And at the same time, I agree with ME just as much as I agree with you.
Just saying that now might just be the time to put some polish on the hoopty before wrenching on a new set of headers.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed but thats what an RC is for. The quirks will be fixed soon.. As you know software is a complicated beast with multi variables input and output.. its good to get out a working package and then iron out issues as a bigger userbase uses and finds them. As a long term professional developer im surprised there arent more bugs.. in the workforce you can expect dozens of new bugs on RCs off the bat so to me the quality is good and
is improving. This is a technical field so its not going to get all sparkly clean and super intuitive all of a sudden.. takes a few iterations to get there. Those who so not see the forest through the trees do not habe experience in the field of r&d to know any better. Those that do well you will see inherint value in what has beem given to you and can extrapolate on possibilities to come which are practically endless.
Just saying that now might just be the time to put some polish on the hoopty before wrenching on a new set of headers.
-minus the negativity-
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed but thats what an RC is for. The quirks will be fixed soon.. As you know software is a complicated beast with multi variables input and output.. its good to get out a working package and then iron out issues as a bigger userbase uses and finds them. As a long term professional developer im surprised there arent more bugs.. in the workforce you can expect dozens of new bugs on RCs off the bat so to me the quality is good and
is improving. This is a technical field so its not going to get all sparkly clean and super intuitive all of a sudden.. takes a few iterations to get there. Those who so not see the forest through the trees do not habe experience in the field of r&d to know any better. Those that do well you will see inherint value in what has beem given to you and can extrapolate on possibilities to come which are practically endless.
September 22, 2014, 06:10:42 AM
-minus the negativity-
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed, there is also such a thing as biased testing where because you are a developer you neglect to check other aspects of the software overall. IMO it would be wise to have a third party point of view with regards to testing. Improvements are in order both in the features and in the dev approach but its good that the dev is open to suggestions.
Agreed... Lack of UAT was the major issue at launch imho.
Hopefully devs will take this feedback on board this time.
September 22, 2014, 06:09:11 AM
-minus the negativity-
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed but thats what an RC is for. The quirks will be fixed soon.. As you know software is a complicated beast with multi variables input and output.. its good to get out a working package and then iron out issues as a bigger userbase uses and finds them. As a long term professional developer im surprised there arent more bugs.. in the workforce you can expect dozens of new bugs on RCs off the bat so to me the quality is good and
is improving. This is a technical field so its not going to get all sparkly clean and super intuitive all of a sudden.. takes a few iterations to get there. Those who so not see the forest through the trees do not habe experience in the field of r&d to know any better. Those that do well you will see inherint value in what has beem given to you and can extrapolate on possibilities to come which are practically endless.
September 22, 2014, 05:45:51 AM
Thank you for blessing us with your cogent and relevant input. (or not)
Seriously, change your approach.
Seriously, change your approach.
I just licked MOOLAH's plums, everyone! (everything else removed)
September 22, 2014, 05:30:55 AM
The most thing in UI design is user friendly and beautiful, maybe you can hire some expertise in UI degisn, UI is simple to developer, but it's very important to users.
I think a quick round of user acceptance testing would be a big help in this regard. Would just take a very small group a few hours to iron out any howlers (such as this passphrase palava..).
That is the plan going forward as per Dan's post.
Development Release Update!
Introducing the Syscoin Release Candidate Program with v0.1.5 RC1
Release Candidate Program: Feedback | Release Candidate Wallet Download
We have created a thread to hold all the FAQ items for this release, 0.1.5 RC1 RELEASE FAQ
I think what gefafwisp means is that maybe in the next release, a possible close private alpha/beta testing should be included in the Syscoin dev cycle to avoid this kind of quirks.
Yep
Aye, it is indeed a good idea and something I would think that we will take on-board.
September 22, 2014, 05:29:50 AM
-minus the negativity-
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Spend more time testing and debugging before spending time cleaning up forum posts. What gives? Why are MINOR issues that should have been tested popping up? The general look of unprofessional behavior and programming techniques stands out more than the work that was done.
Devs,
Not sure if my perspective is dead-on, but here goes:
I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.
Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.
General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).
In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.
Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.
Agreed, there is also such a thing as biased testing where because you are a developer you neglect to check other aspects of the software overall. IMO it would be wise to have a third party point of view with regards to testing. Improvements are in order both in the features and in the dev approach but its good that the dev is open to suggestions.
September 22, 2014, 05:26:48 AM
I think what gefafwisp means is that maybe in the next release, a possible close private alpha/beta testing should be included in the Syscoin dev cycle to avoid this kind of quirks.
Yep
September 22, 2014, 05:20:33 AM
The most thing in UI design is user friendly and beautiful, maybe you can hire some expertise in UI degisn, UI is simple to developer, but it's very important to users.
I think a quick round of user acceptance testing would be a big help in this regard. Would just take a very small group a few hours to iron out any howlers (such as this passphrase palava..).
That is the plan going forward as per Dan's post.
Development Release Update!
Introducing the Syscoin Release Candidate Program with v0.1.5 RC1
Release Candidate Program: Feedback | Release Candidate Wallet Download
We have created a thread to hold all the FAQ items for this release, 0.1.5 RC1 RELEASE FAQ
I think what gefafwisp means is that maybe in the next release, a possible close private alpha/beta testing should be included in the Syscoin dev cycle to avoid this kind of quirks.
Jump to: