I just started reading this yesterday, and so am glad to know some of this is covered in there.

Thx @U051MHSEK! 🙂

@U051MHSEK Incidentally, Dr. Cem Kaner was also one of the authors of a hugely important paper in this space: “MANAGING THE PROPORTION OF TESTERS TO (OTHER) 1 DEVELOPERS” http://www.testingeducation.org/BBST/foundations/Kaner_pnsqc_ratio_of_testers.pdf Elisabeth Hendrickson has been a huge influence on me over the years, and is one of the co-authors, and you can hear an interview I did with her here: https://itrevolution.com/the-idealcast-episode-3/

The context for this was that at the time, Microsoft was recommending Dev/QA ratios of 1:1!

In the following Dispatch from the Scenius, Hendrickson mentions being introduced by someone as the QA director at Cloud Foundry who basically abolished QA. I've been wondering for the past several weeks... how facetious is that? Does that mean a dedicated QA department was disbanded and individual engineers were moved onto specific teams to work alongside developers? Or that developers were told that they alone have to own the work previously done exclusively by QA?

Ha! Nope, not facetious at all! She was hired as the Director of Quality Engineering, and then proceeded to disband the “QA Department,” moving those responsibilities (and QA engineers) to the product teams. So very close or identical to your first answer!

> The more modern approach is that QA and Infosec become more consultative functions. Wholeheartedly second this. > proceeded to disband the “QA Department,” moving those responsibilities (and QA engineers) to the product teams "Responsibility closest to the responsible" is generally a good idea, however, in otherwise-usual organisations, it comes with the usual risks of unbundling --- increased communication and coordination overhead, duplication of effort, creation of new silos etc. Who owns things for common libraries and services, for example? Or who will take responsibility for the e2e validation of #{set of services}? etc. I've been at the receiving end of the fallout of such a re-org :)

Not only CLJS but also using re-frame, if that's relevant: • https://github.com/status-im/status-react • https://github.com/JoelSanchez/ventas (not sure why it's archived - maybe abandoned) • https://github.com/district0x/memefactory • https://github.com/district0x/name-bazaar • https://github.com/lipas-liikuntapaikat/lipas

Pitch

All Street has a "client-logic heavy" single page application written in Clojure + ClojureScript (B2B product - but screenshots on the website). https://www.sevva.ai/ Uses uix for react integration.

Vouch uses ClojureScript, both in the front-end (see https://github.com/vouch-opensource/krell) and in embedded systems.

Nextjournal

https://www.maria.cloud/ might also be worth a look - it's more than it seems at the first glance!

I’m building this: https://www.nette.io/ Heavy but, feels light 😛

We use clojurescript for our front end at Mayvenn (http://mayvenn.com). We’re an e-commerce site for human hair wigs and bundles. You can see the github repo here: https://github.com/mayvenn/storefront

http://Exoscale.com front-end is now cljs as well. Clojure is very present on the backend

http://storrito.com and http://audiocado.com clj, cljs, reagent, datomic

Thanks everyone! 😄

On the open-source side, both Chlorine and Clover (Clojure/Script plug-ins for Atom and VSCode) are written in ClojureScript - which leads to some very interesting use-cases of developing a plug-in for a language, written in that language, using the plug-in itself to debug itself 🤯

Recap, a voice recognition and transcription app, uses ClojureScript entirely on the backend. https://play.google.com/store/apps/details?id=com.griffinscribe.recap

@U01EYFBLHPX pretty cool! Out of curiosity, any clojurescript framework used on the backend?

@U0FKCGH9N See my recent post at https://clojurians.slack.com/archives/C06MAR553/p1643912555499679 for details. I used shadow-cljs for building the code. I might add some cljs html templating libraries like hiccup/reagent for a future web-based version of the app.