This week I've been investigating the @astro web framework, including its Starlight documentation template.

There are loads of useful features and sensible defaults, which propel it way beyond "just works" territory. It feels like a great choice for creating and maintaining web sites where the content is static or mostly static (via "islands").

As such the documentation web site for sharp will be using it from the next release onward. 🚀

My current work contract is coming to an end and I’ll be looking to start a new opportunity at the beginning of March. Please consider reaching out if you use Elixir and you’re looking for a Head of Engineering, Engineering Manager, or Principal Engineer. https://www.linkedin.com/in/james-edward-gray-ii/

#OpenToWork

EDIT: started a new job last week!
Hey friends,

I'm restarting my job search; I had an offer, but it fell through.

Remote US preferred, but hybrid Washington, DC works too. I have 17-ish YOE as a software engineer, and have worked on both frontend and backend, but I lean toward the backend.

#Elixir #Phoenix, #Python #Django, and #React are what I know best.

Hoping to #GetFediHired

Edit: adding my LinkedIn
https://LinkedIn.com/in/mackenziemorgan

2025 is the make-or-break year for companies with investors who want to see returns for all the dollars they’ve thrown at “AI.”

I’m reminded of a CTO of a large corporation who said earlier this year, “No one knows the winning use-case for AI. We’re all scrambling to find it, and the first one there is going to make it big.”

If no one makes it 2025, I think investors will lose interest. Many companies will continue trying to manifest something, though, because their investors will demand it.