About an hour before I checked in I got a message from Booking.com saying my reservation had been canceled. I called them and they said the hotel had canceled the reservation. They attempted to find another hotel upon request but there wasn’t one that would fit our group within 45 minutes of the convention center (the original was a block away).

Without many options, I showed up to the hotel to attempt to check in anyway. They told me Booking.com had canceled it several weeks prior. I denied any knowledge of the reservation being canceled and we got our room with little issue.

I’m not sure what was going on, but I’ve never used them since.

Also, likes commuting? You can listen to your podcast anywhere.

Since I have to watch out for it, I've noticed it's becoming more and more common as a sweetener.

Comments URL: https://news.ycombinator.com/item?id=44605261

Points: 3

# Comments: 0

  - Am I free from feeling frustrated/stressed at work once a week or more?
  - Am I free from work stress/anxieties outside of work hours?
  - Am I keeping up with my hobbies?
  - Do I feel respected and valued, with the ability to influence my work environment? 
  - Do I feel proud of my work and confident discussing my job with others?
  - Am I learning/growing?
  - Am I excited about the company's direction and secure in its stability?
  - Do I feel like my job is secure?

Friends have challenged this, asking if I can't just feel when it's time to move on, which I can, but I've found this leads to me being more thoughtful and proactive about it.

- 6 years

- 3 years -> triggered by matrix

- 3 years -> until acquisition

- 5 months -> acquiring company, triggered by matrix

- 2 years, on-going

It helps me because I have a habit of fixating on the team’s mission and ignoring my own happiness, so the monthly check-in keeps me from staying somewhere longer than I should.

I normally get bored of JRPGs quickly but the game systems, music, artwork and story have all been stellar.

top-down

- makes decisions based on intuition, rationalizes them afterwards if necessary

- quick reactions to new information

- more flexible (sometimes inconsistent) beliefs

- faster to adopt new ideas that align with their feelings, but also more resistant to ideas that they don't like

bottom-up

- systems based reasoning

- builds internal frameworks around ideas

- consistency is paramount

- slower reactions to new information

- can be seen to have more "unique" thoughts or insights through drawing parallels in their internally developed frameworks

- can be more rigid when it comes to new ideas, but not stubborn. it either fits into their frameworks or it doesn't

I'd say it's a spectrum, but people tend to significantly favor one way or another in my experience. I feel like top-down thinkers would be much more likely to be story-based, and bottom-up fact-based.

You may have. I haven't met anyone who has had any effects other than feeling mildly sick for a day or two afterwards. That's the thing about anecdotal evidence.

https://www.youtube.com/watch?v=E-w0R-leDMc - starts about halfway through.

- Auth, sessions, secure cookie handling, etc.

- DB interaction

- View templates, layouts, etc.

- SPA-like interactivity

- Form handling & validation

- File uploads

- Asset handling

- Emails

- Background jobs

- Security (CSRF, XSS, SQL injection, etc.)

- Logging

- Internationalization

- Testing

- Real-time functionality

With Node/Express, you're either searching for other people's libraries to use and integrate, which aren't guaranteed to synergize, or writing it yourself. You have all of that baked into Rails, tucked away neatly so you only have to write and focus on what matters. You also have an opinionated architecture so you know exactly where all the custom business logic should go.

I think if you have extremely simple requirements, or you're at a stage where you want to learn all these things by doing it yourself, it would make sense not to use Rails. But if you want to focus on delivering value ASAP, Rails (or similar frameworks like Django) are for sure the way to go.

Claude's been far and away superior on coding tasks. What have you been testing for?

I have a few observations:

- I vastly prefer Cursor's Copilot++ UX for autocomplete compared to GitHub's in VSCode, which I used until a few months ago.

- The Composer multi-file editor (cmd+i) is easily its most powerful feature and what I use most often, even when I'm working on single files. It just works better for some reason.

- It's far more effective working in popular stacks, eg. Typescript/NextJS etc. It's rarely a time-saver when working in Elixir, for example.

- In a similar vein, the less 'conventional' your task or code is, the less useful it becomes.

- As the context increases, it gets noticeably less useful. I often find myself having to plan what context I want to feed it and resetting context often.

- It's very effective at 'translation' tasks, eg. converting a schema from one format to another. It's much less effective at generating complex business logic.

- I only find it useful to generate code I confidently know how to write myself already. Otherwise, it doesn't save me time. The times I've been tempted, it's almost always bitten me.

So, you can either disagree with the books/studies based on your anecdotal experiences or specific circumstances, in which case the rest of the article isn't relevant to you (and unless you consider yourself an 'elite', it probably never was). Or you can understand that you may have a flawed understanding of the relationship between remote work and productivity, leading to your current opinion on the matter. Or you could have another motive, which may or may not be one of the reasons presented in the article. Which one sounds the most likely to you?