Live data from Hacker News

Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

sleepeasy.app

61–70 of 142 posts

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#61
post #23

Earlier quoted context omitted.

Maybe it was true 6 years ago, but I'm currently playing with Elixir/Phoenix and I feel very productive, Phoenix is well design and adding new functionalities is not that hard and the code is easy to debug. On the other side, Elixir and Erlang are not that popular and every time I talk about it to other developers, they may have heard of it but can't talk about it, so it's probably not that easy to find devs for a st…

What is the best freely accessible Phoenix tutorial? I recently searched a bit, tried a bit, but then ran into a problem, that should not have happened according to the tutorial. I guess the tutorial was outdated (got the RoR vibes from years ago). I could not fix it, due to the lack of understanding of how Phoenix works and what it wants me to do. Gave up again (for the second time) on learning Phoenix. Is there an…

I would get it from the phoenix's beak honestly - https://hexdocs.pm/phoenix/overview.html

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#62
post #28

i have to be honest: as a lover of the language, and with due respect to the author, i’m really tired of these “why i picked elixir” takes extolling the same virtues (or some subset thereof) we’ve seen written up in darn near every introductory article on elixir for the last five or six years. it’s not that i think they’re wrong, at all. it’s just that they add nothing new to the conversation, they’re superficial, an…

Long story short from a business perspective - good luck logistically scaling a dev team from 2 founders to 100 devs as quickly as your app does. Elixir devs are hard to find and are expensive.

I would be interested, if I could maybe learn from a more experienced Elixir dev on the job for a month or so (even for temporarily reduced pay while I am catching up). I am quite quick at picking up languages and have broad experience in many languages and their concepts. I imagine there are more people like me out there, who would be happy to learn something new on the job and a nice language like Elixir at that.

I don't think devs and talents are too hard to find, if you are willing to look and be flexible.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#63

Earlier quoted context omitted.

That's micro-shortsightedness. Lots of tools even OS utilities are being rewritten in a "better" language. It could be quite beneficial from a business perspective too if you're spending more time fixing issues than addressing new requirements.

That really depends though. Part of the time you are right but there are legitimate businesses settings where not shipping by the end of next week can mean missing out on much-needed $50K or so revenue.

Often a feature pressure of "ship next week" is due to bad management and planning though. Often engineers already foresaw similar needs and were told no before. Then suddenly it is urgent.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#64
post #13

Disclaimer: Elixir is extremely productive, Phoenix is outstanding, the community is world-class, and as a result of the Erlang VM / OTP / Beam you can remove whole parts of your traditional webstack. If you haven't tried it I cannot recommend it enough. But! As a long-time Elixir Developer who has gladly used it to bootstrap many applications and companies, I have to say I think this article is actively harmful to t…

Endorse 100%.

The lack of discussion about LiveView tradeoffs is one of the few things I actively dislike about the Elixir community: and I love elixir and reach for it for almost everything.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#65

I love Elixir, but I have to disagree with the principal aspect of this post. As an engineering leader what I look for when picking tooling for SaaS which essentially boils down to two things: 1) How expensive and difficult will it be to scale the Org. 2) How difficult will it be to implement product features. I attempted an Elixir startup and found that it failed at both. The language was lovely to use and very smar…

You make some good points that I don't want to detract from -- but isn't setting the bar for finding a dev at 'built and scaled a unicorn level app' a little high? Are there really that many of those

Sorry, I didn't mean built from scratch and scaled it all the way to unicorn. Rather worked on a unicorn scale app in some capacity. Even if you join a late stage startup and didn't build the foundation, the experience you get from how the org runs is pretty valuable.

Much easier to find a engineer who engaged with a large Python SaaS app than an Elixir engineer.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#66
post #48

Earlier quoted context omitted.

Did the parent comment get updated? It doesn't track to what you've put here.

No it hasn't. As I stated, I was only reacting to his "not that easy to find Elixir devs for a startup" is all.

It sounds like you just dont want to work at a startup? What does that have to do with elixir?

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#67

Earlier quoted context omitted.

That really depends though. Part of the time you are right but there are legitimate businesses settings where not shipping by the end of next week can mean missing out on much-needed $50K or so revenue.

Often a feature pressure of "ship next week" is due to bad management and planning though. Often engineers already foresaw similar needs and were told no before. Then suddenly it is urgent.

I agree and that's why I no longer want to work for startups or any company with "urgency" culture.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#68
post #66

Earlier quoted context omitted.

No it hasn't. As I stated, I was only reacting to his "not that easy to find Elixir devs for a startup" is all.

It sounds like you just dont want to work at a startup? What does that have to do with elixir?

Yes I don't want to work for a startup and I stated as much didn't I? ;)

What it has to do with Elixir is that Elixir does not scale well with a number of programmers, and many startups go through periods of explosive growth of personnel. With Elixir that very rarely works well, 99% of the time IMO it does not. Adding more people does not increase productivity, it hurts it even.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#69

Earlier quoted context omitted.

That's micro-shortsightedness. Lots of tools even OS utilities are being rewritten in a "better" language. It could be quite beneficial from a business perspective too if you're spending more time fixing issues than addressing new requirements.

That really depends though. Part of the time you are right but there are legitimate businesses settings where not shipping by the end of next week can mean missing out on much-needed $50K or so revenue.

Ultimately it is yet another optimization problem. You have fixed dev time, a budget and some deadlines. If possible, try rewriting a component and measure the effort and benefits. We had PoC with deep rooted data issues. We knew throwing it away would set us back by a year but it just kept getting uglier by the day. We added a thin data validation API around it which started catching a good chunk of the data issues and let us deploy the PoC. We're now rewriting a new core with built in data validation and tons of performance and reliability improvements.

Re: Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024

#70

Earlier quoted context omitted.

That really depends though. Part of the time you are right but there are legitimate businesses settings where not shipping by the end of next week can mean missing out on much-needed $50K or so revenue.

Ultimately it is yet another optimization problem. You have fixed dev time, a budget and some deadlines. If possible, try rewriting a component and measure the effort and benefits. We had PoC with deep rooted data issues. We knew throwing it away would set us back by a year but it just kept getting uglier by the day. We added a thin data validation API around it which started catching a good chunk of the data issues…

Well that is a good way to go about it. Direct frontal assault against legacy problem indeed very rarely works.
Post reply on HN