June Blog

Love to see Coast getting some attention again! I got my start into Clojure with it working with Sean on small web apps written in Coast. I even gave a talk about it at the Berlin Clojure conference https://youtu.be/24PRtDJGvW8 The first project we built together with it was called magehash, and it was an app to monitor websites for Magecart attacks (code injection stealing credit card data). That project ended up not working out, but I’m using a lot of the lessons I learned with Sean at my new project (https://www.june.so) which is ironically a Rails app and we keep in touch on Twitter regularly

In the footer they link to several versus pages, including one for Pendo[1]. Perhaps that can shed some light? [1]: https://www.june.so/blog/june-vs-pendo

I've enjoyed, and been lucky to work at companies where engineers are focused on customer outcomes. I would also cite Hiten Shah's engineering driven development: https://www.june.so/blog/the-rise-of-engineering-driven-development-ed… At the end of the day, the stack is collapsing itself, and the lines are blurring because we want people to own the total outcome more often than throwing responsibilities over the wall to each other. That doesn't mean engineers are going to design, but they should know what a good design looks and feels like. That doesn't mean designers or product should write code, but they should be able to engage in high level architecture discussion to understand the capabilities of their products. I have not read it yet but there's a book by David Epstein (not that one), "Range: Why Generalists Triumph in a Specialized World". I'm interested because for the last 10 years I've thought of myself as a generalist but always thought companies were looking for specialists. I could show immense value when I got to those companies, but I don't typically think companies are looking for generalist. They are looking for specialists to solve an acute problem.