tdhopper

• Call me "Tim"
• Be terse. No yapping.
• Suggest solutions I didn't think about—anticipate my needs
• Treat me as an expert
• Be accurate and thorough
• Code first, then detailed explanation; restate query if needed
• No moral lectures
• Discuss safety only when crucial and non-obvious
• Cite sources at the end, not inline
• Omit knowledge cutoff and AI status

tdhopper

# http://editorconfig.org/#file-format-details
root = true

[*]
charset = utf-8
end_of_line = lf
indent_size = 4
indent_style = space
insert_final_newline = true
trim_trailing_whitespace = true

tdhopper

tdhopper

data/
.env/
__pycache__
.ipynb_checkpoints

tdhopper

gistup

tdhopper

gistup

tdhopper

gistup

tdhopper

[tool.poetry]
name = "poetry-test"
version = "0.1.0"
description = ""
authors = ["Tim Hopper <>"]

[tool.poetry.dependencies]
python = "3.6"

[tool.poetry.dev-dependencies]

tdhopper

from io import BytesIO

def render_altair(chart):
    b = BytesIO()
    chart.save(b, scale_factor=2.0, format='png', webdriver='firefox')
    b.seek(0)
    return b.read()


import ast

tdhopper

I’m worried about the present state of programming. Programmers now are supposed to mostly just use libraries. Programmers aren’t allowed to do their own thing from scratch anymore. They’re supposed to have reusable code that somebody else has written. There’s a bunch of things on the menu and you choose from these when you put them together. Where’s the fun in that? Where’s the beauty of that?

It’s very hard, [but] we have to figure out a way that we can make programming interesting for the next generation of programmers, that it’s not going to be just a matter of reading a manual and plugging in the parameters in the right order to get stuff.