351–360 of 1001 posts
It posts a message in your team chat when someone installs, upgrades or uninstalls a Helm chart from your Kubernetes cluster.
It's the first code I've written in a long time and I'm really enjoying it.
* a book of thousands of loglines to inspire writers with writer's block
* a vacation itinerary generator (started months ago, completely useless today)
Right now the FPGA boots the PicoRV32 SoC example code out of the configuration SPI-flash memory of Lattice's ECP5 evaluation board (I started with the firmware in block-RAM, but now it runs right out of the SPI-flash). I also have interrupts working, and have the gcc header file macros for enabling/disabling interrupts and controlling the PicoRV32 timer. I will soon have much more (SDRAM controller, cache, many other peripherals..).
https://github.com/jhallen/radioanalyzer
Also I will port it to this very nice ULX3S board as soon as I get one:
I built it because I frequently find myself looking to onboard (or “reboard”) to a project, and not knowing exactly where to start. After speaking to a bunch of other developers, I didn’t seem to be alone, so it felt like this problem was deserving of some attention.
While documentation can help mitigate this problem, I wanted to explore ways that the codebase itself could become more explainable, without requiring unnecessary context switches. Almost like if every repo had a table of contents. To make it easier to produce these “code tours” I built a tour recorder, that tries to be as simple, and dare I say, fun to use as possible.
I’ve since found that this experience has value in a number of other use cases (e.g. simplifying PR reviews, doing feature hand offs, facilitating team brown bags, etc.), and I’m excited to keep getting feedback from folks as they try it out. It’s also fully OSS, so I’d love any and all contributions: https://github.com/vsls-contrib/codetour.
I'm making a drone that blows bubbles: https://youtu.be/xk99zrlAp9U Hey, you asked.
Soft launched this week. Already getting some exciting results. Working through an issue with the South African based server this weekend because we think the ISP we're using has a crappy network and may have underspecced their servers severely which is causing results to drift way out of the mean. But could also be an overloaded internet over there. We'll probably take ZA offline until Monday. Everything else working great!
I'm working on CallStop, which is Superhuman for your phone number. Here's the app store link: https://apps.apple.com/us/app/callstop-call-manager/id145589... The problem: spam calls. Most current solutions use blacklisting, which doesn't work well. CallStop uses whitelisting, and allows you to accept whitelist requests, pause filtering, or let groups use secret PIN "extensions" to reach you. You can revoke or edit t…
GoDBLedger: https://github.com/darcys22/godbledger
For the most part that backend of the system is working how I want. I now need to build more front end ways to communicate to it.
One of the front end methods I’m working on is programmable journal entries. So you write your journal entries in a JavaScript file which gets executed in the context of the accounting system so you will have full access to the account balances. However this is still early stages:
Yurnell: