bulte-rs

$COMPANY is on Github now, thinking of moving to Codeberg/Forgejo.

This is a personal pet project, just to see what it might look like, how it would work, to satisfy personal curiosity. If it comes to the point that it actually becomes usable for the team (read: actually add value), then it's up to $TEAM to decide whether to use it or not.

I would hate my team to waste company time on such an endeavour. ;-)

I use AppSignal for my side projects AND the two products we have @company. Strikes a good balance between logging/metrics/traces. The hosted OTEL collector is nice!

(disclaimer: I'm a vendor to AppSignal; to add: awesome people to work with!)

Why care about making a commercial alternative? I just want a “forge” for my team that looks like a combination of GitHub and tangled (stacked PRs and JJ).

So I’m working on waza.sh. I have NO intent on making it commercial, nor open-source (unless someone wants to collab on it).

Will it need compute? Yes! For my team only. So a dedicated box at OVH/Hetzner for 30eu is more than sufficient.

I'm a football/soccer coach (youth, U12 and U19).

Got started as a "temp" for my sons mini-team (back when he was 5). Temporary turns into UEFA certified youth trainer/coach real fast. It's no longer just about the kids (sorry guys), but a really awesome hobby with lots of personal development paths.

Chief Executive Nerd checking in!

Hmmm… my wife constantly reminds me that I behave like a 16 y/o child. Perhaps ICQ should be reborn!

This is probably a huge reasoning error, but wouldn’t you “expand away” with the expanding away part of the universe at the same rate, sort of riding along with the expansion given that c is the same in the point of reference (the expanding away faster than c part)?

n.b. I obviously lack the vocubulary to communicate properly about this, help needed!

Perhaps anecdotal, but I have never got any negative response on answering “no, we do not enforce password rotation as this is against NIST recommendations.”

If you - or others here - are interested I can spend some time to clean-up my own "boilerplate" a bit.

It's using Golang + Chi + Templ, uses SQLite as its database and has a multi-tenant-multi-db setup by default (i.e. 1 master database for user/tenant management, and "stem-data", 1 sqlite database per tenant), and uses passkeys for authentication. I'm using some HTMX + Hyperscript + a really small amount of plain-js for passkeys in the apps themselves.

I reckon that switching out Chi for Fiber - for the boilerplate only - would take about 90 minutes.

Edit: Forgot to include TailwindCSS. So for completeness sake.

Former airline pilot checking in!

Remember the importance of checklists in the "grand scheme of things". It helps maintain proper "authority" during operation and makes sure you don't forget things. If you don't write it down and check it, someone, at a certain moment will forget something.

Also, the "Aviate, navigate, communicate" axiom (as mentioned by author) is really helpful if you're trying to setup incident/crisis response structures. You basically get your guiding principles for free from an industry that has 100+ years of experience in dealing with crisises. It's something I teach during every incident/crisis response workshop.

edit: Although it's not aviation specific, and a little light on the science, "The Checklist Manifesto" by A. Gawande is a nice introduction into using (and making) checklists.

Care to elaborate on the use of past tense?

I.e.: are you no longer in business, sold it or no longer running it solo?

Getting a visa is definitely easier than getting a passport. My advise is to look for a good employer, and have a relocation agency take care of the rest. They know what to do and know the intimacies of - e.g. - tax benefits you might be eligible for.

(n.b. Not immigration specialists but married to expat tax advisor)

Let’s turn that around: Let me know if I can help! ;)

Thanks for making this!

Started playing (or trying to) a few weeks ago and spending almost my entire evening practicing fur Elise.

The evolution of the setup is the thing I'm aiming for. Right now it's plain, simple stupid. But if the progression of challenges is the same this year when compared to 2019, then reusability will come in handy, and a more involved setup might be appropriate. ;-)

edit: thanks for pointing out the erred link, updated.