How do you get yourself psyched up to lay the foundations for a new project?

You get to research the best pieces of our ecosystem, which can be gratifying in itself If creating the boilerplate itself is too much of a hassle you can always start from a template and/or framework. If you keep things modular, eventually the architecture can become 'your own', without template cruft

I just channel this meme

more seriously, I try to use different libraries and techniques just to try it out and keep it interesting (but time box it if it's not a side project)

it's easy to be too conservative and just choose the most boring things, but also easy to be too aggressive and force techniques and libraries even if they don't fit the problem. so, balance 🙂

This is the life of a commercial project. Changes necessarily happen during the project. Requirements change. Architectures are discovered to not cover certain cases. A customer changes their mind. As a result, a system that we felt would be robust and elegant… isn't. That doesn't make it useless. Indeed, if it responded appropriately to changes, it will be the best it could be. But it just won't be what was hoped for back when the repo was fresh and hope filled the air 🙂

absolutely

Non-commercial projects are a different matter. You can make them for yourself. This means that you can do whatever you want, and stick to it! But, that means it might not be useful

But they're elegant and fun 😊

Some morse than others!

Can't say I expected to see EatWhatYouKill in a stack trace 😂

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.produce(EatWhatYouKill.java:135)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
	at java.lang.Thread.run(Thread.java:750)

Yeah, that still makes me chuckle every time I see it 🙂

https://thewaroncars.org/2022/01/26/the-end-of-uber-with-cory-doctorow/

Are clojure.spec releases tied to clojure releases? Or is it theoretically possible we'll be seeing a stable release of spec before 1.12?

they are independent

we've already released a spec update that 1.11 will depend on for example

or are you asking about spec 2

yeah

a spec which doesn't contain alpha in the name

well, we could just remove the alpha :)

but to answer your question, I don't know what will happen by the time of 1.12 (given that we have not yet even released 1.11)