fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

#elixir

34 posts27 participants5 posts today

I'm available for development work. I have 20 years of Rails development experience, building more apps than I can remember (wrote couple of books too) - usually solo or leading a small team. A bunch of Elixir Phoenix apps in production too.

I'm in UTC+9 but I work with teams in US, UK & Oz - I'm flexible and always make it work well. Folks seem to like working with me ☺️

More about me at xenocode.co.jp
Always very happy to chat about any ideas or projects!
#fedihire #ruby #elixir

xenocode.co.jpXenoCode - From Ideas to Products, QuicklyXenoCode is a product studio that helps turn your ideas into scalable, production-ready applications using Ruby on Rails and Elixir Phoenix.

The man whose introduction outstays it's welcome because his name is so long it falls out of the banner. The man who called me a sexy viking the first time we spoke. Author, consultant and incredibly enthusiastic he is half of BEAMOps and I look forward to hearing what they want to share.

goatmire.com/#speakers

Continued thread

I've had a thought: if I have an update function that modifies and optimizes a data structure in one branch, but doesn't need to modify it in another branch, should the second branch still apply the optimization?

The trade-off is returning a reference to the unmodified data structure vs building a semantically-equivalent structure that will have faster lookups on subsequent queries.