Remote: Yes
Willing to relocate: No
Technologies: Ruby on Rails, React, Tailwind, PostgreSQL, MySQL, TypeScript, Elasticsearch, Kafka, and more
Email: mads.ohm@gmail.com
Senior engineer with more than 10 years of experience with Ruby on Rails. I'm currently looking for a full-time contract, but am open to part-time for the right company.
Location: Denmark
Remote: Yes, exclusively
Willing to relocate: No
Technologies: Ruby, Rails, Hotwire, Stimulus, Tailwind, React, JavaScript, TypeScript, PostgreSQL
Résumé/CV: https://linkedin.com/in/madsohm/
Email: mads.ohm@gmail.com
Hello, I'm Mads. I have more than a decade experience with Ruby on Rails doing both frontend and backend.It's like the Monty Hall problem, switching is always the better solution.
Location: Denmark
Remote: Yes
Willing to relocate: No
Technologies: Ruby, Rails, React, Tailwind, Typescript, Javascript, MySQL,
PostgreSQL, Elasticsearch, GraphQL
Résumé/CV: https://linkedin.com/in/madsohm
Email: mads.ohm at gmail dot com
I hold a PhD in computer science. I have more than 10 years of experience with Ruby and Ruby on Rails. I've helped build and scale frontends, backends, and APIs in general. I'm ready for whatever you throw at me - and can easily learn new technologies and languages, if needed.https://lemonwatcher.com/baby-names-1.png
https://lemonwatcher.com/baby-names-2.png
https://lemonwatcher.com/baby-names-3.png
For the second kid, I created an iOS app using React Native (https://i.imgur.com/aaTqXAY_d.webp?maxwidth=760&fidelity=gra...) where you could swipe names Tinder-style.
We didn't use the apps to find _the_ names, but to get a narrowed down list we could pick from. The projects were fun and educational.
Location: Denmark
Remote: Exclusively
Willing to relocate: No
Technologies: Ruby, Rails, React, TypeScript, Elasticsearch
Résumé/CV: https://mads.ohmbrix.dk/files/cv.pdf
Email: mads.ohm@gmail.com
PhD in computer science. More than a decade experience with full-stack development using Ruby on Rails. Ex-Elastic, ex-Shopify. Looking for senior/staff engineer positions.Seems wrongheaded to me; that's the same reason Elm wanted you to write arrays like this:
[item1
,item2
,item3
,item4
]
instead of a sane way. It means adding or removing an element only changes one line in the diff!Who cares? It's not hard to understand what's happening in a diff that makes this kind of change. You want the code to be easy to read, not easy to diff.
You could also easily base your diff algorithm on a lexer for the language rather than a lexer for ascii, in which case changing the amount of whitespace would register as "not a change".
[
item1,
item2,
item3,
item4,
]