Exactly. I think only software developers believe AI is going to kill app subscriptions, because they're the ones who can actually wrangle the output into something maintainable.
For anyone without dev or product experience, getting beyond a basic feature set and keeping it running reliably (or roll it out to > 1 user) is still a massive challenge.
Me too! I usually get pretty obsessed with a new topic out of deep curiosity. I then dive deep, think about it a lot, hunt down answers to burning questions. At some point this’ll fade and then I feel like I know enough.
I’m not sure where you’ve got the stats from, but student visas granted dropped since 2022, acc to UK gov (-5% in 2023, -14% in 2024).[0]
Combined with universities' increasing reliance on international student income (over the last years) and issues accessing research funding, this can get universities into trouble.
Yes I’d agree with that. International student income dropped, rounds of layoffs.
Some universities are better at optimising for rankings, see also REF research funding and how much effort and resources are spent on it, which varies by university: https://2029.ref.ac.uk/about/what-is-the-ref/
To me, this recurring narrative of product versus engineering is both tiresome and misguided.
In well-run companies, commercial, product, and engineering teams are aligned - overused as the term may be. Any misalignment points to fundamental flaws in company culture. In my experience, this misalignment is what causes so much pain in high-growth companies that introduce managerial roles to a previously founder-led culture - not the product owner role as such.
It's counterproductive to stereotype POs as overbearing taskmasters, or to cast engineers as creators of beautiful but useless code. Such perceptions, if prevalent within a company, should be the primary issue to address. There's certainly features that POs don't enjoy working on but they have to - same for engineers (think about all those compliance features).
I believe POs can serve as a vital bridge between commercial and engineering departments. They clarify how features add customer value, explain business objectives behind projects and help decide what's next on the roadmap. Additionally, they help maintain focus by minimising abrupt directional shifts in the roadmap that could waste resources. And they can weigh in on decisions when they see that engineering teams are already strained by other projects or any business-as-usual work.
In that way, everyone is be enabled to do their best work and the PO is not reduced to the cookie cutter version the author portrays in the article.
I ended up staying with Hugo because I post loads of photos and image optimisation, or responsive images, was much easier to implement in Hugo.
I heard Astro now has better image processing, so I might give it another try as migrating templates and posts between Hugo and Astro was actually pretty easy.
If you buy an off-brand Moka pot, make sure you can change the rubber seal. That's the only part that deteriorates over time and should be regularly replaced.
Congrats, interesting site and I really enjoyed watching the videos.
I found it slightly annoying that navigating back didn't work as smoothly as on YouTube, for example:
When the video is playing in the overlay, the URL does change when you attempt to go back, but the video continues playing. I'm not sure if that's intentional or something that could be improved.