Also working on building a community site with Telescope on Heroku.
Starting to learn React. As a non-application developer, I'm looking to use this along with Ampersand to create an easy way to create static websites with it. I know, I know, this is not what its meant for, but I like to think outside the box sometimes with these frameworks."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: What project are you currently working on?"}},"_tags":["comment","author_at-fates-hands","story_9891487"],"author":"at-fates-hands","children":[9895126],"comment_text":"I'm working on several site redesigns so putting my design hat back on after being neck deep in JS is always refreshing.
Also working on building a community site with Telescope on Heroku.
Starting to learn React. As a non-application developer, I'm looking to use this along with Ampersand to create an easy way to create static websites with it. I know, I know, this is not what its meant for, but I like to think outside the box sometimes with these frameworks.","created_at":"2015-07-15T16:26:45Z","created_at_i":1436977605,"objectID":"9892247","parent_id":9891487,"points":null,"story_id":9891487,"story_title":"Ask HN: What project are you currently working on?","updated_at":"2023-09-07T03:12:53Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"amk_"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"I found this tutorial series to be pretty good, demoing React with Ampersand as the model/controller: http://learn.humanjavascript.com/react-ampersand/introductio...
There's also a library to hook up React views directly to a Firebase (real-time JSON streaming) backend: https://www.firebase.com/blog/2014-05-01-using-firebase-with..."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"React.js Introduction for People Who Know Just Enough JQuery"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"http://reactfordesigners.com/labs/reactjs-introduction-for-people-who-know-just-enough-jquery-to-get-by/"}},"_tags":["comment","author_amk_","story_9856855"],"author":"amk_","comment_text":"I found this tutorial series to be pretty good, demoing React with Ampersand as the model/controller: http://learn.humanjavascript.com/react-ampersand/introductio...
There's also a library to hook up React views directly to a Firebase (real-time JSON streaming) backend: https://www.firebase.com/blog/2014-05-01-using-firebase-with...","created_at":"2015-07-09T14:42:35Z","created_at_i":1436452955,"objectID":"9858080","parent_id":9857469,"story_id":9856855,"story_title":"React.js Introduction for People Who Know Just Enough JQuery","story_url":"http://reactfordesigners.com/labs/reactjs-introduction-for-people-who-know-just-enough-jquery-to-get-by/","updated_at":"2024-09-19T22:01:30Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jlongster"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"I'm not familiar with ampersand-collection, so I don't exactly understand your questions, but I think you're also farther along than I am researching this. I can't give a good answer yet as I'm just starting to play around with integrating mori.
I don't know what you mean by "derived attributes", or why it would be difficult to do data transformations on the models that deal with mori data structures. It'd be great to discuss this somewhere, maybe on #reactjs IRC? I'm jlongster there."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Virtual DOM in Elm"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"http://elm-lang.org/blog/Blazing-Fast-Html.elm"}},"_tags":["comment","author_jlongster","story_8063870"],"author":"jlongster","comment_text":"I'm not familiar with ampersand-collection, so I don't exactly understand your questions, but I think you're also farther along than I am researching this. I can't give a good answer yet as I'm just starting to play around with integrating mori.
I don't know what you mean by "derived attributes", or why it would be difficult to do data transformations on the models that deal with mori data structures. It'd be great to discuss this somewhere, maybe on #reactjs IRC? I'm jlongster there.","created_at":"2014-07-21T17:18:29Z","created_at_i":1405963109,"objectID":"8064734","parent_id":8064658,"story_id":8063870,"story_title":"Virtual DOM in Elm","story_url":"http://elm-lang.org/blog/Blazing-Fast-Html.elm","updated_at":"2024-09-19T20:57:58Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"voyou"},"comment_text":{"matchLevel":"none","matchedWords":[],"value":"I think "ampersat" was first coined in the 90s (when email suddenly made the @ sign more common), presumably by analogy with "ampersand". The earliest reference I can find is a suggestion from a viewer writing in to CBS Sunday Morning in 1994 (paywalled link, I'm afraid): https://www.lexisnexis.com/uk/nexis/docview/getDocForCuiReq?...
This newspaper article from 1996 also shows someone proposing "ampersat" apparently as a novel suggestion: http://www.independent.co.uk/life-style/bits--bytes-1317440...."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"At"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"http://furbo.org/2014/03/25/at/"}},"_tags":["comment","author_voyou","story_7849715"],"author":"voyou","comment_text":"I think "ampersat" was first coined in the 90s (when email suddenly made the @ sign more common), presumably by analogy with "ampersand". The earliest reference I can find is a suggestion from a viewer writing in to CBS Sunday Morning in 1994 (paywalled link, I'm afraid): https://www.lexisnexis.com/uk/nexis/docview/getDocForCuiReq?...
This newspaper article from 1996 also shows someone proposing "ampersat" apparently as a novel suggestion: http://www.independent.co.uk/life-style/bits--bytes-1317440....","created_at":"2014-06-05T10:02:25Z","created_at_i":1401962545,"objectID":"7851105","parent_id":7850091,"story_id":7849715,"story_title":"At","story_url":"http://furbo.org/2014/03/25/at/","updated_at":"2024-09-19T20:55:34Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"magicalhippo"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"Even if you didn't have mnemonics, you could use tab, arrow keys and alt if needed, to navigate, and space to "click" buttons and such.
So even if the developer forgot to configure mnemonics, which was as easy as prefixing a letter with ampersand, you could navigate by keyboard. Sometimes tedious but beats not being able."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"GUIs should be fully keyboard-driven"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://ckardaris.com/blog/2026/08/28/keyboard-driven-guis.html"}},"_tags":["comment","author_magicalhippo","story_49479837"],"author":"magicalhippo","comment_text":"Even if you didn't have mnemonics, you could use tab, arrow keys and alt if needed, to navigate, and space to "click" buttons and such.
So even if the developer forgot to configure mnemonics, which was as easy as prefixing a letter with ampersand, you could navigate by keyboard. Sometimes tedious but beats not being able.","created_at":"2026-08-28T20:57:30Z","created_at_i":1787950650,"objectID":"49484169","parent_id":49483132,"story_id":49479837,"story_title":"GUIs should be fully keyboard-driven","story_url":"https://ckardaris.com/blog/2026/08/28/keyboard-driven-guis.html","updated_at":"2026-08-31T08:34:22Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"ayanb"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"Currently, I am working on Ampersand (https://withampersand.com/)
It's a sync infra product that is meant to cut down 6 months of development time, and years of maintenance of deep CRM sync for B2B SaaS.
Every Salesforce instance is a unique snowflake. I am moving that customization into configuration and building a resilient infrastructure for bi-directional sync.
We also recently launched a pretty cool abstraction on top of Salesforce CDC which is notoriously hard to work with: https://www.withampersand.com/blog/subscribe-actions-bringin..."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: What are you working on? (October 2025)"}},"_tags":["comment","author_ayanb","story_45561428"],"author":"ayanb","comment_text":"Currently, I am working on Ampersand (https://withampersand.com/)
It's a sync infra product that is meant to cut down 6 months of development time, and years of maintenance of deep CRM sync for B2B SaaS.
Every Salesforce instance is a unique snowflake. I am moving that customization into configuration and building a resilient infrastructure for bi-directional sync.
We also recently launched a pretty cool abstraction on top of Salesforce CDC which is notoriously hard to work with: https://www.withampersand.com/blog/subscribe-actions-bringin...","created_at":"2025-10-13T03:14:05Z","created_at_i":1760325245,"objectID":"45564369","parent_id":45561428,"story_id":45561428,"story_title":"Ask HN: What are you working on? (October 2025)","updated_at":"2026-03-05T22:51:17Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"kjuulh"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"Another step in getting proficient with ampersand (or rather immutable refs), is pulling stuff from enums and structs, in an immutable way. I.e. Option<SomeStruct>, or Result<SomeStruct, ErrorKind>. Using as_ref and friends.
There was a great post the other day about the "Register of rust", and getting to know all the different variants of these features to be proficient and being able to build whatever you want.
The same goes for async features as well. Async especially requires that you understand lambdas, borrow checking and so on. As it can be quite tricky to send a value to a tokio::task::spawn!(...) if you don't have some mastery over the borrow checker.
When you get to taking lambda in a func, that should be async then you begin to get into the weeds of rust, and where some of the nasty compilers errors show up, some of the unhelpful variants, where you are expected to know the intricacies of how lifetimes work, and how rust handles generics vs impl vs enums etc.
In the beginning I just recommend using a good old Arc<Mutex<...>> if you need to pass stuff to functions, you can still shoot yourself in the foot, but you can take the optimizations piecemeal."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Getting Past \u201cAmpersand-Driven Development\u201d in Rust"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://fiberplane.com/blog/getting-past-ampersand-driven-development-in-rust"}},"_tags":["comment","author_kjuulh","story_35081027"],"author":"kjuulh","children":[35081943],"comment_text":"Another step in getting proficient with ampersand (or rather immutable refs), is pulling stuff from enums and structs, in an immutable way. I.e. Option<SomeStruct>, or Result<SomeStruct, ErrorKind>. Using as_ref and friends.
There was a great post the other day about the "Register of rust", and getting to know all the different variants of these features to be proficient and being able to build whatever you want.
The same goes for async features as well. Async especially requires that you understand lambdas, borrow checking and so on. As it can be quite tricky to send a value to a tokio::task::spawn!(...) if you don't have some mastery over the borrow checker.
When you get to taking lambda in a func, that should be async then you begin to get into the weeds of rust, and where some of the nasty compilers errors show up, some of the unhelpful variants, where you are expected to know the intricacies of how lifetimes work, and how rust handles generics vs impl vs enums etc.
In the beginning I just recommend using a good old Arc<Mutex<...>> if you need to pass stuff to functions, you can still shoot yourself in the foot, but you can take the optimizations piecemeal.","created_at":"2023-03-09T14:45:43Z","created_at_i":1678373143,"objectID":"35081689","parent_id":35081027,"story_id":35081027,"story_title":"Getting Past \u201cAmpersand-Driven Development\u201d in Rust","story_url":"https://fiberplane.com/blog/getting-past-ampersand-driven-development-in-rust","updated_at":"2024-09-20T13:30:02Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"dataflow"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"It's called uniform initialization syntax (aka "brace initialization" aka list-initialization [1]). tl;dr is everyone loves it due to the terseness, but I recommend against it. It's kind of like a forced cast/coercion in some ways (and it also looks ugly). Also be careful with parentheses since C++20; if they invoke implicit (aggregate?) constructors that would've traditionally needed {}, I think you can also run into similar casting issues. I just ran into this one a couple days ago; I haven't narrowed it down yet, but it seemed to be due to this.
The second one is a lambda (which, if you're not familiar with the term, are anonymous functions/functors); the entries in the initial brackets define the captured variables (if any), and whether they're captured by reference (with ampersand) or by value (without).
[1] https://en.cppreference.com/w/cpp/language/list_initializati..."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"std::latch"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://en.cppreference.com/w/cpp/thread/latch"}},"_tags":["comment","author_dataflow","story_27217877"],"author":"dataflow","children":[27219025],"comment_text":"It's called uniform initialization syntax (aka "brace initialization" aka list-initialization [1]). tl;dr is everyone loves it due to the terseness, but I recommend against it. It's kind of like a forced cast/coercion in some ways (and it also looks ugly). Also be careful with parentheses since C++20; if they invoke implicit (aggregate?) constructors that would've traditionally needed {}, I think you can also run into similar casting issues. I just ran into this one a couple days ago; I haven't narrowed it down yet, but it seemed to be due to this.
The second one is a lambda (which, if you're not familiar with the term, are anonymous functions/functors); the entries in the initial brackets define the captured variables (if any), and whether they're captured by reference (with ampersand) or by value (without).
[1] https://en.cppreference.com/w/cpp/language/list_initializati...","created_at":"2021-05-20T08:09:48Z","created_at_i":1621498188,"objectID":"27218651","parent_id":27218628,"story_id":27217877,"story_title":"std::latch","story_url":"https://en.cppreference.com/w/cpp/thread/latch","updated_at":"2024-09-20T08:34:35Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jasode"},"comment_text":{"matchLevel":"none","matchedWords":[],"value":">I think much of modern C++ should be rejected [...] then fricken switch language! There are countless better alternatives today: Rust, Swift, D, Haskell etc.
The reality is that many projects are enabled more by existing libraries & tools rather than blank slate clean language syntax.
Some example domains of libraries & tools where C++ is the 1st-class client instead of Rust/Swift/D/Haskell:
+ deep learning: NVIDIA CUDA api is C++
+ HPC High Perfomance Computing: Intel MKL math library is C++
+ physics engine for video games: Unreal game engine is C++
+ latest cpu chip : ARM Allinea dev tools for the new ARM/Neoverse chips (e.g. latest AWS Graviton2 servers) is C++
+ Qt GUI is C++
Because of the extensive C++ ecosystem, you get a counter-intuitive situation where programming the latest cutting-edge apps requires a 35-year-old language from 1985 instead of the newer Rust language from 2012. I predict this delta of tools+libraries between C++ and Rust/Swift will continue to exist for 10+ years. Recommending/lecturing people to use Rust/Swift/D overlooks the reasons that many programmers use C++. It's not a random choice.
E.g., a realistic starting point for a project might be: "What's a good game engine... oh, it's Unreal, and that's C++." -- instead of -- "Rust has clean syntax of ownership and borrow with "&" ampersand symbol instead of ugly warts of unique_ptr<T> and std::move() in C++ so I'll code a game in Rust."
Sometimes, we look at the ecosystem first, and then work backwards from that to make programming choices.
It's when you have the luxury of a greenfield project that doesn't need legacy dependencies that choosing alternative cleaner syntax of Rust/Swift is possible. Amazon AWS and MS Azure are examples of doing new bare-metal projects with Rust instead of C++."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"Std::visit is everything wrong with modern C++ (2017)"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://bitbashing.io/std-visit.html"}},"_tags":["comment","author_jasode","story_25314126"],"author":"jasode","children":[25316237,25316315,25316383,25316644,25317039,25319958,25321031],"comment_text":">I think much of modern C++ should be rejected [...] then fricken switch language! There are countless better alternatives today: Rust, Swift, D, Haskell etc.
The reality is that many projects are enabled more by existing libraries & tools rather than blank slate clean language syntax.
Some example domains of libraries & tools where C++ is the 1st-class client instead of Rust/Swift/D/Haskell:
+ deep learning: NVIDIA CUDA api is C++
+ HPC High Perfomance Computing: Intel MKL math library is C++
+ physics engine for video games: Unreal game engine is C++
+ latest cpu chip : ARM Allinea dev tools for the new ARM/Neoverse chips (e.g. latest AWS Graviton2 servers) is C++
+ Qt GUI is C++
Because of the extensive C++ ecosystem, you get a counter-intuitive situation where programming the latest cutting-edge apps requires a 35-year-old language from 1985 instead of the newer Rust language from 2012. I predict this delta of tools+libraries between C++ and Rust/Swift will continue to exist for 10+ years. Recommending/lecturing people to use Rust/Swift/D overlooks the reasons that many programmers use C++. It's not a random choice.
E.g., a realistic starting point for a project might be: "What's a good game engine... oh, it's Unreal, and that's C++." -- instead of -- "Rust has clean syntax of ownership and borrow with "&" ampersand symbol instead of ugly warts of unique_ptr<T> and std::move() in C++ so I'll code a game in Rust."
Sometimes, we look at the ecosystem first, and then work backwards from that to make programming choices.
It's when you have the luxury of a greenfield project that doesn't need legacy dependencies that choosing alternative cleaner syntax of Rust/Swift is possible. Amazon AWS and MS Azure are examples of doing new bare-metal projects with Rust instead of C++.","created_at":"2020-12-05T16:40:32Z","created_at_i":1607186432,"objectID":"25315815","parent_id":25314924,"story_id":25314126,"story_title":"Std::visit is everything wrong with modern C++ (2017)","story_url":"https://bitbashing.io/std-visit.html","updated_at":"2024-09-20T07:25:20Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tannhaeuser"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"> And it's really the URL (URI, IRI, URN...) that makes the web.
Well Chrome devs seem to disagree, with the recent push to hide URLs, and so do SPA devs. Is the article meant to save the URL, or rather a fairwell? Anyway, URLs aren't particularly well-designed IMO, for their use of the ampersand char as separator in the query part alone, since these conflict with ampersand as used for starting entity references in HTML and other SGML docs."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"The History of the URL"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://blog.cloudflare.com/the-history-of-the-url/"}},"_tags":["comment","author_tannhaeuser","story_22493216"],"author":"tannhaeuser","children":[22495899],"comment_text":"> And it's really the URL (URI, IRI, URN...) that makes the web.
Well Chrome devs seem to disagree, with the recent push to hide URLs, and so do SPA devs. Is the article meant to save the URL, or rather a fairwell? Anyway, URLs aren't particularly well-designed IMO, for their use of the ampersand char as separator in the query part alone, since these conflict with ampersand as used for starting entity references in HTML and other SGML docs.","created_at":"2020-03-05T17:22:55Z","created_at_i":1583428975,"objectID":"22495680","parent_id":22494456,"story_id":22493216,"story_title":"The History of the URL","story_url":"https://blog.cloudflare.com/the-history-of-the-url/","updated_at":"2024-09-20T05:47:11Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jhallenworld"},"comment_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"I've implemented something like this in a non-LISP syntax language. See:
https://github.com/jhallen/joes-sandbox/tree/master/lang/ivy
The idea is that in a function call, the arguments are normally evaluated before the call as usual. But if a formal argument in the function's declaration is prefixed with ampersand then during a function call, that argument is not evaluated, but is instead packaged up as a zero-argument lambda function. The argument can be called later using the normal function call syntax, but also there is semantic sugar: the * operator calls a zero-argument function.
Further, when a variable is evaluated, you get both its value and a reference to it. This allows variables to be evaluated before being assigned to in assignments. This sounds weird, but it works with the above. You can make a "set" function which does the same thing as assignment:
# Define set function\n fn set(&left, right) {\n *left = right\n }\n\n # Set x to 10\n set x 10\n fn switch(&val) {\n var rtn, x, v = *val\n x = 1\n while x < len(argv) - 1 {\n if *argv(x) == v {\n return *argv(x + 1)\n }\n x += 2\n }\n if x < len(argv) {\n return *argv(x)\n }\n return void\n }\n switch 2 1 {\n print "one"\n } 2 {\n print "two"\n } 3 {\n print "three"\n } {\n print "default"\n }\nRight now the delayed arguments are evaluated in the closure of the function call (so they are lexically scoped). The wrap/unwrap concept from this paper gives me ideas on how to make this more versatile..."},"story_title":{"matchLevel":"none","matchedWords":[],"value":"$vau: the ultimate abstraction (2010) [pdf]"},"story_url":{"matchLevel":"none","matchedWords":[],"value":"https://web.wpi.edu/Pubs/ETD/Available/etd-090110-124904/unrestricted/jshutt.pdf"}},"_tags":["comment","author_jhallenworld","story_18405014"],"author":"jhallenworld","children":[18415976,18416695,18417031,18418009,18418968],"comment_text":"I've implemented something like this in a non-LISP syntax language. See:
https://github.com/jhallen/joes-sandbox/tree/master/lang/ivy
The idea is that in a function call, the arguments are normally evaluated before the call as usual. But if a formal argument in the function's declaration is prefixed with ampersand then during a function call, that argument is not evaluated, but is instead packaged up as a zero-argument lambda function. The argument can be called later using the normal function call syntax, but also there is semantic sugar: the * operator calls a zero-argument function.
Further, when a variable is evaluated, you get both its value and a reference to it. This allows variables to be evaluated before being assigned to in assignments. This sounds weird, but it works with the above. You can make a "set" function which does the same thing as assignment:
# Define set function\n fn set(&left, right) {\n *left = right\n }\n\n # Set x to 10\n set x 10\n fn switch(&val) {\n var rtn, x, v = *val\n x = 1\n while x < len(argv) - 1 {\n if *argv(x) == v {\n return *argv(x + 1)\n }\n x += 2\n }\n if x < len(argv) {\n return *argv(x)\n }\n return void\n }\n switch 2 1 {\n print "one"\n } 2 {\n print "two"\n } 3 {\n print "three"\n } {\n print "default"\n }\nRight now the delayed arguments are evaluated in the closure of the function call (so they are lexically scoped). The wrap/unwrap concept from this paper gives me ideas on how to make this more versatile...","created_at":"2018-11-09T16:43:58Z","created_at_i":1541781838,"objectID":"18415732","parent_id":18405014,"story_id":18405014,"story_title":"$vau: the ultimate abstraction (2010) [pdf]","story_url":"https://web.wpi.edu/Pubs/ETD/Available/etd-090110-124904/unrestricted/jshutt.pdf","updated_at":"2024-09-20T03:16:07Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"laurenzlong"},"story_text":{"matchLevel":"none","matchedWords":[],"value":"Hey HN! I\u2019m one of the co-founders of Ampersand and we\u2019re excited to launch our developer docs today! Ampersand is built for SaaS engineers who want to:
- Read data from their customers\u2019 SaaS (e.g. Salesforce, Hubspot).
- Write data to their customers\u2019 SaaS.
- Subscribe to events happening in their customers\u2019 SaaS (including creates, deletes and field updates).
We feature a Terraform-like declarative interface for defining integrations, embeddable UI components for your users to set up and manage their integrations, and a management console for your team to monitor and troubleshoot.
We\u2019re launching our docs ahead of our product because we believe that docs are one of the most important things to get right in building a developer product, and we want to get early feedback on it. Looking forward to hearing your feedback in the comments below!"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: Ampersand \u2013 \u201cTerraform for Integrations\u201d"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["withampersand"],"value":"https://docs.withampersand.com/docs"}},"_tags":["story","author_laurenzlong","story_35562089","show_hn"],"author":"laurenzlong","children":[35565224],"created_at":"2023-04-13T21:08:59Z","created_at_i":1681420139,"num_comments":2,"objectID":"35562089","points":6,"story_id":35562089,"story_text":"Hey HN! I\u2019m one of the co-founders of Ampersand and we\u2019re excited to launch our developer docs today! Ampersand is built for SaaS engineers who want to:
- Read data from their customers\u2019 SaaS (e.g. Salesforce, Hubspot).
- Write data to their customers\u2019 SaaS.
- Subscribe to events happening in their customers\u2019 SaaS (including creates, deletes and field updates).
We feature a Terraform-like declarative interface for defining integrations, embeddable UI components for your users to set up and manage their integrations, and a management console for your team to monitor and troubleshoot.
We\u2019re launching our docs ahead of our product because we believe that docs are one of the most important things to get right in building a developer product, and we want to get early feedback on it. Looking forward to hearing your feedback in the comments below!","title":"Show HN: Ampersand \u2013 \u201cTerraform for Integrations\u201d","updated_at":"2024-09-20T13:51:46Z","url":"https://docs.withampersand.com/docs"}],"hitsPerPage":20,"nbHits":13,"nbPages":1,"page":0,"params":"query=withampersand&advancedSyntax=true&analyticsTags=backend","processingTimeMS":16,"processingTimingsMS":{"_request":{"queue":7,"roundTrip":23},"afterFetch":{"format":{"highlighting":2,"total":2},"merge":{"mergeLoop":{"prepareNextHit":5,"total":5},"total":5},"total":5},"fetch":{"query":4,"scanning":5,"total":10},"total":16},"query":"withampersand","serverTimeMS":26}