Megadosing B6 can lead to B6 toxicity/syndrome as a result of its longer half life and ability to accumulate in the system. Between multivitamins, energy drinks, preworkouts and food, it's very easy to go well above the recommended amount. I'm currently recovering from B6 induced peripheral neuropathy (tingling in my feet) caused by 20-50mg/day over several years.
As long as you stick to pure ActiveJob features it really shouldn't be too difficult to scale from in memory based queue to PostgresSQL backed Good Job and then to Redis backed Sidekiq if and only if you need to.
Yes, I wanted a PG-based one and reached for Good Job on a new project since it was recently created and with Active Job in mind from the start. Check out the intro:
> If a Sidekiq process crashes while processing a job, that job is lost. [0]
We use Sidekiq Pro at work but I find it unfortunate that reliability is a pro feature. It's really hard to tell a product owner: Yeah, we might lose a few jobs once in a while.
I just looked this up. It's $995/year, or approximately 4% of the fully loaded cost of an FTE software engineer at most companies. i.e. about 3 weeks of a developer's time.
Back around 2000, I was writing software patches for a large telecom company. These patches had to be applied to live, inservice telephone switches and equipment that were powering public phone services - restarts and downtimes were not an option. Needless to say, careful consideration had to be given with regard to how a patch was developed and applied.
I don't recall the specifics, but one fateful patch had a very large compound boolean expression that included an invalid condition. For whatever reason, that expression didn't or couldn't receive 100% test coverage.
When applied, this patch took down the entire phone service (including emergency 911) for the island of Newfoundland Canada and all its residents (maybe 300-500k people).
The immediate fix was simply a new patch that reverted the bad patch. Unfortunately, it took several hours from the point we learned of the issue to writing, delivering and applying the fix.
I've heard that Newfoundlanders have a reputation for being very friendly, so I like to believe that all has been forgiven and forgotten and that I may one day visit the island in peace.
I discovered PostgreSQL in a similar happenstance sort of way - working at a large telecom directly out of college in the late 90s, tasked with setting up a MySQL backed webapp to manage some internal processes. Fortunately, I was unable to compile MySQL on our HPUX workstations (issue with threads IIRC), PostgreSQL to the rescue. Been using it ever since.
We're currently using Crystal 0.25.1 with the Kemal web framework to provide an online paycheck calculator for US based employees (it's basically a demo/tool for our SaaS based accounting, payroll and fund raising app).
Really impressed with the language so far and hope to expand its use within our organization.
We use FreeBSD in production (SaaS accounting/payroll app) as a load balancing proxy/web server (Nginx) and outgoing mail server (OpenSMTPD) because it's a stable, proven OS with sane defaults. Thanks to OpenBSD, we get an awesome firewall (PF) and dead simple OpenSMTPD mail server (total config is around 25 lines which gives us DKIM signing and PKI with no additional software).
At home, FreeBSD is used as a HTPC (Kodi), file server and backup box (it acts like a Time Machine for our Macs via netatalk and for Linux we use rsnapshot over NFS).
These do a good job of providing VIM mode, but I just learned about the file/project pane vim mode. Will try that out latter.
You will have to do some config changes if you want the commands from other plugins to feel more natural in vim-mode.
---
Sidenote: I love vim, and use Atom for certain types of projects, but the vim-mode in Atom just never felt right, so I don't use it any more. Now that I know about some of the other neat things it can do, plus the ex-mode support, I might go back to using it again. The second I start using vim mode, I naturally start thinking I am in vim itself, and commands like `:wq` are muscle memory. Hate it when there is a commit message with `:wq` at the end, or I run the program and a crash occurs because of a rogue `:wq`.
A derivative of Unicorn named Pitchfork is also in the works from Shopify - https://github.com/Shopify/pitchfork