git filter-branch –tree-filter ‘rm -rf largeFile’ HEAD
Full Screen your chrome, then leverage ont this plugin for URL boxEnjoying Chrome in Completely Full Screen mode even without omnibox (Zen). Leave the address typing to ZenHelper. Keyboard Shortcut: windows: Ctrl+Shift+L mac: Cmd+Shift+L Note: This is still beta stage, new feature WIP.
multipliers = 
for i in range(5):
return i * x
for multiplier in create_multipliers():
return [lambda x : i * x for i in range(5)]
for multiplier in create_multipliers_lambda():
return [lambda x, i=i : i * x for i in range(5)]
for multiplier in create_multipliers_fix():
it’s not a completely novel requirement to get the status for asynchronous processing, for example, to get the file upload progress, to get the order status, alert for processing failures etc.
IMO, there are mostly two approaches for it,
whether it’s through REST/GraphQL/Queue/DB/FS, if the client is polling for status, that’s a synchronous call, which kind of patched for the original fire and forget async process.
this would still be a patch for the original async process, however, it’s really valid. since it’s a “new” requirement from the client to get the status. instead of polling, which almost removed the merits of the original async call, the client could expose a webhook for the server to post back status asynchronously. as such, even though it’s a patch, it will be patched async, leave both processes fire and forget.
recently i have a need to build/start/stop some sibling containers (vs docker within docker), the way to do it is to expose a pipelien from the host to the container:
for single container:
docker run -v /var/run/docker.sock:/var/run/docker.sock
for docker compose
actually the dameon could listen from other host (configuration):
have encountered some issue with the stale dockerfile. turns out, docker compose actually cache previous builds (this is not stated in the doc).
so to keep it updated, need to run build without cache then bring it up.
docker-compose build --no-cache && docker-compose up
history is full of similarity.
this is such a repeat of WSDL2Java vs Java2WSDL debate. personally, it’s nothing black or white, right or wrong, similar to the ORM vs mybatis, it’s just opposite design suitable for individual use cases.