delegate.roadkill, community apprentice developer

[roadscape]

Roadkill is an individual I support based on conversations had outside this forum. Roadkill is contributing to this community in meaningful ways and will benefit the delegate ranks as a code reviewer, active community participant and ultimately feel will make development contributions based on his qualifications and drive.

Appreciate your support, thanks Fox!

Cheers man, you've got my vote!

Likewise!

Welcome!

 

[roadscape]

Great intro Roadkill.
I support you.  I think you will make really solid contributions!
Cheers!

Thank you!

Yes.  THis would be the easiest.   Or we split off somewhere else that is less noisy.  I don't really care, but it would be interesting to have a place where devs can discuss their issues with the toolkit.  Keeping it here is probably the best as the actual devs are more likely to read it here.

Sent toast a PM. We'll see what he says.

I expect to be asking a lot of technical questions, and it makes sense for those conversations to be in public.
"Dev Support" belongs in "Tech Support" but it should be tucked away.

[donkeypong]

Welcome!

[Method-X]

Cheers man, you've got my vote!

[Fox]

Roadkill is an individual I support based on conversations had outside this forum. Roadkill is contributing to this community in meaningful ways and will benefit the delegate ranks as a code reviewer, active community participant and ultimately feel will make development contributions based on his qualifications and drive.

Edit:fix typo

[gamey]

So where are the spots where devs talk?  There is a skype channel but it isn't that optimal as most of the devs are too busy to answer the more basic questions.  (Well, I'm saying that I wouldn't ask basic questions, not that they refuse to answer them.  All the devs I met in Vegas seemed like great guys.)

So I'd like to see a sub-community somewhere where the conversation is strictly at the developer level without extraneous noise.

IRC channels are ok, but they end up being lurkfests.

Maybe we need a Developers board under Technical Support?

Yes.  THis would be the easiest.   Or we split off somewhere else that is less noisy.  I don't really care, but it would be interesting to have a place where devs can discuss their issues with the toolkit.  Keeping it here is probably the best as the actual devs are more likely to read it here.

[roadscape]

Welcome!
Nice introduction!
Good Luck and Have Fun!

Thanks, already am

[lovejoy]

 

Great intro Roadkill.
I support you.  I think you will make really solid contributions!
Cheers!

[roadscape]

So where are the spots where devs talk?  There is a skype channel but it isn't that optimal as most of the devs are too busy to answer the more basic questions.  (Well, I'm saying that I wouldn't ask basic questions, not that they refuse to answer them.  All the devs I met in Vegas seemed like great guys.)

So I'd like to see a sub-community somewhere where the conversation is strictly at the developer level without extraneous noise.

IRC channels are ok, but they end up being lurkfests.

Maybe we need a Developers board under Technical Support?

[gamey]

So where are the spots where devs talk?  There is a skype channel but it isn't that optimal as most of the devs are too busy to answer the more basic questions.  (Well, I'm saying that I wouldn't ask basic questions, not that they refuse to answer them.  All the devs I met in Vegas seemed like great guys.)

So I'd like to see a sub-community somewhere where the conversation is strictly at the developer level without extraneous noise.

IRC channels are ok, but they end up being lurkfests. 

[svk]

Is there an advantage to writing these tools in Python and not, say, Ruby?

Yes .. I don't speak ruby 

Yea to each his own, I'm using nodejs

[xeroc]

Is there an advantage to writing these tools in Python and not, say, Ruby?

Yes .. I don't speak ruby 

[roadscape]

Thanks xeroc! Glad to see RPC isn't daunting at all. Excited!!

Is there an advantage to writing these tools in Python and not, say, Ruby?

[xeroc]

There are open source parsers for Bitcoin, and someone here started working on one for Bitshares but not sure who that was, someone who was documenting the blockchain

That was "drltc" .. afair

[svk]

Nice intro and glad to have you on board! To add to your "various toolkits", wackou has made a very nice-looking delegate control tools that could do with some more documentation as well as peer review, that could be a good place to start!

https://github.com/wackou/bitshares_delegate_tools

For your final questions: I got started by simply jumping in. I've been coding and learning as we go, lots of positive feedback kept me motivated.

If you're looking for another project, a full-fledged blockchain parser is something we're missing atm..

Best of luck to you!

Thank you! wackou's work looks excellent, I will definitely be testing it out.

What are the use cases for a full blockchain parser?
Sounds like it's right up my alley.

It will allow us to perform more in-depth analysis of the blockchain than what's available through the RPC calls, and also to develop specialized retrieval functions that aren't really necessary in the client. One use case is retrieving blockchain information for a given point in time, such as share supply at block X for example. That kind of thing isn't available through RPC calls.

It might enable some deep analysis to circumvent TITAN restrictions too, but not sure about that.

There are open source parsers for Bitcoin, and someone here started working on one for Bitshares but not sure who that was, someone who was documenting the blockchain.

https://github.com/bkchain/bkchaind