Home

#Jtime (11 Oktober)

J is a lead developer at Blockchain Foundry which is persuing different ways of bringing value to any kind of business sector out there by using the Syscoin blockchain.

Due to the limitations of Slack, the AMA's will be stored here for further reference and reading.

J [12:45 AM]
*Welcome* again! Hope all is well in your worlds today. From the development front, not much new to report that hasn't already gone into community-dev. However a couple of things that I don't remember whether I noted or not...

- in preparation for their eventual open-sourcing, we're making some changes to _indexer-api_ and _syscoin-indexer_ to also make them npm-packagable in the event people also want to utilize them *within* the context of their existing projects (similar to what we've done for _syscoin-api-server_)

Most of the dev group is busy working on Pangolinish stuff which isn't much of a change in status there.

Definitely worth noting from a dev team perspective is that @keyare is now the Director of Product Management and Quality Assurance, which formalizes the already phenomenal role he's been playing on this front - I know the entire dev team is super pumped about that one
On a non-BCF but certainly awesome front I wanted to highlight @Zontar’s work on SYSIO, which you can see here:

https://www.razorwire.io/api/sysapi.dll/
And that's it! I'll have Slack open for the next while if there are questions and if not, enjoy your day!!

J [1:54 AM]
Radness! *Finally* we're getting to quieter times!! :smiley: Thanks for existing, and I'll see you ladies and gentlemen here next week around 1 PM PST!

leo [2:12 AM]
When moon?
Why did you offer jtime to begin with? (my cellphone broke for a month and i missed many problems...)

J [2:26 AM]
Yeah, you missed a bunch - this was the 4th or 5th I think...
@leo Mostly to
a) provide some clarity on different items I saw repeated over and over...and over...and *over* on Slack that I had/have some insight into and could answer, particularly when it came to explaining things about the development process and development focused stuff.
b) over time through the spread of information, get the signal to noise ratio on Slack back to something acceptable + get people in a more comfortable (read: knowledgeable) state
For example, I used to see near daily confusion/frustration/discussion around BMW and other related projects in Syscoin/BCF land. That seems to have levelled off in this Slack massively in the last few weeks as more light has been shed on what's been happening (and that's not credit to me - a bunch of BCFers or ex-BCFers have been communicating actively here in the last while). (edited)

shrill [2:57 AM]
joined #jtime. Also, BigPoppa left.

redrace [7:07 AM]
Thanks J
And having no questions for once is indeed a good thing after the storm of questions and repetition, thanks for grinding through them and in this way creating clearity for wandering mind

blocknugget [10:10 AM]
we're all patiently waiting for the fantastic revelations that are no doubt due :wink:J [12:45 AM]
*Welcome* again! Hope all is well in your worlds today. From the development front, not much new to report that hasn't already gone into community-dev. However a couple of things that I don't remember whether I noted or not...

- in preparation for their eventual open-sourcing, we're making some changes to _indexer-api_ and _syscoin-indexer_ to also make them npm-packagable in the event people also want to utilize them *within* the context of their existing projects (similar to what we've done for _syscoin-api-server_)

Most of the dev group is busy working on Pangolinish stuff which isn't much of a change in status there.

Definitely worth noting from a dev team perspective is that @keyare is now the Director of Product Management and Quality Assurance, which formalizes the already phenomenal role he's been playing on this front - I know the entire dev team is super pumped about that one
On a non-BCF but certainly awesome front I wanted to highlight @Zontar’s work on SYSIO, which you can see here:

https://www.razorwire.io/api/sysapi.dll/
And that's it! I'll have Slack open for the next while if there are questions and if not, enjoy your day!!

J [1:54 AM]
Radness! *Finally* we're getting to quieter times!! :smiley: Thanks for existing, and I'll see you ladies and gentlemen here next week around 1 PM PST!

leo [2:12 AM]
When moon?
Why did you offer jtime to begin with? (my cellphone broke for a month and i missed many problems...)

J [2:26 AM]
Yeah, you missed a bunch - this was the 4th or 5th I think...
@leo Mostly to
a) provide some clarity on different items I saw repeated over and over...and over...and *over* on Slack that I had/have some insight into and could answer, particularly when it came to explaining things about the development process and development focused stuff.
b) over time through the spread of information, get the signal to noise ratio on Slack back to something acceptable + get people in a more comfortable (read: knowledgeable) state
For example, I used to see near daily confusion/frustration/discussion around BMW and other related projects in Syscoin/BCF land. That seems to have levelled off in this Slack massively in the last few weeks as more light has been shed on what's been happening (and that's not credit to me - a bunch of BCFers or ex-BCFers have been communicating actively here in the last while). (edited)

shrill [2:57 AM]
joined #jtime. Also, BigPoppa left.

redrace [7:07 AM]
Thanks J
And having no questions for once is indeed a good thing after the storm of questions and repetition, thanks for grinding through them and in this way creating clearity for wandering mind

blocknugget [10:10 AM]
we're all patiently waiting for the fantastic revelations that are no doubt due :wink:

Redrace
October 11, 2018

Connect with Syscoin