Excited for the final RailsConf (my third). My whole team will be there, God-willing, celebrating almost two decades of RailsConf—and hoping to find another teammate or two.
(First hire I made at JLG was a “Scholar” I met at RailsConf 2024.)
Excited for the final RailsConf (my third). My whole team will be there, God-willing, celebrating almost two decades of RailsConf—and hoping to find another teammate or two.
(First hire I made at JLG was a “Scholar” I met at RailsConf 2024.)
@jzig Thanks, I wrote you a book on LinkedIn, but for reference here JLG has ten paid holidays/year and we offer 3 weeks PTO.
The Rails team works on internal and client-facing projects, and as the client-facing apps scale up, we will need to setup some monitoring and resiliency stuff so that pager duty is no big deal. (I.e., this is new and we haven't crossed this bridge here, but I'm opposed to heroism-as-a-strategy.) Otherwise there's no expectation of availability on weekends/late/early.
@ryanfb A wide range of ~75k-195k since we're open to all experience levels. That's for US-based FTE, comes with group health insurance partly paid by employer, PTO, etc..
Outside US also fine so long as there's useful working hours overlap, salary subject to market adjustment and negotiation.
Obviously this is a fully remote position.
Do you know any good Rails or JS devs (any experience level) interested in working on a very small team building new apps to make the litigation process smoother for people injured by big companies?
Job post is for senior Rails position, but we're open to all experience levels, and I'm looking for strength on the front end, so I'm considering JS devs as well.
Mention my handle in your application to make sure I see it!
https://jobs.gorails.com/jobs/senior-software-engineer-873c1ce9
@Scottw I went digging in the Ruby LSP extension source code, and they have explicit callouts to enable highlighting for quite a few heredoc tags, including HAML and Slim (and SQL, HTML, CSS...), but no ERB. AFAICT at least some of these are not supplied directly by Ruby LSP.
Next step would be to try forking the Ruby LSP extension (and follow a guide for writing and installing one's own extension, which I've never done) and see if just adding a comparable callout for ERB solved it.