joevandyk

You would add commands for ExtendBooking and CancelBooking and ChangeRoomType, I think?

I’ve found that you want to be super careful in application code about where you do updates and inserts when using AR.

Sprinkling calls to order.save! or order.update(foo: bar) in random places is a recipe for disaster.

That’s why I buy a new mouse after every 10 clicks. It’s pretty rare for them to fail on the 11th click.

Gusto uses a Rails monolith.

https://engineering.gusto.com describes some of their experiences with it.

Doing large queries on a Postgres standby had the potential to mess up the master, depending on configuration settings.

Because you acclimate over time to a certain temperature and humidities.

It’s a set of libraries that work great together, it’s pretty easy to learn, and lots of people know Rails.

Easier:

Save a file, see the result instantly.

In a browser, terminal, etc. Using live reload, auto test, Rails class reloading, and so on.

Most common error in my and teammates code (Ruby, JS) while actively working on it is code being edited is not consistent with the other code in the system.

Thinking I’m dealing with an Object A when I have object B.

Not realizing that nil is a valid thing to be returned from code that at first glance shouldn’t return nil.

Plus, accidentally writing super slow n+1 queries. And accidentally loading too much data.

I search for /def.*partial_name/ frequently when I can’t quite remember what a method is called in Ruby.

Using it 3/2 is probably enough...

What car do you recommend?

Any recommendations for how to start backpacking? Books, stores, guides, etc.

If anyone’s curious about the difference between Wagyu and Kobe, my company has this article on the subject midway down the page: https://www.crowdcow.com/article/akemika2t/japanese-a5-wagyu...

Not sure that comparing base memory usage on tiny programs that aren’t including any commonly used libraries is that useful.

10 of the large instances costs $5000 a month. Not insignificant. Smaller ones in my experience don’t run larger Rails apps very well.

We’ve been happy using buefy for our projects at Crowd Cow as well.

This integrates bulma css components into vue’s JavaScript framework, so you don’t need to write the html/JavaScript code that displays, say, a dialog prompt, you can just write `Dialog.alert(“hey”)`

What about mysql?

Sending an email can have a few different responsibilities:

Who is the email being sent to?

What is the content of the email?

What data does the email content and recipient depend on?

What are you tracking on the email?

How is the email visually formatted?

All those things might be in different apps as the logic gets more complicated.

I thought uuid-ossp was just a bunch of utilities around uuid parsing and generation. It shouldn’t need anything special from the OS.

https://www.postgresql.org/docs/9.4/uuid-ossp.html

I just had surgery on my l4 and l5 herniated discs after a year of impinged nerves. Highly recommend seeing if surgery is right for you, it was life changing for me.

Theft by deception. https://definitions.uslegal.com/t/theft-by-deception/

It’s difficult to show how much profit you had in Q2 2018, let’s say. Hence the fiction qualifier.

Total taxes are likely to be about $3500 a month or so.

He's referring to Go being more work to setup realtime web things, as opposed to Phoenix.

Does anyone miss or want type checking when working with Elixir? After working with Ruby to build large systems for so long, I'm missing a little bit of the safety that types provide. Typescript has been great.

Crowd Cow employee here. Animal welfare is incredibly important to us, and is the reason why many of us work here. We will look into ways of improving our messaging.

Branch off the release branch for fixes to it. Then merge back into release and develop branch.

Server is supposed to check authentication/authorization through some method.

If HTTP, that’s done via setting some information in the request headers, be it a cookie, or basic auth, or token auth, or similar.

CORS is done by the browser - to not allow certain requests to be made (In case you are accidentally executing malicious javascript code). The server tells the browser via the CORS headers which requests are ok to make.