maxlapdev

Location: Montreal, Canada Remote: Yes, or hybrid in Montreal Willing to relocate: No Technologies: Ruby/Rails, PostgreSQL, Tailwind, Python, Dart/Flutter, Go, C++, AWS, Docker, Linux. Interested in learning Rust Résumé/CV: https://drive.google.com/file/d/1eNWRWWzNVbUFse3LhkDydAw9YdF... Email: maxhlap [at] gmail.com

Senior engineer with 12 years of experience in Ruby on Rails. I'm a strong generalist who quickly builds deep understanding of codebases, systems, and product context.

I care about quality, reliability, and maintainability, and I particularly enjoy refactoring existing code improve those aspects. I aim to solve immediate problems in ways that also support the broader product vision.

I consistently look for opportunities to reduce friction, improving the experience for both users and developers. For example, I built [activerecord_where_assoc](https://github.com/MaxLap/activerecord_where_assoc), a Ruby library with over 1.5 million downloads.

Open to full-time and part-time engagements.

  Location: Montreal, Canada
  Remote: Yes, or hybrid in Montreal
  Willing to relocate: No
  Technologies: Ruby/Rails, PostgreSQL, Tailwind, Python, Dart/Flutter, Go, Linux, AWS, Docker. Interested in learning Rust
  Email: maxhlap [at] gmail.com

Senior engineer with 12 years of experience in Ruby on Rails. I'm a strong generalist who quickly builds deep understanding of codebases, systems, and product context.

I care about quality, reliability, and maintainability, and I particularly enjoy refactoring existing code improve those aspects. I aim to solve immediate problems in ways that also support the broader product vision.

I consistently look for opportunities to reduce friction, improving the experience for both users and developers. For example, I built https://github.com/MaxLap/activerecord_where_assoc, a Ruby library with over 1.5 million downloads.

Open to full-time and part-time engagements.

Never said they were unsolvable. You asked for elaboration about pains of back then before lots of the tools most take for granted existed. You seem to think we are talking about massive problems, but it's more about a thousand papercuts.

It is very funny to me that the sibling comment calls this "a very broken setup" and for you "it doesn't sound like a big deal".

It's all about perspectives, or you really just never had to deal with it.

The happy path ain't a big deal. But think of the unhappy ones:

* What if a server gets rebooted (maybe it crashed) for any reason anywhere in the process. Maybe you lost internet while doing the update. Were you still dropping tarballs? Did the server get it? Did it start with the new version while the other servers are still on the old one?

* What about a broken build (maybe gem problem, maybe migration problem, may other). All your servers are on it, or only one? How do you revert (push an older tarball)

A lot more manual processes. Depends on the tool you had. Good tooling to handle this is more prevalent nowadays.

Note that you probably need 2 or 3 drivers per car to get a similar level of usage of the car that Waymo can do.

The one liner shouldn't have shortcircuiting since it uses the binary or |, not the boolean/logical or||.

For those unaware, Ruby blocks (and procs) are more flexible than anonymous functions as most language implement them. The article briefly goes over that, mentioning that lambda (regular anonymous functions) and procs (blocks) don't treat execute `return` the same way. There are also particularities with regard to next (continue) and break.

I made a post about the niceties of blocks: https://maxlap.dev/blog/2022/02/10/what-makes-ruby-blocks-gr...