The conflict of interest should be disclaimed in the very first sentence of the post.
- if only one process can write to the db, how do you architect your system so that writes are performed by just one of the instances (the writer) - how do you gracefully upgrade your app without any downtime?
Sometimes an unexpected snack makes its way into my belly, leaving behind an annoying dirty plate that needs some cleaning.
Thanks for trying though
Hello HN. A long time ago I found a link to a short scifi story that made it to the homepage of HN, but I lost the link. I really liked it and want to re-read; this is the plot of the story:> Humans discovered through space observation that they are actually a simulation inside some other civilization. The catch is that because we run on their computers, our time goes way faster than theirs....
Lately I have been migrating all my self-hosted stuff into a raspberry pi (instead of running a public instance in the cloud). It gives me a bit of piece of mind knowing that it adds an extra layer of security (to hit any of my endpoints/apps you would need to infiltrate my VPN). And it will save me a lot of money on hosting.
I don't need to expose my computers publicly or enable upnp or anything. It just works.
The bot names and places the file in the right folder for paperless to ingest.
If you want to build anything mildly interesting, you need to have a solid background on software engineering (building data pipelines in Spark, Flink, etc. goes way beyond knowing SQL), you need to really understand your runtime (e.g. the JVM, and how to tune it when working with massive amounts of data), you need a bit of knowledge about infrastructure, because some of the most specialized and powerful tools do not have yet an established "way of doing things", and the statefulness nature of them make them different from your typical web app deployment.
Maybe if you want to become a data analyst you only need SQL, and I would still doubt it. But data engineering is a bit different.
I mean, I floss at least twice or more a day. Like I don't understand how someone could be more than a day without flossing and not feel something is not right in their mouth.
https://github.com/casidiablo/macondo
I don't even know what it is I built, but it has been useful in some contexts.
It basically allows you to easily wrap and distribute scripts (or more complex apps) that have specific dependencies that might not always be installed in the host. It does so by wrapping the script in a docker image.
It also automates the annoying part of docker: mounting local paths for apps that need to interact with the host's file system.
I need to write a blog post on this if anything to gather feedback. I'm still not 100% sold on the idea and there are some edge cases. Still, a fun experiment.
The experience is for the most part pleasing, and I'm sure you will find a lot claims supporting that, so I'll focus on the things that I don't like:
* people tend to abuse some of the features (like extension functions), which sometimes does more harm in terms of readability
* Kotlin offers means to do quasi-functional programming, and people tend to write horrible one liners just for the sake of it.
* most tooling seems stuck in Java 8. So you are stuck in that ecosystem (you can, though, compile with Java 8 and run in java 11 of course).
* for mid-sized applications where it makes sense to use DI, using kapt is sometimes a pain (it's better this days, but still I hate the thing)
* even though the jetbrains support is first class, it is still considerably slower then pure Java code. * very personal: I've come to miss Java's verboseness.
* some tools don't integrate well with it (yet)... So do not expect things like static analyzers to be good or even existent.
Another option is to just detect when I'm not speaking, or typing.
It also forces me to think out loud which I found it useful because it helps me improve the way I would communicate my thought process to someone else.