Static analyzers like https://github.com/zizmorcore/zizmor can help find such misconfiguration. It is however unfortunate, that such footguns aren't harder to fire.
Making it solely about the extraction of dollars is a great recipe to make something mediocre. See Hollywood or Microslop.
Its like min-maxing a Diablo build where you want the quality of the product to be _just_ above the "acceptable" threshold but no higher because that's wasting money. Then, you're free to use all remaining points to spec into revenue.
Exactly. In addition, sometimes a good software "only" makes you save 1% of your time, but that 1% was a terrible burden that induced mental fatigue, made you take bad decisions, etc. It can even make a great Engineer stay when he would have left with the previous version.
While reading the article I was thinking the same thing. I can think of problems I've solved that directly affected 0% of our customers, but overloaded our customer support team.
High number of days with commits, merging and shipping code consistently (some people/project will ship multiple times a day/week, some projects move a little slower).
That plus the completion of high impact projects makes good strong engineers.
I think its cool that more people are building what I call "calm tech". More technology should try to serve a purpose quickly and then get out of the way instead of trying to artificially stay on your screen as long as possible.
nice! yeah, i agree. calm tech is a nice way to put it. the current big platforms are highly tuned to keep people engaged and enraged to the max, rss is kind antithesis of that. that's probably why big companies try to bury and hide it. youtube and reddit still give pretty good rss support though, which is nice.
I habe a "Pocketbook Verse Pro" that runs Linux. No need to root, you can copy ARM executables to the SD card and run them (that's how I use Syncthing on it). KOReader also works on it.
I built my own reader because I didn't want unread items to accumulate. It just shows what was published the last X days.
The result is that there is no need for persistent storage, so its real easy to host. If you're interested, its here: https://github.com/lukasknuth/briefly
My specific need for RSS is the accumulation. There are people who post once a week and I don't want to miss the posts because I was offline at the time.
We look at K8s more like "the Cloud Operating System". Many of its capabilities are more valuable for other runtimes, but that doesn't mean that Elixir is a bad fit with it.
For example, the Erlang VM clustering can make use of K8s for Service Discovery. You can do ephemeral containers and use readiness probes to create a " hand over" period where new instances can sync their data from old, about-to-be-replaced instances.
reply