Long-Term Funding, Update #1
As part of Clojurists Together's Long-Term Funding for 2023 I talked about working on clojure-doc.org which I had resurrected a few years ago, as a GitHub Pages project, powered by Cryogen.
As part of Clojurists Together's Long-Term Funding for 2023 I talked about working on clojure-doc.org which I had resurrected a few years ago, as a GitHub Pages project, powered by Cryogen.
I've mentioned in several posts over the years that I switched my development setup from Emacs to Atom, initially with ProtoREPL and later with Chlorine, and then to VS Code, initially with Clover (a port of Chlorine) and more recently with Calva. There were several detours along the way, but that is the overall arc.I've also mentioned a couple of times that I use Portal now, as an extension inside VS Code (after previously using Reveal and, before that, Cognitect's REBL).I've also published my VS Code and Calva setup files on GitHub.But I haven't really talked about what that experience is like on a day-to-day basis or any specifics of my integrated workflow.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
About a year I posted that I had deleted both my Twitter and Facebook accounts.In March, my wife & I visited friends and family in England (for the first time in three years) as my mother had been diagnosed with AAA (abdominal aortic aneurysm) and it had grown substantially -- the doctor has given her "months" to live, although she's already lasted longer than that!
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
Back when I was working on the clojure.java.jdbc Contrib library, I moved its documentation to clojure-doc.org so that the community could contribute to it, without the CLA that covers contributions to Contrib itself. Over time I became a general contributor to clojuredocs/guides which was the repository behind the clojure-doc.org web site.Unfortunately, about three years ago, the infrastructure that runs clojure-doc.org became inaccessible to the maintainers of the site so, although pull requests continued to be accepted, the site itself could no longer be updated. I talked with Michael Klishin, the original creator of the site, about moving it to GitHub pages but we never quite got around to it. Until today.
I've been on both Twitter and Facebook for a very long time and it definitely has had its ups and downs. A couple of times over the last six years, I've felt the need to take a complete break from Facebook and have deactivated my account for up to a couple of months each time. I've also taken several breaks from Twitter, although I didn't deactivate my account.I've finally decided that the cons are outweighing the pros for me on social media so I have shutdown (deleted) both my Twitter account and my Facebook account. Permanently.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
With the recent release of tools.build, I wanted to provide a quick example of using it for a CI-like pipeline.tools.build is focused on "building" things and when the subject has come up on Slack, the feedback has been that the CLI already has a good story for running tests etc, and the consensus seems to be that running multiple CLI commands is the intended usage.
This is part of an ongoing series of blog posts about our ever-evolving use of the Clojure CLI, deps.edn, and Polylith, with our monorepo at World Singles Networks.
Back in April, I talked about us dipping into Polylith at work in deps.edn and monorepos II, and also our planned migration away from clj-http. Since then, we've completed the migration to http-kit and we've also migrated away from clj-time (which is deprecated, because it is based on Joda Time). We've also started refactoring our subprojects into Polylith components. This is another periodic update on where we are in our journey.
A couple of months ago, I wrote about our use of deps.edn with our monorepo at work. I've updated that post to reflect changes we've made recently and I'm going to talk in more detail about those changes in this post.
Our Clojure team is a big fan of reducing dependencies and, in particular, avoiding dependencies that are known to be troublesome (such as the special circle of hell that is all the different versions of the Jackson JSON libraries).
At World Singles Networks llc we have been using a monorepo for several years and it has taken us several iterations to settle on a structure that works well with the Clojure CLI and deps.edn.Updated April 21st, 2021 to reflect recent changes in our setup. See deps.edn and monorepos II for more details.
For about a decade, I used to speak regularly at conferences and user groups around the world. In 2013, I decided to take a break and just enjoy attending events (here's a small selection of my presentations covering the last three years of that decade).
I've written before about how I switched from Emacs to Atom at the end of 2016, where I initially used ProtoREPL (which is no longer maintained) and then I switched to Chlorine at the end of 2018. I've been very impressed with the work that Mauricio Szabo has done on Chlorine, adding a way to extend the functionality using ClojureScript so that you can add your own commands -- as I do in my atom-chlorine-setup repo so that I can easily work with Reveal (and previously with Cognitect's REBL). I've posted a few Atom/Chlorine/REBL videos to YouTube showing my workflow.
seancorfield/next.jdbc 1.1.610Updated 2022-09-12 to clarify camel-snake-kebab usage in more recent next.jdbc versions.
seancorfield/next.jdbc 1.0.445This morning I released 1.0.445 and realized it's the sixth release since I last mentioned it in a blog post, so I thought it would be helpful to summarize all of the changes made so far in 2020. 1.0.13 came out at the end of December and I decided to switch from MAJOR.MINOR.PATCH versioning to MAJOR.MINOR.COMMITS versioning since I'd already made the commitment to no breaking changes -- only fixative/accretive changes -- when the library originally moved from Alpha to Beta a year ago.
Wrapping Up 2019It's been a while since I blogged about the projects I maintain so I figured New Year's Eve 2019 was a good time to provide an update!
An interesting Clojure question came up on Quora recently and I decided that my answer to "how do you use clojure.spec" there should probably be a blog post so that folks without a Quora account can still read it. [If you do have a Quora account, feel free to read it there instead and upvote it!]The original question on Quora was:
Lots of ReleasesOver the last week or so I've released minor updates to several of the projects I maintain, so I thought it would be nice to have a summary blog post rather than a scattering of minor announcements.
next.jdbc 1.0.0 and 1.0.1First off, seancorfield/next.jdbc 1.0.0 was released on June 13th, 2019 (and I announced it on ClojureVerse but did not blog about it), and yesterday I released seancorfield/next.jdbc 1.0.1 which is mostly documentation improvements.