Ruby 2 Elixir @ruby2elixir

Community-driven initiative to switch from Ruby to Elixir ruby2elixir.github.io Joined November 2015

Tweets

1K
Followers

542
Following

488
Likes

795

Josh Price @joshprice

7 years ago

Need some #elixirlang in your org? Get in touch, we can help.

0 7 8 0 0

One of the big issues I’m struggling with right now is - how the heck am I going to fit everything I want to say about Scenic in a single talk! Am probably going to have to do a Youtube series or something afterwards to go deep. #myelixirstatus

5 4 49 0 0

Eric Oestrich @ericoestrich

7 years ago

In preparation for my @ElixirConf talk I made a video showcasing the cool multi-node stuff in ExVenture! This is killing a node and recovering without players noticing much at all #myelixirstatus youtube.com/watch?v=qzWH9v…

1 5 23 0 0

Joseph Rosztoczy @TehBrofessor

7 years ago

Nothing adds as consistent joy and confidence to my development like when stock test tooling and patterns from @elixirlang, @elixirphoenix, and Ecto run ~400 integration tests from DB to html/json/output in ~2 seconds. 😇

1 6 16 0 0

Shuaib X @shuaibafegbua

7 years ago

Hey people, write @elixirlang and save money

0 3 4 0 0

Austen Allred @Austen

7 years ago

Emailing people you don't know can be shockingly effective. There's an unwritten rule that you shouldn't do it, but if you actually provide value you can connect with almost anyone instantly and for free.

25 49 580 0 26

Elixir Tip @ElixirTip

7 years ago

How to Build a Back-Pressure Queuing System in Elixir with sbroker by Maximilian Störchle buff.ly/2KFWiH7

0 7 39 0 6

ElixirStatus @elixirstatus

7 years ago

Decoupled Modules with Elixir EventBus elixirstatus.com/=rCkc /cc @elixirweekly #elixirlang

0 4 17 0 1

ElixirStatus @elixirstatus

7 years ago

Practical Guide to Test Doubles in Elixir by @thiagoaraujos elixirstatus.com/=QCza /cc @elixirweekly #elixirlang

0 5 12 0 0

Elixir Tip @ElixirTip

7 years ago

Elixir v1.7.0-rc.0 has been released. buff.ly/2NaznWg

0 18 38 0 0

Download Image

ElixirStatus @elixirstatus

7 years ago

Gentle Introduction to GraphQL with Elixir and Phoenix elixirstatus.com/=vWxT /cc @elixirweekly #elixirlang

0 8 21 0 1

Jake Morrison @reachfh

7 years ago

Published a new blog post: cogini.com/blog/the-impac…

0 3 4 0 0

Indy Elixir @indyelixir

7 years ago

The recap and videos are up from last week's meetup! Lots to learn about Kafka and supervision, as well as property-based testing with StreamData: indyelixir.org/2018/07/03/rec…

0 1 3 0 0

ElixirBerlin @ElixirBerlin

7 years ago

Watch the Elixir documentary yourself and let the ppl know what you think ;) news.ycombinator.com/item?id=175138…

0 2 10 0 0

DDD Borat @[email protected] @DDD_Borat

7 years ago

Financial Times is now have useful piece of advice from DDD Borat

7 216 481 0 28

Download Image

Dave Gray @davegray

7 years ago

Google discovered that giving every employee a credit card and trusting them to follow policy on expenses, even with some bad actors, was cheaper than the enforcement and structures most companies use. How much do you waste due to low trust? Can you do the math for your company?

200 4K 10K 0 151

Erlang Solutions @ErlangSolutions

7 years ago

If you’ve tried to debug a running Erlang system, you probably tried tracing. Here's our tips: bit.ly/2xXUyrL

0 13 26 0 3

Download Image

Joe Armstrong @joeerl

7 years ago

Also ... the big ideas in Erlang and elixir are processes messages and links - not gen_servers, file structure, and dependency management- the distinguishing feature of Erlang/elixir is the light-weight concurrency and error handling- all the rest is hype.

Dave Thomas @pragdave

7 years ago

4 48 157 0 17

7 64 191 0 9

Dave Thomas @pragdave

7 years ago

My @empexco talk about rethinking the way we write Elixir is up. It's no more than a set of initial thoughts, but I really think there's something to them. I was just coming off a case of pneumonia, so sorry about the sniffs. youtu.be/6U7cLUygMeI

4 48 157 0 17

A. Sharif @sharifsbeat

7 years ago

Stop referring to people as "resources". * It's disrespectful * It show a lack of understanding of actual Software Development * Resources don't accumulate knowledge over time. * Resources can't form teams. * Resources can't collaborate. What else?