Last year I bought a 4bay WTR PRO NAS with an N100. It idles at 13W, after some tuning (mostly putting drives to sleep after ~10min of inactivity). I briefly looked into TrueNAS/unraid, but I ended up installing plain Debian, with ZFS, pCloud for remote backups and running everything on plain docker (in my case samba, HASS, jellyfin, kodi, rutorrent and some custom apps of my own). All in all it took me about 8 hours to setup, and 0 issues since. 100% satisfied with my setup.
What you are describing sounds precisely like your brain trying to do some emotional processing and you are shutting it down because you think it's not useful. If you are looking for the productive spin, then I would suggest trying some metathinking. Try to discover why your brain decides to bring this up to your attention. The specific story might seem banal, but uncovering the underlying pattern will teach you things about yourself that you might not be aware of yet, like what you are afraid in life.
I was wondering about that too. Compared to my peers I consider myself having a below average short term memory (not really good at raw computation power), but in contrast, I am pretty good at abstract thinking, e.g. I can easily visualize the end2end flow of a system, identify all the pain points and produce very good designs (in terms of simplicity). So perhaps this "working context" is about knowledge, pattern recognition, analytical thinking, ...
you are assuming hidden costs, I am assuming hidden incentives. It’s not that they are stupid or incompetent, but bad incentives within the org can and do produce stupid outcomes.
I think I've listen to asianometry (YT channel) talk about this too, but I am unable to find any clip now where he explicitly talks about interference lithography...
masks dont have the actual shape, but shapes accounting for wave interference patterns that will end up producing the final shape when EUV light passes through. I believe the process of comming up with the correct intereference pattern takes weeks of supercomputing.
I’ve always thought it might be PHP legacy of returning 200 even on critical errors. AFAIK Slack and FB APIs work like that, and they are, or have been, PHP based…
Building on the web form example given by the author, there is a lot of extra that one could do: Improve the design, improve user experience, improve performance, format/cleanup the code, add some extra features, add flags to enable alternative behaviour ...
OP is talking about concurrent execution of the task without serialization on the database (serializable isolation is almost never the default). Which results in 2 concurrent queries getting the same list of customers to charge.
when you say parallel you mean the work is distributed across multiple cores? e.g. multiple python worker processes. Or is all work running single threaded in a single process (concurrent IO, but not true parallelism)?
When I add autoreload functionality to my programs I just spawn a thread that checks for last modified date and then re-executes the program with os.execlp(sys.argv[0], *sys.argv)
I found my solution superior in several ways:
- I can force an autoreload just by saving a file (no file changes needed to force an md5 diff)
- exec() doesn't suffer from the side effects of not restarting the python interpreter, clean start every time :)
- it is also quite portable and doesn't require extra dependencies like inotify/fswatch/etc.
</ul>
> Consider the incubation time of 5 days avg, 14 days max during which you're already infectious."
I have seen several comments like this on this thread suggesting people are contagious during the incubation phase. Do you have a source for this? AFAIK this has not yet been confirmed, other than perhaps a few anecdotal cases.
A common solution is to wrap all code within a function. This way nothing gets executed until the last line, the one that calls the function, is executed.
I wouldn’t categorize this as technical debt unless you’ve deriberatly choosen to implement the wrong abstraction first, to get the product out the door earlier, or some other short term benefit. Technical debt is a deliberate action with some upfront knowledge of its consequences.