Kyle DowneyCross-compiling C++ with Bazel and Wolfi
rules_apko, toolchains_llvm and Wolfi
Kyle DowneyLeft of Launch: Questioning the Speed-Quality Tradeoff in Software Engineering
The concept “left of launch” comes from missile defense: in the timeline, the events that happen before the missile launch are to the left; this is where the idea of Shift Left in QA testing comes from as well. You can apply this idea to building code, unit testing, benchmarking and even security scanning: the common thread is that in all these things when there is a mistake of some kind, you want it to become apparent as soon after the mistake is made as possible. Why you might want that, an...
Kyle DowneyPre-Building Standard Devcontainers with GitHub CI
To support Left-of-Launch quality checks and ensure a consistent development environment straight out of GitHub, I make extensive use of VS Code’s devcontainers. The one problem is once you have built up a large set of tools, the time to rebuild the container gets to be quite long -- unnecessarily so, because the vast majority of the layers in the container never change. Ideally we want the majority of our core features to just be available as a pre-built image. If you search for how to do th...
Kyle DowneyCross-compiling C++ with Bazel and Wolfi
rules_apko, toolchains_llvm and Wolfi
Kyle DowneyLeft of Launch: Questioning the Speed-Quality Tradeoff in Software Engineering
The concept “left of launch” comes from missile defense: in the timeline, the events that happen before the missile launch are to the left; this is where the idea of Shift Left in QA testing comes from as well. You can apply this idea to building code, unit testing, benchmarking and even security scanning: the common thread is that in all these things when there is a mistake of some kind, you want it to become apparent as soon after the mistake is made as possible. Why you might want that, an...
Kyle DowneyPre-Building Standard Devcontainers with GitHub CI
To support Left-of-Launch quality checks and ensure a consistent development environment straight out of GitHub, I make extensive use of VS Code’s devcontainers. The one problem is once you have built up a large set of tools, the time to rebuild the container gets to be quite long -- unnecessarily so, because the vast majority of the layers in the container never change. Ideally we want the majority of our core features to just be available as a pre-built image. If you search for how to do th...
Subscribe to Kyle Downey
Subscribe to Kyle Downey
Share Dialog
Share Dialog
Many years ago Jerry Pournelle wrote a column for the now-defunct Byte magazine called Computing at Chaos Manor. Nowadays a lot of system administrators and developers are homelabbing and writing about it, but he was probably one of the pioneers, so the title here is a nod to that history. As I am getting back to regular hobbyist software development and being our home’s Bastard Operator From Hell, I wanted to write more about that as well. In the past I have written while building both hardware and software, and I have found that it’s the best way to learn: read about it; do it; teach others what you learned.
In this blog I’ll be covering:
DevOps and cloud engineering
High performance computing techniques
Data structures & algorithms
New developments in software engineering & languages
New developments in AI
with no particular planned cadence at this time, and no agenda.
As a global disclaimer, all writing here are my own personal opinions and not those of my employer. I have written on trading and markets as well in the past, and while I am not planning to do so here, none of this constitutes investment advice or a solicitation to purchase securities, and it is presented purely for educational purposes.
Many years ago Jerry Pournelle wrote a column for the now-defunct Byte magazine called Computing at Chaos Manor. Nowadays a lot of system administrators and developers are homelabbing and writing about it, but he was probably one of the pioneers, so the title here is a nod to that history. As I am getting back to regular hobbyist software development and being our home’s Bastard Operator From Hell, I wanted to write more about that as well. In the past I have written while building both hardware and software, and I have found that it’s the best way to learn: read about it; do it; teach others what you learned.
In this blog I’ll be covering:
DevOps and cloud engineering
High performance computing techniques
Data structures & algorithms
New developments in software engineering & languages
New developments in AI
with no particular planned cadence at this time, and no agenda.
As a global disclaimer, all writing here are my own personal opinions and not those of my employer. I have written on trading and markets as well in the past, and while I am not planning to do so here, none of this constitutes investment advice or a solicitation to purchase securities, and it is presented purely for educational purposes.
<100 subscribers
<100 subscribers
No activity yet