This article is a high-level overview of design patterns that are commonly used in Ruby on Rails applications
How would you feel if you could no longer use [product]?
- Very disappointed
- Somewhat disappointed
- Not disappointed (it isn’t really that useful)
- N/A – I no longer use [product]
If you find that over 40% of your users are saying that they would be “very disappointed” without your product, there is a great chance you can build sustainable, scalable customer acquisition growth on this “must have” product. This 40% benchmark was determined by comparing results across 100s startups.
Use gateway classes to organize external API integrations and establish a clearer separation of concerns.
It’s worth noting that the gateway pattern is often applied without using the term gateway. The term service is also popular. I prefer the term gateway because service is overloaded in the developer community and can lead to confusion.
Where service is vague, the term gateway more clearly states its purpose: it defines a boundary between the app and an external system.
It’s based on lessons learned from researching and creating Large Language Model (LLM) prompts for production use cases. It covers the history around LLMs as well as strategies, guidelines, and safety recommendations for working with and building programmatic systems on top of large language models, like OpenAI’s GPT-4
I’ve come to believe it’s an impossible title. You’re either CEO, or you’re Founder. You can’t hold both full-time jobs.
Because a Founder’s job is injecting risk into the business. It’s flooding it with new ideas, stuff that seems hard to do, ideas that no one else would dare try, placing the kinds of bets that only someone who started the damn thing would be willing to wager. A Founders’ job is basically to stay in business by almost always putting it out of business.
A CEO’s job? Just about the opposite. It’s reducing risk, executing diligently to achieve obvious goals, staying in business at all costs. It’s primarily about about being conservative, keeping the company’s collective cool, and not letting things get out of hand.
This is a quick guide to a workaround to get your the development branch of your Rails app running via SSL and under your production URL.
It sits on top of basic Docker, and harvests all the benefits you get from isolated containers with a sliver of the complexity associated with most other solutions. Instead of sending the deployment pipeline off to servers in the cloud, it runs entirely on your own machine. Just like Capistrano did.
We transmogrify Docker containers into lightweight micro-VMs and run them on our own hardware in racks around the world, so your apps can run close to your users
Neither a borrower nor a lender be, for loan oft loses both itself and friend, and borrowing dulls the edge of husbandry…— William Shakespeare, Hamlet
I’m not here to teach anyone anything, I’m just here to show people what winning looks like …— Jason Williams, Parabolic Guy
There is nothing more permanent then a temporary fix that works, it is only temporary if it fails…— Unknown