in which glasnt has thoughts
This post is a text version of the code samples and resources from Golang for Python Devs by Dana Garifullina from Kiwi PyCon 2016. Some resources no longer work, so I’ve updated to the most accurate thing I can find. Some Python samples were Python 2, updated to Python 3. Most code OCR’d, may contain translation issues Hello World Python print ( "Hello World!" ) Golang package main import "fmt"…
Happy to announce that after learning my way around research papers with ACROSS , I’ve published a new paper. Sadly I don’t have a journal to contribute to (I’m still learning that part without guidance), but I’ve pushed the PDF and raw data up on GitHub . This one was a long time in the making (original research was from 2019), but hopefully it’s now in a form that can be shared with the…
I’ve recently been learning more about Generative AI and LLMs as part of my day job, and was having problems understanding some of the concepts. Evals, fine tuning, etc; it was all confusing to me. Until I had an epiphany, and realised that I already have a mental model for this sort thing already: containers . Dockerfiles that build containers are just instructions to build a tarball. That…
Previous articles: 2015 , 2016 , 2017 , 2018 , 2019 A decade ago today, I gave my first conference presentation. Talk 95 - Where should I run my code? Dublin, Ireland, Nov 2019 ~ much time passes ~ Talk 124 - Present like a pro, Wellington New Zealand, Aug 2024 Well. The last five years. What can be said that hasn’t been said many times already. I ended up working for exactly one year as a…
In both my day job and my community work, I use GitHub. A lot. And I’m asked to review code on GitHub. A lot. At the time of writing I have over 100 review requests on the platform. When I have things that require reviewing, I’m normally notified by email. But the email footer doesn’t tell me much about why I was requested. I can also use the Review requests page to view all my requests. In this…
One of the neat features when developing in Cloud Run was knowing you can use gcr.io/yourproject as a place to push your Docker containers. This is a Container Registry (the CR in GCR.io), and would be available as soon as you created your project, ready for your containers. Container Registry’s implementation included the interesting detail that the container layers you pushed would end up in…
A lot of writing on this blog stems from meta content about the blog. This is completely fine. It also helps me pinpoint that it’s been 9 years since I first moved my content into Jekyll. I was using the integrated GitHub Pages functionality (a website that seems to have not changed much since I first migrated to it), but one of the issues I’ve written about it before is that I was locked to the…
In Cloud Build, you can create steps , with each step using a base image. Images can be common ones to interact with gcloud or docker , but you can also create your own. When building custom images in Docker, you might have your ENTRYPOINT as the name of an executable, then you can send various runtime parameters to it. How the docker Cloud Builder image is defined in the Dockerfile However, when…
If you’re using Infrastructure as Code for declaring your serverless applications, you may encounter issues if you’re relying on latest container tags. latest is used in Docker when there is a lack of tag – if you’re not using other tags, it will typically be the most recent image to be built, as therefore “latest”. However, if you’re using tools like Terraform, you may be declaring this image…
When using Cloud Build pull request triggers , especially when the trigger is to run tests, you’ll traditionally be running your “run my unit tests please” command which will run every test across your entire repo. But in cases where that takes a long time, it might be useful to only run tests for pull requests across the code that’s been changed. You might be familiar with using a test suite that…