Tody (https://todyapp.com/) an app for household chores. It makes it easy to create chores to do, tune the cadence to do them at, and divide them up by room and by person. It keeps chores more fair and balanced between my wife and I and helps out with those chores that need to happen every few weeks or months and you forget about them. I also am the type of person that needs a clean inbox or 0 unread messages so it definitely works for my brain. I'm sure there are alternatives or systems that work just as well or better but it works well for us so sticking with it until it doesn't.
A small portable scanner. I don't take it anywhere I just got a portable one due to it's size so I can stick it in a drawer.
I've been able to save a bunch of space and get rid of 99% of documents in my filing cabinet by making a digital copy and getting rid of the physical ones. Now when I get an important document I scan it save it to a few places and get rid of it.
Why not just a scanner app for your phone? They work pretty well. I have a flatbed scanner that I keep stored away most of the time, until I need to scan a bunch of stuff quickly. If I need to scan the odd receipt, I use Tiny Scanner.
The main reason was I had 2 filing cabinet drawers filled with paper and wanted something that could be relatively hands off. I was able to do double sided paper and load multiple pages at a time (24 pages before it didn't work well) so it was easy to burn through the them. I've tried a scanner app before for one off things and have had okay success with them. I guess now the backlog is burned down I can compare the two for things that are just a couple of pages.
I ended up getting the Canon imageFORMULA R10 off of amazon but there are a few similar options. Does double sided scanning and I was able to load 24 pages at a time.
As others have mentioned there are apps in the wild that do this. I use a notes app Notion.so which does auth like this.
To be honest I didn't/don't like it because it's an extra step and I use a password manager anyway that makes it easy to fill in my passwords.
As I'm reflecting on it though, it's not that big of deal as I use the mobile and desktop apps which I'm signed into all the time. I would imagine if it were an app I had to log into again all the time or frequently I would be pretty annoyed with it.
I think there can be different types of documentation (tutorials, reference, explanation, how-to guides). I came across this article a while back that goes over different categories and always re-read it when I know I'm going to have to write a bunch of documentation for something and always find it helpful to really think about the type that I need to write. In regards to the poster you replied to I think Oreilly books are in the explanation category of documentation instead of the traditional reference kind found online.
I was actually looking for something like this, good to know a product like this exists.
I use a combination of Trello and Google Drive for most things, everything from my personal life, to hobbies, to side projects, and work items. I love Trello but sometimes I want something a little bit more. I think I'll to duplicate things I'm working on for a few weeks or so in here to see how I like it. Maybe I'll replace Trello or maybe there are some integrations out there already to sync somehow, or maybe If I'm bored and have time on my hands I'll try writing something myself.
The app looks great but hopefully they add Kanban support for iPhone soon.
Neat! I was looking into tracing solutions for our k8s cluster the other day and was going to look into setting up Zipkin. Now I'll this to my list of tools to evaluate. I found this blog post by uber informative https://eng.uber.com/distributed-tracing/ so maybe there is no need to even setting up Zipkin and just start with Jaegar?
Most folks will choose either Zipkin or Jaeger, but both are OpenTracing-compatible distributed tracing systems. You might find the Cloud Native Landscape useful for thinking about the options: https://github.com/cncf/landscape/blob/master/README.md
Disclosure: I’m the executive director of CNCF, which just adopted Jaeger 2 weeks ago, and I’m an author of the landscape.
Last I checked "OpenTracing-compatible" only went as far as using common terminology. Tbh I was a bit disappointed by this; has more been defined since? E.g. are there now shared schemas, APIs of sorts?
It's weird for most people. We're used to cross-language wire protocols. OpenTracing is different.
An analogy is SLF4J for Java logging. All libraries, etc use the same interface and the final user determines the backend: java.util, Logback. This makes sense if you have many authors of libraries with a cross-cutting concern.
This really makes OpenTracing half a dozen different standards, one per language, with common semantics.
"OpenTracing-compatible" is strict API compatibility in any supported language. The cross-language spec is "terminology-based" since it's, well, cross-language.
As an OpenTracing contributor, the core value prop still seems quite strong in that instrumentation of OSS dependencies is a massive pain point and should not be tracing-system-specific since it doesn't need to be. There is also value in common protocols and formats, and in that spirit there is interest in broadening scope to include those... though from seeing many companies adopt tracing tech, I haven't observed protocol compatibility as the main pain point or blocker.
How do you plan on keeping it sane over time? Even disregarding paring down the number of times managed major providers appear on the list (which is super sensible imo), won't it start to get quite crowded with all the open source competitors appearing?
The CNCF storage WG is also looking at creating a "zoomed in" version of the storage section with higher fidelity information. That's one model of providing more detail.
We also have an interactive version of the landscape coming that will provide filtering, zooming, etc.
Last week I did a test of Linkerd with Zipkin for k8s clusters. Works like a charm, buy still a bit more work to use Jaeger as Zipkin replacement, as they do not support the same protocols yet. I believe https://github.com/linkerd/linkerd-zipkin will fix that but haven't tested yet.
I see Zipkin is a Java app, without sounding like I’m hating on a language for no reason here - but I wonder if it’s awfully heavy and slow to launch like so most other java apps? By comparison I’d expect a tracer written in Go would be significantly more efficient.
Does slow startup time matter for services that are supposed to be running continuously in a cluster environment?
I have no doubt that a Go tracer would start orders of magnitudes faster than a Java one (especially if it pulls in spring or other web-related dependencies for the zipkin UI) but I think it is irrelevant.
it's irrelevant. if you take a look at the diagrams in the blog post that include zipkin, it's is basically only the query/frontend portion - the tracing itself is done natively in the language the code is written in, and outputted to cassandra. The zipkin part is a long running server that just needs to query cassandra.
