Was it so bad? My experience with it was resoundingly positive, and saw lots of productivity gains with a great developer experience for teams that could build apps with strong guard rails in place.
Now everyone and the kitchen sink „needs“ their own kubernetes cluster and operations teams struggle to build complex landing zones for the underlying cloud infrastructure so teams don’t shoot their own foot off all too easily…
For context: I was at a company that was trying to roll out OpenStack internally (don't do this). Lots of stuff got thrown at the wall in an attempt to find a unified provisioner, nearly all of it terrible. Thankfully my role was that of a consumer.
My recollections were that BOSH and CF exposed a ton more complexity than I wanted, and I don't remember there being a great story for deploying Rails apps. But all of these abstraction layers are just like cross-platform GUI toolkits – you're never going to approach the native look and feel or integration. And I don't like the terminology(!) it's all relatively unintuitive to me (e.g. stem cells, deployments, releases).
For contrast the Hashicorp stack for our AWS environments (tf+packer+vault) generally felt much more pleasant to deal with, and that's where the comparison to GUI toolkits falls apart I suppose.
But… look at all the integrations and enterprisey features that CF+BOSH offer. That's way more of the sort of thing that I'd expect to fit in at Salesforce.
meshcloud GmbH | Various Engineering Positions | Frankfurt, Germany | Remote work within Germany, after the Onboarding World Office | Fulltime and Permanent
Our cloud foundation platform provides control and visibility that empowers an efficient and secure multi-cloud adoption for our customers such as Volkswagen or Commerzbank. To get a tiny insight about our work: We recently launched an open-source CLI tool that provides an easy overview of multi-cloud landscapes https://github.com/meshcloud/collie-cli
Feel free to take a look at our website to learn more about our benefits: https://jobs.meshcloud.io Among other things, we offer World Office (mobile working all over the world), but most importantly a working atmosphere that allows you to do your job with passion.
If you are interested in hearing more please choose a free slot in the calendar of our HR-Manager Joanna https://app.harmonizely.com/jbauer our reach out via mail to jobs@meshcloud.io
Is this a US specific problem? In Germany companies need to maintain cap tables in a mandatory public registry (Handelsregister). You can request any company’s records against a small fee (which in fairness I consider very backwards, could be more open). There are some third party providers like NorthData making this data available publicly as well.
I am one of the organizers of this Coalition. for the first version of our open format we're focused on American Delaware Corp C's - most common entity that VCs invest into.
we announced a number of new Coalition members yesterday who also would like to see this sort of standardization outside of the US. we're focused on the US atm
Just a shoutout that vuepress 2 (or is it called vuepress-next?) can also bundle via vite. I haven't compared it to vitepress, but its reloads from markdown are also really snappy.
> Espresso machines, then and now, are gigantic, expensive, difficult to use, and incredibly inefficient from an energy perspective.
Interestingly that's not my experience with Moka Coffe Pots. The 2-pot Bialetti I have takes a long while to heat and is almost always too small for the heat source I have available. Electric stove fields are too wide, and camping gas heaters seem to wrap the flames more around the pot than boiling it properly. After the water is steaming, you also need to sustain the heat for a bit to let the steam travel through. In total, it feels like a lot of wasted heat energy for a little bit of coffee.
I have a Flare Espresso machine (piston, manually operated) that just requires boiling water that I can get from a more efficient source like a pot matching the stove, a water boiler or even a good thermos (!) when travelling ;-) And the result I get out of that is a "proper" espresso because you can easily hit 10 bars of pressure, by applying gentle pressure on the lever.
> The 2-pot Bialetti I have takes a long while to heat
Do you put cold water in the bottom thingy and heat it up on the stove? When I started using moka pots, I read that you should put pre-boiled hot water in there and then put it on medium to low heat on the stove. Even with that I still find it a bit too quick sometimes.
So I've gone through a bit of journey doing docs for a product company. I feel that for a product company it's really important to own your documentation and the publishing workflow as it's a key part of your product.
GitBooks was my first stab. I liked git and markdown, however I disliked all the places where "proprietary" formatting/features crept in and once it got more closed/commercial wrt. publishing/theming pipeline we went out.
We then adopted docusaurus v1 for our product documentation. It's a great tool, but never really built custom components for it because we're not a react shop. We did integrate some nice tools to work with our markdown tool (e.g. markdown-lint, custom code snippet injectors etc). One downside of docusaurus is how much friction there is to create a new page. You have to create a markdown file, insert frontmatter, add it to sidebars.json, reload the dev server, then insert your content.
When docusaurus announced v2, we considered adopting it. Instead, we started looking into VuePress vNext. What I love about it is that its configuration is TypeScript (vs. JSON). This allows us to generate things like navbars, sidebars from code instead of manually wrangling JSON. It uses Vite for bundling and the local editing experience is therefore much faster.
As you write more and more docs, markdown editing experience becomes important. VSCode + the right plugins can get you far, but we found they all did not feel "fluent" to the point where our team _loves_ writing documentation. People often complained that our company wiki (Notion) feels much nicer, so we built a tool that allows us to use Notion as a "CMS" for our documentation: https://github.com/meshcloud/notion-markdown-cms
It's really handy because that way we get perks like organizing content with databases, link pages using @mention syntax, drag & drop for screenshots etc.
Publishing on netlify rounds it off.
Thanks for the context. Which docs system one chooses is really dependent on that person's specific goals / product so it's helpful to see your detailed thinking here.
There are quite a few options for markdown + git knowledge bases, eg. Obsidian. You can easily find more alternatives discussed here on HN by starting a search on Obsidian.
If you’re looking for more of a CMS there’s quite a few options out there, most notably static site generators like docusaurus or vuepress. Plug: I’ve built a small tool to generate the markdown from notion, which allows me to use notion as my CMS editor while keeping the generated site fully under my control. https://github.com/meshcloud/notion-markdown-cms
Now everyone and the kitchen sink „needs“ their own kubernetes cluster and operations teams struggle to build complex landing zones for the underlying cloud infrastructure so teams don’t shoot their own foot off all too easily…