←back to thread

Ask HN: Companies of one, what is your tech stack in 2024?

13 points ecmascript | 2 comments | 21 Oct 24 10:29 UTC | HN request time: 0.406s | source

Hello dear HNers. Each year for the last few years I have asked companies of one, meaning companies that consists of only one person of what tech stacks you use. Include as much and as little information as possible but the more the merrier! Feel free to link to your site or project for show case if you want.

What is your tech stack?

Why did you choose it?

Do you think your choices had any impact on your success or failure?

Here is the previous threads:

(2023) https://news.ycombinator.com/item?id=37467429

(2022) https://news.ycombinator.com/item?id=32960033

(2021) https://news.ycombinator.com/item?id=28299053

(2020) https://news.ycombinator.com/item?id=25465582

(2019) https://news.ycombinator.com/item?id=21024041

Thanks in advance!

1. crisopolis ◴[21 Oct 24 11:41 UTC] No.41903051[source]▶
I'm also in the process of building a product mostly in Elixir with minimal JavaScript. I just completed the WorkOS integration, now putting more effort into the actual product itself which is a extended workforce management SaaS.

What is your tech stack?

Backend: Phoenix

Frontend: Phoenix LiveView (with Preline UI)

Database: PostgreSQL (I want to use neon.tech soon for tenant db isolation)

Auth: WorkOS (for B2B SSO)

Cloud Provider: Fly.io (tbd)

Why did I choose this tech stack?

I've loved elixir for a few years but I've yet to build a functional SaaS with it yet. I've built one-off apps, and even stock algo bots. This time I'm going to try for something bigger which means I get to use Phoenix and LiveView to make a fast web app.

As for PostgreSQL we'll it's PostgreSQL and WorkOS seemed to be my biggest risk since I had no experience with it's platform or SSO OAuth2. However, WorkOS has tons of features that makes B2B SSO painless for me and potential customers. No real reason for fly.io yet.

Do you think your choices had any impact on your success or failure?

No success or failures yet.

replies(1): >>41904038 #
2. ecmascript ◴[21 Oct 24 13:37 UTC] No.41904038[source]▶
Very cool, I have had my eyes on liveview since it came out but since what I am building is a heavy user of maps and client side functionality that will utilize offline support, liveview brings unfortunately pretty little to my table and would be impractical.

Besides I can get the same functionality for most of the app with Server Sent Events and EventEmitter in node even if it is a tiny bit more of a hassle. But since the SSE is a better protocol than Websockets (especially with http3) you also get benefits you can't get with Liveview such as stuff working when customers have Proxies or firewalls that block stuff that is not http.

I really like Elixir as a language and I think Phoenix Liveview is a game-changer and I can't fathom why more people don't use it that doesn't have the same client side requirements as myself.