What is inside a K-Cup

The kid asked what was inside the K-Cup (the coffee unit for the single serve coffee brew system). We shook and cut and concluded there are two basic kinds.

  1. Classic – “teabag of coffee”
  2. Fully dissolvable contents – like hot chocolate and “Chai Latte”

The classic kind is described by Wikipedia, and you can discern the design by simply shaking and examining an unused K-Cup.  To complete the investigation, I cut a used classic K-Cup open.  The embedded filter holding the coffee (like a teabag) is quite apparent.

During brewing, the hot water is injected at the top (through the foil seal – here on the bottom because the K-Cup is upside-down) .  The brewed coffee drains out the bottom, here visible on the left half of the opened shell.

Image

SAP Archived PocketBuilder

I was poking around the Appeon and SAP sites and such when I fell across a link to our beloved PocketBuilder.  It has not been totally scrubbed but moved to an ‘archived’ location:
http://www.sybase.com/products/archivedproducts/pocketbuilder

So, if you’re wanting win bar bets by pointing out the “already invented by PocketBuilder” ideas, just reference this area.  Things like:

  • Occasionally connected, transactional, data access objects using MobiLink (2003).
    On top of the rock solid ACID SQL within the device itself.
  • Easy access to web services from the mobile device (2004).
  • 4GL objects for barcode & fingerprint readers (2004).
    This included support for multiple hardware variations.
  • Referring to the user’s source code library as the ‘pickle’ (in homage to a PowerBuilder shorthand).
  • 4GL objects for tying the contact list to the device’s phone for easy calling and lookups (2003)
  • 4GL objects for GPS, SMS, Camera, and SIM card (2005).
    And yes, these support multiple hardware variations.
  • The PocketBuilder group also ‘snuck’ features into PowerBuilder – like enhancements to direct file access, edit masks, and display formats (hex, boolean, etc).

Internally this project was run using agile techniques such as nightly builds, nightly QA runs, burn-down lists, and frequent internal and external releases.  This was a small project that made a profit, but not large enough for a big company to bother with (IOW – if this was a company in my garage, we would be very very happy).