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

[emski]

Welcome!
Nice introduction!
Good Luck and Have Fun!

[roadscape]

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.

[xeroc]

• Contribute to the wiki by cleaning/simplifying/elaborating
  
  • I plan to make this a habit for every new aspect I explore.
  • I'm good at simplifying and documenting procedures.

Awesome! .. The wiki can need every helping hand ..
I hope that I can jump in soon to refresh parts of the content.

• Study how the RPC system and various toolkits work

It's quite simple:
https://github.com/xeroc/pytshares/blob/master/btsrpcapi.py

• Play with market-maker bots (I'm excited to do this)

Alternative implementation with updates and a 'balancing' bot:
https://github.com/xeroc/btsx_bots

• Leave all documentation better than I found it and write it if it doesn't exist

Yeah!

Eagerly await to see you contributions ..

[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!

[roadscape]

I'm a coder/sysadmin by trade, eager to contribute to this grand philosophy.
I'd love to be able help with important things like bugs, stability, and core features.
There's a lot to learn, so I'm starting with the basics.


I'm launching a delegate as the first step of my initial learning plan:

• Build bitsharesx, learn the CLI basics, launch a delegate, publish price feeds
• Reflect on what I can offer; write a delegate bid
• Contribute to the wiki by cleaning/simplifying/elaborating
  
  • I plan to make this a habit for every new aspect I explore.
  • I'm good at simplifying and documenting procedures.
• Study how the RPC system and various toolkits work
• Play with market-maker bots (I'm excited to do this)
• (I'll keep an updated roadmap as I progress in my quest)

Some potential "beginner projects" I'm excited about:

• Working with and enhancing delegate automation tools
• Pulling data/reports from blockchain
  
  • (I love working with and adding value to large data sets)
• Learning about and improving external parts (e.g. price feed scripts)
• Communicating with the blockchain from web apps
• Dip my toes into BitShares code by studying and hunting bugs
• to be continued...

Throughout all of this, I will:

• Keep the delegate up-to-date, publish all feeds, and be quick to adopt and adapt
• Engage with other developers and contribute to the extent my skill level permits
• Leave all documentation better than I found it and write it if it doesn't exist
• Engage on a local level (3 of us have schemed on a weekly basis for the last 2 weeks )
• Help others interested in following a similar path

Support my quest to learn, document, and
contribute to the technical aspects of the BTS vision.

delegate.roadkill
BeyondBitcoinX / delegate.roadkill

• Are there any resources for new devs I should know about?
• Active developers: how did you get started?
• Potential developers: what's holding you back?
• What are some good starter projects for apprentice devs?
• Questions/feedback?