masilotti.com VS railsdevs.com

If your like this approach to building hybrid native mobile apps, I highly recommend following Joe Masilotti at https://masilotti.com/

I only read three emails newsletters, and Joe’s is one of them because it’s roughly once per month and it keeps me current on all the things happening with Hotwire and Turbo Native apps.

And you're not wrong - there are very few resources available on Turbo Native development. My blog, workshop, and YouTube videos are practically the only things out there. And William Kennedy is sharing his process learning Android, which is helping fill that gap.

add contact links as well (LinkedIn, Github) (ex. https://masilotti.com/ )

update your website - make the site clean and direct about who you are, what you do, what you're looking for, and where you are (ex. https://masilotti.com/ )

be specific in your title & intro - "Junior Python/React Fullstack Dev" and "Locacted in Tulsa, Ok" mean more than "I thrive on challenges". What's the most important info about what you do and who you are? Make that first and prominent. (ex. https://masilotti.com/ )

add your photo in place of sonar. This site is selling your services and it gives more trust to have your face on your website. ex. https://masilotti.com/ ) You can move a block of text with skills below your "Hi, I'm Patrick" text.

Turbo Native in its current form requires a fair amount of iOS knowledge (and code!) to get working. I'm trying to fill that gap with my blog, workshops, and live streaming sessions. [1]

But it's no excuse for what this library could be if we invest more time into it. In an ideal world the library handles 90% of the boilerplate required to make an iOS app work. I'm talking authentication, pushing/presenting controllers, sensible defaults for Path Configuration, etc. All the stuff that I have to add to every single Turbo Native app I work with. (12+ since I last counted.)

Then devs can focus on differentiation and exciting features like push notifications, native integrations, fancy animations... while the core of the logic remains on the Rails app.

I'm hoping that getting more maintainers (like me!) on the repo will help kickstart this. And I'm excited to see more interest on both HN and Twitter in the framework.

[1] https://masilotti.com

I blog about Turbo Native and run the monthly ⚡️ Hotwire dev newsletter!

I'm also building a reverse job board for AI developers like me to find full-time, part-time or contract work. Developers can make a free profile to promote their AI/ML skills and hiring companies can search the profiles and contact developers through the platform. It's an open-source open startup that's a fork of a similar project for rails developers.

railsdevs.com - Specific to Ruby on Rails

Other than reading, the best way to learn domain modeling is to read a lot of code, e.g. Rails codebase (to learn how to model the domain of web applications) or open source repositories (a good one is Railsdevs). Over time, you'll find and understand the common patterns enough to use on your own.

To find a freelance, it could depend on your location. There are https://www.malt.uk, https://railsdevs.com

Rails Devs - https://railsdevs.com/ - create and businesses reach out.

So far I've been using the Rails Guides on testing and studying the source code of railsdevs.com. Any guidance is greatly appreciated, thank you in advance!

Hey, I totally agree with you. Linking to the entire newsletter can be quite overwhelming and comes off as spammy. It would be great if you included the specific links to the tweet or the GitHub repo mentioned in the newsletter. The links you provided, https://twitter.com/joemasilotti/status/1639261944652914688 and https://github.com/joemasilotti/railsdevs.com/which, are definitely more helpful and provide a better user experience. Thanks for sharing!

RailsDevs - Rails dev specific

I recommend Joe Masilotti's project: RailsDevs. Very well-written and follows most of the Rails best practices. It also uses the Rails recommended front-end stack with Hotwire, Tailwind, etc.