Full disclosure: I’m pretty far along in the process of exploring opportunities and already have some offers on the table. I’m still open to considering more opportunities for the time being.
Remote: Yes, and I have extensive experience working remotely.
Willing to relocate: Yes
Technologies: Senior full stack engineer and technical leader currently enjoying working with Go (Golang), Ruby on Rails, React, Next.js, and Kubernetes.
Most of the guidance is very outdated. It's likely to confuse more than clarify unless you've taken the time to study modern resources. I prefer Bryan Garner's work, like his usage guides.
Sure, coffee roaster here. It's false that allowing beans to degas c02 preserves them indefinitely as the parent comment seems to imply. There is however about a 10-hour window after roasting where degassing of c02 is so vigorous it impedes oxidation. Freezing vacuum sealed coffee, both green and roasted beans, will preserve it almost perfectly for years because freezing decreases oxidation rates by more than 90% and slows the movement of volatiles.[0] Enough people have documented and tested this and it's very common for Cup of Excellence winning and other notable coffees to be stored for extended periods of time this way. There are even cafes with reserves of such coffee, you can walk in and they'll pull winners from years ago for you to try. Scott Rao documents the research and resulting evidence of why it's beneficial to freeze coffee in his book The Coffee Roaster's Companion.[1] It's just not economical at scale, or necessary. Green coffee is "fresh" for about 9 months on average, most roasters go through specific lots of coffee well before that window closes. The sad reality is that most roasted coffee is well past its peak by the time it reaches the consumer.
You can conduct an at-home experiment yourself by finding a local roaster, asking when their roast days are and if you can get some coffee from that batch before it's allowed to rest. Seal and freeze a portion while keeping the rest in a normal valve-release bag and compare after a week or two.
I built https://www.stackpair.com because I was over reading job listings to get an idea of what I'd be working with. It puts as much info as possible up front about the languages, stack, and tools used in the position. The search makes finding relevant positions easy, the query "go remote sf" returns what you'd expect, for instance. I also do a lot to feature quality opportunities, which traditional job boards can struggle with.
Remote: Yes, and I have extensive experience working remotely.
Willing to relocate: Yes
Technologies: Go, Redis, PostgreSQL, Kubernetes, Docker, and Linux.
Résumé/CV: https://www.lukeheuer.com/resume/a1g
Email: [email protected]
Full disclosure: I’m pretty far along in the process of exploring opportunities and already have some offers on the table. I’m still open to considering more opportunities for the time being.