knoam

Methodists

I maintain a microservice we'll call the FooProcessor. As part of it doing its thing, it calls what we'll call the FooSubProcessor which handles a specific case of a specific step of foo processing. To do its thing, the FooSubProcessor needs a bar value for every foo it subprocesses. We don't use the bar value, so we have to first fetch it from the BarService. But that service needs a baz value that again we don't have and need to fetch from another service.

What are some rules to determine which service should be responsible for fetching each of these values? Are there certain patterns that would help? Is it generally better to push these responsibilities downstream or upst

My credit card was about to expire so Mint sent me an email to update it. I did so, but the next screen the app (Android) took me to after doing that was to buy a whole new year of service, even though I just renewed at the end of March.

There was a back button on that screen, and that worked fine. It didn't lose my updated payment details.

I could have easily made the mistake of paying for a whole extra year of service.

I think this a bug in the app. It shouldn't have sent me to the payment screen since I came in via the screen to edit a payment method, not make a payment.

As you probably know, checkinstall creates a native linux package, like .deb or .rpm, for your typical ./configure && make && make install compile from source installation. The value of this is that you can see that the package is installed alongside your regular packages installed via pacman, yay, etc. And you can uninstall it the same way you would for those typical packages.

It would be nice to have something similar for packages that only provide installation via npm -g install or pip install. And we could do better than checkinstall since what I'm proposing could also do automatic updates. In fact we could specify say a major version or a minor version and

Most web pages these days are responsive, so things move around as you resize the window. This can help you get exactly what you want in the screenshot without distracting extra stuff. Then you can use the "screenshot window" feature and you don't have to add an ugly highlight to point out the important content.

Plus they'll be easier to view on mobile the more you shrink down the window.

Or if you share the screenshot in a chat app, a smaller screenshot can mean the viewer doesn't have to click the image to zoom.

Also

• Drag the tab out to a separate window so you don't have your other tabs in the shot.

• Hide your bookmark bar with ctrl-shift-b

The other day I actually went so far