hschne

It's quite possible that the expected value for most companies over, say 10 years, is overall higher. I obviously have no data, call it a hunch

We just don't hear enough about companies growing steadily and profitably over the years, but over report on the unicorns and smash hits.

Either you focus on creating a great product that customers love. As a consequence, you'll hopefully make some money.

Or you focus on making a truckload of money as quick as possible, and building a product is merely a means to an end.

As OP said, there's far too few companies choosing the first approach, and far too many choosing the second one.

It's surprisingly simple. You can check out the relevant source here: https://github.com/rails/solid_queue/blob/main/lib%2Fsolid_q...

Happy to answer any questions.

Different tech stack and slightly different features though. Super cool to see more other tools in the space!

https://datadeaddrop.com/

Not sure what you mean.

https://bundler.io/guides/git.html

I'm looking forward to using some of the developer experience stuff, such as default RuboCop or default GH actions for new apps. Not sure if it's everyone's cup of tea though.

So instead I used a third party authentication service, store some data in JSON files, and also threw up a lamda gateway to store some more data in Google Sheets?

It's not relevant to the bug hunt, but I'm genuinely intrigued. Is this approach considered easier to work with than using a regular ol' DB?

Goes from literally no configuration management (just SSH into the box to install your stuff) to Ansible and then to Docker and k8s. Quite the Journey.

I think a lot of people here can relate, I certainly can.

I'm on an older phone though and your landing Page murders it. Animations stutter and scrolling is pretty janky. Not sure I'd that's an issue with the components or something else?

Not an easy read by any means, but it's core hypothesis is spot on IMO: Google (and others) core business is aggregating and processing as much user data as possible. Every product they create and every decision they make aims to increase or protect their access to data.

Good luck.

I thought Sitepress looks interesting, as its supposed to integrate with Rails. Have you given that one a try?

https://sitepress.cc/

My main issue is that if you want to build anything these days it kinda has to look at least decent. All depends on your customers and project, but generally expectations towards UI are high these days.

I'm trying something similar where I style my first prototype - but I'm only allowed to use black and white. Forces me to consider layout, but helps avoid the design rabbit-hole.

I think the language is fine, but the thing that really makes me stick with Ruby is the ecosystem and the culture it fosters. The article also makes that point.

I have yet to see a programming community (around a language) that is as encouraging and nice as the one around Ruby.

- Useful to know when you work with APIs (as the article outlines).

- Very useful when working with background jobs. You're not gonna have a good time if those aren't idempotent.

- Good to know for interviews. I was asked to explain idempotency a handful of times, weird as that is.

I wonder how anyone goes about planning such an enormous effort.

I almost stopped reading right there because it so violently disagrees with my experience.

I'm glad I made it through the article though, as it makes some good points. Ask for different feedback based on what makes sense at this point in time. Manage expectations . Alright.

The thing is, giving good, constructive feedback is hard. I don't think a lot of people are good at it, for various reasons. So no, even if you ask for feedback, chances you'll be getting good feedback are low.

If there's a way make that more likely I haven't found it yet.

I don't have a use for Grimoire - not willing to change my bookmark workflow at this point - but you can be sure I'll remember it just based on that.

Both Games get updates every couple of months. Which is perfect, because you get something new every time you pick one of them up again.

In all seriousness though, I'd love to know more about Shopify's infrastructure. Pretty marvelous how they handle such an enormous influx of load.