Physical engineering is a huge welcome transition for me from what coding has become in the last couple years.

There’s something nice about the realities of creating a model, then printing it, then seeing that exact is too exact, then reprinting, then eight more times, and then that feeling when it all comes together properly.

A few weeks ago I was working on an adapter for an airbrush to use on a standard pancake air compressor. Learning to create threads in blender was really neat! I learned a lot about the physical construction of threads, something I have never put much thought into before.

As long as I don't let it control the pod bay doors, I should be fine.

The basic idea is that when one failure fans out across 20 services, you often end up with 20 alerts and 20 separate investigations, even though there is really just one root cause. I’m using distributed tracing to build a live model of how errors propagate through the system, and then exposing that context directly at each affected service.

Longer term, I want this to become a very high-precision RCA engine. Right now I’m looking to try it with a few early design partners that already have a lot of tracing data, especially OpenTelemetry or Datadog APM users. I'll love to chat with some folks who would be willing to try it out!

https://pikkoloassembly.com/

An LLM observability SDK that let's you store pre and post request metadata with every call in as lightweight an SDK as possible.

Stores to S3 in batched JSON files, so can easily plug into existing tooling like DuckDB for analysis.

It's designed to answer questions like; "how do different user tiers of my services rate this two different models and three different systems prompts?". You can capture all the information required to answer this in the SDK and do some queries over the data to get the answers.

- No sign-up, works entirely in-browser

- Live PDF preview + instant PDF download

- Flexible Tax Support: VAT, GST, Sales Tax, and custom tax formats with automatic calculations

- Shareable invoice links

- Multi-language (10+) and 120+ currencies

- Multiple templates (incl. Stripe-style)

- Mobile-friendly

- QR Code Support: Add payment QR codes with any invoice-related information (payment links, UPI, contact details, custom data)

- Multi-Page PDFs: Seamless multi-page support with automatic pagination and page breaks

GitHub: https://github.com/VladSez/easy-invoice-pdf

Would love feedback, contributions, or ideas for other templates/features.

PS: e-invoice support is wip

Instead of building scrips here and there I'm attempting my own everything app. Lets see if that's a good idea :).

Starting with android home screen and widget sync to server/desktop. So e.g. calendar notifications happen desktop first, then escalate to mobile etc. Also phone as mousepad (for using my projector from bed). Just feature creeping it all in without regrets so far.

In general I feel like feature creep needs to be reevaluated. UX must not be destroyed, but features cost less now.

Check out this twisty vase demo: https://nodillo3d.com/s/VmP0nJdKRcPazQ1g

You can also share you files and create sharable configurations as well. Here is the same vase as a configurator: https://nodillo3d.com/v/a9REIEZIDYGtzZRA

I would like to do a more detailed intro class to help people learn how to model with nodes.

Hope you enjoy it!