Hacker Newsnew | past | comments | ask | show | jobs | submit | mstibbard's commentslogin

This thread on Elixir Forum is a good read if you are considering building agents with Elixir. Jido's author weighs in also.

https://elixirforum.com/t/is-anyone-working-on-ai-agents-in-...


This appears to be true remote (I.e., globally remote) as long as you are willing/able to have 4 hours overlap with US working hours per day


I’d really like to hear more about this



OpenAPI predates OpenAI by quite some time. OpenAI has adopted usage of OpenAPI.

I do find myself accidentally saying one and meaning the other, in both directions too!


Actually only a month! I just looked it up and was surprised myself.


According to Wikipedia[1] it looks like the rebranding effort from Swagger -> OpenAPI was in November 2015, but the OpenAPI Specification was only officially renamed on 1st January 2016. OpenAI was founded on 10th December 2015. So it depends how pedantic we are being -- technically on branding, OpenAI predates OpenAPI by 21 days. In terms of the spec itself (as in, the thing they adopted), Swagger v1 was released August 2011.

[1] https://en.wikipedia.org/wiki/OpenAPI_Specification


Worry not, this is Hacker News. Pedantry is more valuable as currency than H100s here.



I think that was their point - the rest of the world solved this long ago, it is just the USA that lagged


I could see that. "Anybody from any country" could have included the US or meant "any other country."

But if it did include the US, it would have the assumption that Americans are unaware how terrible our payment systems are (generally untrue I think) or unaware that other countries have better systems (may or may not be generally true).


I would estimate a senior staff engineer to be an L5 or L6 at Google


L6 is staff, senior staff is L7.


Right but a Google L6 is a was probably a PE at the last Fortune 500 they worked for.


If you don't already know a tech stack, I'd recommend Elixir & Phoenix (incl. LiveView).

If you DO already know a tech stack then use that one!


Forcing consistent language, runtime, tooling etc is generally a good thing as it reduces ongoing operational burden as well as some retention & hiring dilemmas.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: