Recently a lot of the JuliaLang community showed up on BlueSky. Which is interesting times for me, who has been on there for quite a while. Since it results in me having a very split following in demographics. I wanted to analyse that, and I thought I would take the opertunity to write a bit about how to access the bsky API using Julia.
This post brought to you by the same manic “I gotta stay awake to move my body clock to Boston” as last night’s blog post. But it’s even more manic, as I am very much jetlagged now. Expect typos. And weird digressions. Anyway, topic this time is metaprogramming patterns. In particular patterns for how to use eval at the top level.
Hiii, it’s ya girl. She is sleep deprieved because she need to adjust her sleep cycle 12 hours to prepare for JuliaCon 2023 in Boston. Thus this blog-post is coming to you fresh from the small hours of the morning in Australia, to keep me awake. Expect this to be more manic than usual. I am here today to tell you that you are probabl wrong about what top-level code in julialang does. Though if you…
As a trans-femme on HRT, I would like to know the concentrations of estradiol in my blood at all hours of day. This is useful as the peak, the trough and average all have effects. However, I only get blood tests a finite number of times per day – usually once. I am not a medical doctor, but I am the kind of doctor who can apply scientific modelling to the task of estimating curves based on limited…
Julia 1.0 came out well over 2 years ago. Since then a lot has changed and a lot hasn’t. Julia 1.0 was a commitment to no breaking changes, but that is not to say no new features have been added to the language.
Griewank and Walther’s 0th Rule of algorithmic differentiation (AD) states: Algorithmic differentiation does not incur truncation error. (2008, “Evaluating Derivatives: Principles and Techniques of Algorithmic Differentiation”, Andreas Griewank and Andrea Walther.) In this blog post I will show you a case that looks like it does in fact incur truncation error. Though this case will arguably be a…
An antipattern is a common solution to a problem that over-all makes things worse than they could have been. This blog post aims to highlight a few antipatterns common in Julia code. I suspect a lot of this is due to baggage brought from other languages, where these are not Antipatterns, but are in fact good patterns. This post is to clear things up.
One of the most remarkable things about the julia programming language, is how well the packages compose. You can almost always reuse someone else’s types or methods in your own software without issues. This is generally taken on a high level to be true of all programming languages because that is what a library is. However, experienced software engineers often note that its surprisingly difficult…
If you follow my blog, it may look like I am blogging a fair bit less this last year. Infact I am blogging just as much, but collaborating more. So my posts end up hosted elsewhere. Also since I am no longer the only julia user in 3000km, I am giving more talks. For this post I thought I would gather things up so I can find them again.
TL;DR; Every Pull Request should increment the version number in the Project.toml, and then you should register the release immediately after merging. Why do this? Because people are making PRs to your repo because they want that change. Don’t make them wait for you to tag a release. Also for all the normal advantages of continuous delivery.