MasterLeon79
New Member
- Joined
- Dec 31, 2014
- Messages
- 213
- Reaction score
- 0
I've been struggling with the bot from the beginning and not even the 1Euro-3days-Trial was able to satisfy or make me believe in this bot. This bot could be a hit and practically own all other bots out there (including viper - i already subscribed to them but to be honest they have a simple grind bot) if developers would pull themselves together and work on existing problems instead of relying on others (the community) to do their jobs and research.
I have been working for a software firm for a couple of years (as project manager most of the time arguing with the dev department) and I know how hard it is to follow each and every issue or even resolve them - but this is what you guys are paid for isn't it? I came along posts that showed me even the bug-tracking is done by the board. There are lots of free software out there that you can install to your server to make bug-tracking very easy and good to overview - why use a public board?
Now my 3-days-subscription has expired and from what I can tell now is that I won't be buying another one or the one for 1-year for that matter.
The lack of understanding customers needs, the information flow, workflow and severe bug-tracking issues will inevitably destroy what's left of this bot.
I am not a critic, as I wrote you very often now I see a lot of potential in this bot (and I want to recommend it to my botting community) - what I'm trying to do is to give you an insight and maybe let you know what most probably a lot of users are thinking (yeah, I've been surfing the board a lot since 3 days). I was also aware that the support of this bot was crashtalked pretty hard. Not only here on this board but also on external boards like elite-pvper, viper (well of course they did it here) and ownedcore just to name the 3 largest sites. But I use to build my own opinion and that is why I'm here.
On the other hand: it states "community-driven application" on the site but I think somebody has been mislead on the definition of these words.
community-driven states that the community are given the choice on how the application should work including suggestions of i.e. modules/plugins BUT it doesn't mean that the community should be given the responsibility to actually manage everything - this is how bots like angelbot (AION) vanished from the plattform and had to be rebuild.
There's an old and very wise saying in german: "to many cooks mess up the soup" which basically means the more people independently contribute to the development of the bot the more error-prone it will be and the more work it means to the developer.
Edit:
Ok I don't want to leave without any suggestions because frankly its always easier to give a critic but really hard to back them up with suggestions:
Bug-Tracking
Depending on the size of your group/company consider to use either Jira or the free Version or mantis (here is a set of really good suggestions: Top 10 Open Source Bug Tracking System)
Priority Handling
1 - Bugs
Can be subdevided to critical, blocker denpeding on if the bug causes the bot not to work at all (blocker)
(if you decide to include guidelines to your development process)
It's good to have the prioritized after bugs and before any new implementations or changes
2 - Changes
Changes to existing plugins and modules
3 - Improvements
New implementations into the bot to improve its handling and reliability
Regarding the management:
DON'T give the community your jobs. There are reasons why implementations that have been suggested (by the community) should be discussed and properly worked out by either a team of advisers or the team of developers. Pick a few stone-hard users to test your implementations. Use releases (alpha for devs, beta for selected member and then the chargeable stable for the rest of the community). Trust me this will not only improve your internal process management it will (most importantly) improve the reliability of your app and your reputation.
I have been working for a software firm for a couple of years (as project manager most of the time arguing with the dev department) and I know how hard it is to follow each and every issue or even resolve them - but this is what you guys are paid for isn't it? I came along posts that showed me even the bug-tracking is done by the board. There are lots of free software out there that you can install to your server to make bug-tracking very easy and good to overview - why use a public board?
Now my 3-days-subscription has expired and from what I can tell now is that I won't be buying another one or the one for 1-year for that matter.
The lack of understanding customers needs, the information flow, workflow and severe bug-tracking issues will inevitably destroy what's left of this bot.
I am not a critic, as I wrote you very often now I see a lot of potential in this bot (and I want to recommend it to my botting community) - what I'm trying to do is to give you an insight and maybe let you know what most probably a lot of users are thinking (yeah, I've been surfing the board a lot since 3 days). I was also aware that the support of this bot was crashtalked pretty hard. Not only here on this board but also on external boards like elite-pvper, viper (well of course they did it here) and ownedcore just to name the 3 largest sites. But I use to build my own opinion and that is why I'm here.
On the other hand: it states "community-driven application" on the site but I think somebody has been mislead on the definition of these words.
community-driven states that the community are given the choice on how the application should work including suggestions of i.e. modules/plugins BUT it doesn't mean that the community should be given the responsibility to actually manage everything - this is how bots like angelbot (AION) vanished from the plattform and had to be rebuild.
There's an old and very wise saying in german: "to many cooks mess up the soup" which basically means the more people independently contribute to the development of the bot the more error-prone it will be and the more work it means to the developer.
Edit:
Ok I don't want to leave without any suggestions because frankly its always easier to give a critic but really hard to back them up with suggestions:
Bug-Tracking
Depending on the size of your group/company consider to use either Jira or the free Version or mantis (here is a set of really good suggestions: Top 10 Open Source Bug Tracking System)
Priority Handling
1 - Bugs
Can be subdevided to critical, blocker denpeding on if the bug causes the bot not to work at all (blocker)
(if you decide to include guidelines to your development process)
It's good to have the prioritized after bugs and before any new implementations or changes
2 - Changes
Changes to existing plugins and modules
3 - Improvements
New implementations into the bot to improve its handling and reliability
Regarding the management:
DON'T give the community your jobs. There are reasons why implementations that have been suggested (by the community) should be discussed and properly worked out by either a team of advisers or the team of developers. Pick a few stone-hard users to test your implementations. Use releases (alpha for devs, beta for selected member and then the chargeable stable for the rest of the community). Trust me this will not only improve your internal process management it will (most importantly) improve the reliability of your app and your reputation.