The Startup (Medium)

It all depends on the nature of your application. A video editor and a command line utility are so different!

Sounds like you already know the big players so I won't repeat them. Instead, here are some off-kilter ideas:

1. Casual use, general interest, notification-requiring, simple single-file data requirements, tolerant of desktop / mobile split sessions? Try making a chat bot for Telegram, FB, Discord, Slack..

2. Dynamic, visualization-focused UI with simple options that need to be tweaked interactively? Try Imgui[0] or Godot[1]

3. Scientific or data-centric stuff pulling in data from here and there, but meant for interactive exploration? Try Wolfram / Mathematica or an IPython notebook / GoogleColab

[0] https://github.com/ocornut/imgui/wiki/Software-using-dear-imgui

[1] https://medium.com/swlh/what-makes-godot-engine-great-for-advance-gui-applications-b1cfb941df3b

Hmm. By tooling are you referring to things like jq and other "uncommon" cli/tui apps I use to work against a code base locally? I think that's what you mean.

One of the best practices when using docker-compose to develop is actually to mount your code base as a volume. This lets you modify the code locally without requiring a complete rebuild of the container each time code is modified.

You might have to no-hup a service or run it not as pid1 (init container or supervisord) so it can restart without killing the container but that depends on the work being done.

I'm trying to find a good example to show you but I'm not finding much. If you have a medium account this might be decent, I don't have one but it starts off going through the process https://medium.com/swlh/tutorial-how-to-use-docker-volumes-to-code-faster-245f15a60534

Thank you both! A Friend Link without Paywall :) https://medium.com/swlh/why-you-shouldnt-use-offset-and-limit-for-your-pagination-4440e421ba87?source=friends_link&sk=2dafef5c1fb698e2f7884bf5e8149b37 Let me know if you have any suggestions on it, would love to know about them!

One of the things I've learned is literally don't "impose" anything to your readers. What I've written is mainly cited by big sources (and I have included the sources in the article!), but people rather prefer to point the finger if they do not agree with you.

I believe the article title is a bit "imposing" on the reader, but so do are all the other "click-baity" titles we see everywhere, and in this case I am able to prove my point of view, being it through an explanation or a PoC that I do provide as well. But people are mean :)

This blogpost by a self-taught engineer at Uber gives a framework for deciding what to blog about that I really resonate with.
"As a rule of thumb, any topic that passes any of the following litmus tests is a good candidate for a blog post or conference talk:
1. The most senior engineer you know would find the information and subject matter compelling.
2. People who read the post think: “Wow, I can’t believe they managed to <something really hard or difficult to figure out>. I really wish we had someone like that who could help us with <thorny problem>”.
3. The subject matter is deep in a way that readers are unlikely to be able to obtain the same information anywhere else."
https://medium.com/swlh/from-coding-bootcamp-graduate-to-building-distributed-databases-29acbb723d8

There's not much about it online. They do mention it in the docs, they call this "prefix compression" [0], so you can search for that. This article describes it [1], although it is somewhat high level.

They only use this for indexes. It works really well for internal mongo ids (they all start with timestamps if I remember correctly). It also works well for compound indexes. Pro tip: for compound indexes always go from low-cardinality attribute to high-cardinality attribute to get the best results from prefix compression (it's also good for speed of queries).

[0] https://www.mongodb.com/docs/manual/reference/glossary/#std-term-prefix-compression

[1] https://medium.com/swlh/mongodb-indexes-deep-dive-understanding-indexes-9bcec6ed7aa6

One unusual alternative you may not have thought about is using Godot Game Engine. Before dismissing it, consider this: Godot engine is shockingly small for what it does. The download is about 30-40 MB. The GUI designer tool is second to none, and you can make highly interactive advanced GUIs using a language that looks very much like Python called GDScript. It is very quick to learn.

It does make GUI which are native to the platform but you get a small native binary which renders OpenGL.

Is Making Advanced GUI Applications with Godot the Future? https://medium.com/swlh/what-makes-godot-engine-great-for-advance-gui-applications-b1cfb941df3b