Immediately opened it and laughed out loud. Perfect execution, no notes.

I do think we lost something in the middle ~20 years there as the industry (understandably) matured. For those of us in tech-forward companies, and industries, everything continued forward... but what I'd certainly missed was how much fear(?) was in the industries that were left behind.

I think this is a pre-existing problem, as there's quite a lot of people who now have senior in their title but their expertise is very shallow, as they've just been picking tickets up most of their career and have been handed acceptance criteria and requirements on a plate, without really being involved in that part of the process. Obviously not talking about the best of the best here, but the other 90% of working software engineers today.

Inside of organisations, there's still a lot of place for that very human back and forth on what exactly you're building. Navigation of internal politics, org structures etc. What is really exciting for me, is I've never seen so much appetite to actually build ... there's plenty of companies out there for whom that was unthinkable for one reason or another, and now they're hungry for it. Of course it means those companies are going to be learning for the first time the ups and downs of owning your own stack, and there's plenty of opportunity for us there too.

I've noticed that I'm now getting frustrated if I forget the question mark, as I actively want and prefer an assistant response. I'm sure this wouldn't always be true, but chat is a nice way to do search... and I suspect more thorough than I'd actually be at checking longer-tail sources.

My point is, I think this interface might be what a search engine for humans looks like now.

I'm always pleased when working with a dev who has Rails experience even if they've since moved stack, as often they have picked up and learned the value of these good behaviours. Perhaps it's as much a community thing as a framework thing, or combination of both.

Agentic development definitely still has room to improve, but I suspect that there is some future framework (maybe even language) designed to help minimise these types of mistakes.

It is notable that his perspective in this talk is very much from a developer-user side rather than someone who is responsible for the framework itself. That surprises me, and I suspect it is not a good omen for Rails.

For all of this embrace of agentic development, there is nothing here on how they are adapting the framework for this new agentic development reality. Agents do currently work well with Rails, but there's nothing here pushing things forward as best as I can see.

I know for my own projects I've largely moved to Elixir/Phoenix, for similar reasons to his use of Rust... I didn't want to have to learn it, but now I don't have to and I get to benefit from its strengths.

I set out to solve that with https://stayupfront.com and now that the build is in a good place i’m finally having to bite the bullet and learn marketing. I’m also realising that all the advice to start with marketing first was probably good advice!

I know this sounds like an ad, but I was pretty impressed with it

I'd been considering mostly an English speaking audience at launch. To be more accurate, I was generally thinking about users physically local to me initially, so I could meet with them for customer onboarding and feedback etc.

Your post has got me thinking on an approach to making translation work in an open and honest way, so that is something I will experiment with and hopefully get in quite quickly.

If you'd be interested in helping me test that, please feel free to reach out to hello@stayupfront.com

If any founders find themselves reading this, and don't think it's the best idea to self-host your own support infra, I've just spent the last 6+ months building stayupfront.com which has, I think, quite reasonable pricing, and a few more features than this... largely around the customer's portal experience (changelog, roadmap, etc.) and includes monitoring & incident management which I think should all be ran from the same surface.

I've only just soft-launched, so still have founding pricing on there. Would certainly love to speak to others in this space too, as I was surprised how neglected an area it seemed to be when I was trying to find a replacement for jira service desk for a company I was working with at the beginning of this year.

Passwords were a really poor solution to the problem of security, they didn't take the human factor into account. After a rocky start, I'm now finding passkeys super easy and convenient to use. Far more convenient than OTP codes.

I appreciate that if you're OS/browser doesn't integrate nicely with passwords you might be in for a bad time. I'm having a great time with 1Password, though I believe native apple handles them nicely now too – and I suspect this is true of any modern password manager (even the ones built into the browser).

I too built my own equivalent of this (belfry.robgough.net). I take it as a good thing, we're all using these tools and coming to similar conclusions.

I suspect over time it'll settle down, once we've gotten comfortable with the new ways of working and found the new normal.

I actually started with a Mac app primarily, as I wanted to have an easier way to switch sessions with the mouse and see Claude Code's status at a glance (I had herdr envy, but wanted to keep tmux). I then figured why not do the iOS/iPad version while I was at it.

Highly encourage you to build out a Desktop version, I'm now using mine as my only terminal and wouldn't go back. Working across machines feels seamless.

I really wanted to have background audio and make it so the keyboard would directly record audio etc, but my first pass didn't make it through app review (and that was just keeping background audio listening AFTER you'd already started a recording). I could maybe have fought it, but figured if I was already butting up against app review there was little point as they'd likely reject in a future release anyway.

Re: analytics, It is quite weird having no idea how many people are using the app. It does leave you a little blind, but I figure people will get in touch if they have big enough problems with it.

For the Google app, I believe Gemma E2B and E4B both have audio input, so I suspect they're using one of those.

My initial Mac version actually had three additional steps that you could toggle, obviously at the cost of some speed. That is what the website talks about, although nowadays for my own use I've reduced that to just one step and found that it's pretty great. I've got a new version in test to tidy that up, but still lets you define as many steps as you want.

It also helps to have a "boring" framework with strong opinions and strong community standards etc.

I wouldn't claim it to be the best as I'm not sure how you'd measure that, but I can say that in my experience it is letting me build things to a decent standard really rather quickly.

If you're building something new today, I'd generally recommend starting with a framework that you already know. But for those of us who already know Rails, it continues to be a wonderful choice. I'm playing with Phoenix LiveView for some projects, which is letting me build real-time UI's really easily – but they have some real-time requirements which Rails can do but is not it's strength. For anything a little more CRUD, it's a no-brainer.