I maintain an open-source project that could use some new contributors. We have bounties ranging from $50 to $100. Would that be attractive in this platform?
you can use Algora.io (it’s open source) to cover 120+ countries for the bounty payout - it would be a fantastic showcase on our website (founder here)
So that open source contribution can be part of your CV when looking for a job, right?
I guess what I'm trying to say is that employees should try to get open source contributions as part of their job. Either by open sourcing a component or by contributing to projects on which the company depends.
28 years, 10 jobs, including one at BigTech. I’ve never written one line of code that I haven’t been paid for since a year before graduating from college - in 1995.
with that much experience you should consider volunteering you services to good causes, no money, but you’ll feel good. I am similar in years and have written probably six-digit lines of code I haven’t been paid for.
I live a very commitment free life. Outside of work and my wife.
Our home in Florida easily converts to a short term rental (a unit in a condotel - https://www.investopedia.com/terms/c/condotel.asp) when we leave for longer stints. We did the digital nomad thing for a year around the US and in the next couple of years, we plan to alternate between Panama City Panama and San Jose Costa Rica during the winter in the US - their dry season.
During the summer, we might spend a month back where are friends and family are in GA.
The benefit of remote work. We have experience living out of two suitcases and picking up and flying random places and staying for a few weeks.
This was my first impression too but I wasn't sure it covered the OPs convention over configuration stipulation.
Elixir/Phoenix is far and away my favorite framework to build with, but it does leave some things up to the user in a way that Rails doesn't, eg: there is no automatic `class name -> db table` mapping, or automatically inferring what partial or form names to use by a variables name.
In my mind, this is not a downside and there are still idiomatic ways to write Phoenix code, but just to outline some philosophical differences I guess. In the end I much prefer it because everything's a bit more explicit and flexible when I want it.
I think Phoenix also expects read documentation around OTP if you want to really achieve high leverage. This is worth it, and you can sort of drip feed yourself by starting with Phoenix, recognising that Phoenix primitives [sic] are actually Elixir primitives are actually just OTP primitives and you end up with some pretty good examples of how OTP works in a system you're already familiar with.
Elixir + Phoenix is amazing. It's one self-contained stack. Just Elixir processes (and Postgres) which takes care of everything other ecosystems farm out to extra services. Background jobs, real-time channels, and even hot-code deployments run natively within the same BEAM runtime.
Working with this with a small team with one simple stack is a breath of fresh air in today's world.
I’ve always heard awesome things about elixir/beam but I only have so much love in my heart for languages without good static types. Right now that love goes to clojure!
I’ve been hearing some buzz about static types landing in elixir, and it’s definitely piquing my interest. This comment of yours has fully sold me though!
having used both, elixir feels a lot like clojure semantics with a ruby like syntax. the big advantage of elixir is the erlang vm. if you want a vm that heavily prioritizes parallelism and network programming, give elixir a try. otherise, clojure is perfectly adequate.
I've been slowly / occasionally dipping my feet into Elixir / Phoenix dev over the past year or two, building an app idea that's been floating around in my head for a while. It's a bit of a steep learning curve for me, coming mainly from Python land (Django / Flask / FastAPI); I understand that it's designed to be a gentler learning curve for those coming from Ruby / Rails land. Phoenix is also a lot less mature / less feature-complete / less thoroughly-documented (than I had hoped, and) than Django / Rails (many of my Phoenix questions I've only found answers for in the forums, rather than in the official docs). Nevertheless, I agree, BEAM / Elixir / Phoenix is awesome, I'm hoping to get into it more in future.
I had the opposite experience coming from Django/Flask to Elixir/Phoenix. I found it very comfortable and that there were many similar patterns at the framework level. Now, LiveView is a bit of a different story but basic Phoenix routing and views seem quite similar to Django routing and views. Ecto's model schemas have a decent amount of overlap with Django's model objects.
Was it the LiveView stuff that felt foreign? I'd agree there's a learning curve there as someone coming from Django.
Built my startup on phoenix and I can vouch that it was 100% the right decision. code is easy to modify/reason about. Performance smokes rails by a wide margin and its websocket support is simply amazing. There's a few really great libraries for it that just let you scale very efficiently without much effort.
A lot of OSS companies are currently hiring. Contribute to their codebase to stand out, get experience, network & improve your resume. Some also share feature bounties on GitHub (https://algora.io) so you can even make money in the process.
I know dozens of engineers who landed jobs within a few months by actively contributing to OSS.
I run a bounties platform (https://algora.io) and I've seen people who create bounties try to use some AI like Devin to solve them (@seveibar livestreamed trying it) just for fun and in all cases AI failed to solve the bounties.
A Rust project that rewarded 300+ bounties ($37k) is now building an AI coding agent with the aim to solve bounties on Algora - it's an interesting benchmark I guess.
Curious myself what the next years might look like, but from everything I've seen so far we're definitely not there yet.
