Radar 45

[chadwhitacre]

What are you working on this week and why?

last week

[chadwhitacre]

Roadmap (what?)

Short Term

Embarrassments:

• can't edit teams (Team Basics)
• not using immutable ids (use id as primary key instead of username gratipay.com#835)
• widgets are broken (Radar 31 #389 (comment))
• escrow imprecision (Radar 31 #389 (comment))
• no payroll! bring back take-what-you-want gratipay.com#3433
• Team and ~user pages are the same Differentiate participants and projects gratipay.com#3852

Long Term

Color code:

• red—external forces that we're under
• yellow—administration
• green—product development
• orange—marketing
• blue—capitalization

[chadwhitacre]

Okay! @pjz and I just had our monthly Aspen call (AspenWeb/pando.py#537). We are aiming for a 1.0 release on September 19 of this year—10 years since the first commit! :-) I'm gonna write up some notes from the call, and then I wanna work on gratipay/gratipay.com#3870 for @rohitpaulk and then hopefully land gratipay/gratipay.com#3909 with @aandis.

[techtonik]

I am looking at the two red bricks on the diagram. For the last month I was involved with investigation of Payment Law + Companies Law in Belarus. Made a sponsored release for Roundup tracker getting 500 EUR and wasted two weeks trying to figure out how to pay the taxes and understand why I got only 495 EUR. The money will go out really soon though. We've calculated that monthly minimum for living in Minsk is $667 with rent, which is $100 higher than I've earned, and I didn't pay any taxes yet. Banks provide really awful API here - I mean no API at all.

So this is not sustainable without some guaranteed basic income (maybe after some challenge to prove your usefulness).

On a technical side I resumed working on ekalinin/nodeenv#140 to get back to learning JavaScript stack so that I can test what's going on with JS tests in isolated environment and not hunt offending files all over my system.

[rohitpaulk]

!m @whit537 @techtonik

[chadwhitacre]

Inbox 2, GitHub 2, L2 Support 0, Vendors, etc. 0.

[chadwhitacre]

Okay! Turning to #319 ... time to start bringing that in for a landing! 😳

[techtonik]

#319 is a book! 📖 : ♻️ Let's open https://leanpub.com account to get funds for Gratipay development by writing books about all that stuff. =)

[chadwhitacre]

Hah! Maybe some day ... :-)

[chadwhitacre]

I logged into my personal Twitter account for the first time in ... months? My heart is racing. :-)

[kzisme]

Woo!!!
On Feb 9, 2016 3:29 PM, "Chad Whitacre" [email protected] wrote:

I logged into my personal Twitter account for the first time in ...
months? My heart is racing. :-)

—
Reply to this email directly or view it on GitHub
#494 (comment)
.

[chadwhitacre]

😮

[chadwhitacre]

!m @aandis for moving us one ticket closer to landing gratipay/gratipay.com#3399 and the Pivot milestone, with gratipay/gratipay.com#3909. 💃

[chadwhitacre]

Inbox 3, GitHub 1, L2 Support 0, Vendors, etc. 0.

[chadwhitacre]

Picking up with #479 (comment) ...

Another factor here is that I'm not sure about how much I can contribute towards AML, but with Uphold - pretty clear.

I hope to address this by making some tickets and milestones based on gratipay/gratipay.com#3433 (comment).

[chadwhitacre]

Looking at #319—tomorrow's the big day!

[chadwhitacre]

Woo!!!

Baby steps:

https://twitter.com/whit537/status/697803048584740865
https://twitter.com/whit537/status/697804364434448384

First tweets in 10 months. I was on for 3 months before that, and off for 4 months before that.

[chadwhitacre]

Things on my mind:

• Getting determine Gratipay's response to questions about the Gittip crisis #319 out the door
• Team Review 21, especially YAS - MALAWI project-review#156
• @brainwane's CoC feedback: community guidelines - 2 questions #499
• more Inside Gratipay cleanup to support determine Gratipay's response to questions about the Gittip crisis #319
• kicking off Uphold compliance for @rohitpaulk (Payin + Payout via Uphold gratipay.com#3870)
• moving ahead on backfill remaining exchanges gratipay.com#3912 and catch up on books finances#3 with @kaguillera
• might have a new guy showing up to cowork

[chadwhitacre]

Also:

• Review 5 esp. Widgets work with both ~users and Teams grtp.co#112

Things for which I am grateful that they are not on my mind:

• run Gratipay 193 #500 !m @clone1018 @rohitpaulk 💃

[chadwhitacre]

Lunch 1

[chadwhitacre]

Lunch 0. Coffee 0. Gotta knock out a COS review and then ...

[chadwhitacre]

#319 is out the door! 😳

[chadwhitacre]

Interesting! :-)

https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/

via Sue Gardner retweeting

[chadwhitacre]

Psychological safety was far and away the most important of the five dynamics we found -- it’s the underpinning of the other four. How could that be? Taking a risk around your team members seems simple. But remember the last time you were working on a project. Did you feel like you could ask what the goal was without the risk of sounding like you’re the only one out of the loop? Or did you opt for continuing without clarifying anything, in order to avoid being perceived as someone who is unaware?

Turns out, we’re all reluctant to engage in behaviors that could negatively influence how others perceive our competence, awareness, and positivity. Although this kind of self-protection is a natural strategy in the workplace, it is detrimental to effective teamwork. On the flip side, the safer team members feel with one another, the more likely they are to admit mistakes, to partner, and to take on new roles. And it affects pretty much every important dimension we look at for employees.

[chadwhitacre]

To watch: "Building a psychologically safe workplace"

[chadwhitacre]

"What if the better teams have a climate of openness?"

[chadwhitacre]

Psychological safety is a shared belief that the team is safe for interpersonal risk taking. In psychologically safe teams, team members feel accepted and respected. It is also the most studied enabling condition in group dynamics and team learning research.

https://en.wikipedia.org/wiki/Psychological_safety

[chadwhitacre]

Edmondson's 1999 PDF

[chadwhitacre]

Reticketed digesting Edmondson's work further as #501.

[chadwhitacre]

Security 15.

[chadwhitacre]

L2 Support 0, Vendors, etc. 0.

[chadwhitacre]

Security: New 0, Triaged 16.

[chadwhitacre]

Eep!

[chadwhitacre]

Email (what?)