go to PyOhio 2016

[chadwhitacre]

July 30-31

http://pyohio.org/

CFP is open until May 15

[chadwhitacre]

Talk idea: "Now where did that $1,000,000 go?" Talk about the Great Accounting Cleanup of 2016, and all the Python scripts we've written along the way. Could be fun. :-)

[chadwhitacre]

• scraping (maybe? this could be too trivial to be interesting, or could be a nice warmup)
• converting JSON to CSV via SQLite
• backfilling
• backfilling, again
• extracting from PDFs via TETML
• whatever Python we land on for the books themselves (cf. convert to GnuCash finances#22)

[chadwhitacre]

Could be fun to organize this around Inception. Levels something like:

1. Reality: We need to run Gratipay!
2. Van Chase: We need financial reports!
   • balance sheet
   • income statement
   • cashflow statement
3. Hotel: We need an accounting system!
   • Ledger, GnuCash, tooling around it/them ...
4. Snow Fortress: We need data!
   • Scraping HTML, JSON, CSV, PDF, ...
5. Limbo: We need clean data!
   • Matching transactions and exchanges

The "kick" is the loading of data back up into the system.

Hmm ... ETL as inception ... :-)

[chadwhitacre]

Or maybe Snow Fortress is ETL, and Limbo is schema fixes (gratipay/gratipay.com#3822).

[chadwhitacre]

Something like:

1. Reality: We need to run Gratipay!
2. Van Chase: We need financial reports!
   • balance sheet
   • income statement
   • cashflow statement
3. Hotel: We need an accounting system!
   • Ledger, GnuCash, tooling around it/them ...
4. Snow Fortress: We need data! ETL:
   • Extract data from HTML, JSON, CSV, PDF (via XML), microfilm (via dead trees) ...
   • Transform data—matching transactions to exchaaaaaaaaaaaaaanges.
   • Load data into the database (easy part).
5. Limbo: We need to fix our schema!
   • NOT NULL constraints (avoid null route, ref, and status in new exchanges gratipay.com#3822)
   • immutable primary keys (use id as primary key instead of username gratipay.com#835)

[chadwhitacre]

The call for proposals has been extended to June 4!

https://twitter.com/pyohio/status/731506166036041730

[kzisme]

I just got tickets as well 💃

[kzisme]

@whit537 Are you still planning on heading out on Saturday? I plan on making my way there!

[chadwhitacre]

Yes! My plan is to be at PyOhio on Saturday morning for a bit. Look for the penny puncher! 💃

[kzisme]

I shall! How long are you planning on sticking around for?

Anything I should know as a first time conf go-er?

[chadwhitacre]

I'll probably leave around lunchtime. Meet people and have fun! 😄

[chadwhitacre]

Missed you, @kzisme! Next year? :)

https://twitter.com/cmbeelby/status/759425485789167616

[chadwhitacre]

Also rep'd COS. :)

https://twitter.com/heartdefense/status/759469405562699776
https://twitter.com/whit537/status/759871631934185472

[chadwhitacre]

The most important part of PyOhio for me was apologizing face-to-face to some people for the Gittip crisis (cf. #319 (comment)). Not everyone I may have liked but to several. There was one apology in particular that was super awkward and difficult ... and good. 😥

[chadwhitacre]

Other than that it was fun to be there. I like that conference a lot. :-)

Okay! To next year! :)