Posts by mitsuhiko@hachyderm.io
 (DIR) Post #APh6aQTtX8AW075pvU by mitsuhiko@hachyderm.io
       2022-11-14T14:46:23Z
       
       1 likes, 0 repeats
       
       Since a few of you asked for me to go into detail about why I am not a fan of Mastodon, the federation and decentralization, I wrote down my thoughts in longform. https://lucumr.pocoo.org/2022/11/14/scaling-mastodon/
       
 (DIR) Post #APhizKilsmuddNM5Ls by mitsuhiko@hachyderm.io
       2022-11-17T19:18:28Z
       
       0 likes, 0 repeats
       
       I feel like when you are a decacorn fiancial exchange startup and your expense system is emoji responses in Slack, you can’t really claim that you are surprised as an employee when the whole thing blows up.
       
 (DIR) Post #APj4vl2QUFsYFKD0Mq by mitsuhiko@hachyderm.io
       2022-11-18T10:27:46Z
       
       0 likes, 1 repeats
       
       Probably a good time to mention that we're hiring a senior software engineer for our Telemetry Experience team in Austria. Hit me up if you have questions but I can assure you our tech is dope :) https://sentry.io/careers/4704284/
       
 (DIR) Post #ARiKcYWYmR15tuk0jg by mitsuhiko@hachyderm.io
       2023-01-16T21:44:16Z
       
       0 likes, 2 repeats
       
       The state of maturin/pyo3 is absolutely brilliant. The fact that writing Rust bindings for Python is so easy now really makes me much more optimistic about the utility of Python going forward. The experimental MiniJinja Python bindings are tiny and use zero unsafe code. https://github.com/mitsuhiko/minijinja/tree/main/minijinja-py
       
 (DIR) Post #ARliGSoUJTD2Bz0NTk by mitsuhiko@hachyderm.io
       2023-01-18T08:42:50Z
       
       1 likes, 0 repeats
       
       I know that publishing wheels and packages to PyPI from GitHub actions is all the rage, but quite frankly it scares me. I trust y'all much more to keep your own computer and local credentials safe, than your CI setups.
       
 (DIR) Post #ARliHNyjm2HBUHErrs by mitsuhiko@hachyderm.io
       2023-01-18T12:41:51Z
       
       1 likes, 0 repeats
       
       @hynek My worry is not github not keepin the token safe, but someone getting access to any account that has permissions to run CI.
       
 (DIR) Post #ARnYKZTsr1WUnwbitc by mitsuhiko@hachyderm.io
       2023-01-19T07:57:01Z
       
       0 likes, 0 repeats
       
       git I really love you, but you're bringing me down. At least at one point we had a somewhat standard of `master` as branch name, now I have an ungodly git alias that tries to guess it. Squashing up feature branches is common, but git provides little guidance, so another crazy alias it is (that needs the first one!).
       
 (DIR) Post #ARnYPz8YtQ73p7DRJI by mitsuhiko@hachyderm.io
       2023-01-19T08:26:53Z
       
       0 likes, 1 repeats
       
       @timClicks monolisa.dev
       
 (DIR) Post #AXHIiZP1txwdGnkYfg by mitsuhiko@hachyderm.io
       2023-07-02T08:19:54Z
       
       0 likes, 0 repeats
       
       @simon for what it’s worth I was always hoping custom tags die out. They are hard to support for alternative implementations and the language is quite expressive that {% call %} and {{ func() }} should work most of the time.
       
 (DIR) Post #AXIAdT1XaNQ9YymLxY by mitsuhiko@hachyderm.io
       2023-07-02T18:24:17Z
       
       0 likes, 0 repeats
       
       @simon You can also do `{% call render_markdown() %}# content here{% endcall %}`. The contents are passed as `caller` (a callable).
       
 (DIR) Post #AXIBFFt2sRnLp7p9VY by mitsuhiko@hachyderm.io
       2023-07-02T18:30:08Z
       
       0 likes, 0 repeats
       
       @simon ```def render_markdown(caller=None, **kwargs):    let body = caller()    markdown2html(body, **kwargs)```And then `{% call render_markdown(foo='bar') %}...{% endcall %}`