As the other commenter said, pretty sure it's at the routing layer. Deploys, start ups, all working just fine for our apps. But router can't reach them. Related to the Google CA outage maybe?
Carats & Cake delivers the operating system for events, transforming the $100 billion annual events industry through a full suite of purpose-built marketing and sales tools as well as customer conversion solutions (contracting, invoicing, and payments).
We are looking for someone who is excited about being part of a small team with other experienced engineers and playing a key role in executing against our product roadmap.
Our stack is Ruby on Rails, Postgres, React w/ Typescript, and we use Sidekiq for background processing.
Carats & Cake delivers the operating system for events, transforming the $100 billion annual events industry through a full suite of purpose-built marketing and sales tools as well as customer conversion solutions (contracting, invoicing, and payments).
We are looking for someone who is excited about being part of a small team with other experienced engineers and playing a key role in executing against our product roadmap.
Our stack is Ruby on Rails, Postgres, React w/ Typescript, and we use Sidekiq for background processing.
#3 is one of my favorite things about Sidekiq. Anything I'm trying to do with Sidekiq, I check the wiki first, and it's usually there. Any time I've introduced the library to a team, the docs and wiki are always my recommendation for answering questions. Even Pro/Ent features are covered there, which is so much nicer than having the docs hidden behind a login/paywall.
Thanks for the hard work you've poured into them Mike!
Full Stack Engineer with over 7+ years experience, with 6 of them being remote. I've spent the past 5 years in Ed-Tech, and am looking for my next opportunity.
There was a lot of research that was done, but we were able to get into cans with a few key components.
We use a piece of home brewing equipment right now to fill our cans and bottles, the beer gun [1]. The beer gun allows us to purge our cans/bottles with CO2 (oxygen is bad for alcohol), and then fill them from the bottom to reduce foam.
I was able to find a local supplier, that wraps cans in plastic. So rather than printing them, they shrink wrap our label on to them. They're a bit more expensive than printed cans (if I recall 34¢ sleeved vs 19¢ printed). This allows us to order a single pallet at a time, decreasing our storage needs
The last key was the can seamer[2]. I found this early on, and it's been a great little work horse for us. We've put over 6,000 cans through it, and it's been one of the best purchases we've made.
Bottles are the easy one, we just use the beer gun [1] and then a manual capper to seal them.
Happy to answer any other questions! It's been a fun ride trying to figure out how to "mass produce" something on a smaller scale :)
I licensed my house as a winery, and run a hard cider company with my girlfriend. We sell to some stores in our area, and do our local Farmer's Market during the summer.
It's been very satisfying making and selling a physical product.
The profitability part isn't quite there yet. But we're working on that.
We (the beverage industry/my company) are only in practice responsible for deposits. While we are required to take collections, no consumers really returns them to us. The return burden often falls on the retailers, who collect deposit directly from consumers.
When we sell product to a retail store. We collect a 10¢ deposit per can from them. The retailer then collects a 10¢ deposit from the customer.
My company gives all our collected deposits to a co-op (which is state run I believe) who handle the collection/recycling of the containers.
I interact with our bottle bill on a pretty small scale, but I believe that only changes my reporting frequency.
I feel like this is a big missing piece for voice activated things. I've got an Echo device ~10ft from my TV, and it gets activated from Netflix (Parks & Rec mostly... I blame Rob Lowe) all the time. I should be able to go into the app and label it as a false activation so it can ignore it in the future