For serverless things, websites, prototypes, web apps, time sensitive stuff:
Next.js (react)
typescript
jest
tachyons (sometimes tailwind if I have a tougher design)
faunadb
jest
For web apps, monoliths, things that need extensive databases and models, more security and control, or apps I won't be maintaining often:
Ruby
Roda
Sequel ORM
tachyons still
stimulus or vanilla or preact depending upon frontend complexity
MiniTest
Postgres
API Only:
Ruby / Roda (if I'm working with sql databases)
Node + typescript (if I'm working with NoSql ie Fauna or Mongo)
Go (still not super comfortable with it but getting there to replace node and typescript)
In general I'm most comfortable with Javascript, however the build processes and configuration issues can be a nightmare. Working with sequel based databases with Ruby is leaps and bounds ahead of Javascript so I stick to that but have moved away from rails in favor of Roda and the Sequel ORM these days.
I enjoy the security of typescript especially when working with lots of external data sources. It can make your head spin trying to remember the data structures of a headless CMS, plus a database, plus a myriad of other services so typescript helps there. However, I find that typescript / javascript apps are best if you are working on them every day. If you build something then come back a few months later you may spend the next day debugging the build (babel, webpack, typescript...), the ecosystem in JS is really what gets me down.
Recently I'm getting more into Go for back end work for first class types support and a nice simple language with amazing speed. That being said the front end tooling and templating stuff that Go offers is a little lackluster so if working on a monolith I'd say Go may not be the best pick and is more of an amazing API language.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For serverless things, websites, prototypes, web apps, time sensitive stuff:
For web apps, monoliths, things that need extensive databases and models, more security and control, or apps I won't be maintaining often:
API Only:
In general I'm most comfortable with Javascript, however the build processes and configuration issues can be a nightmare. Working with sequel based databases with Ruby is leaps and bounds ahead of Javascript so I stick to that but have moved away from rails in favor of Roda and the Sequel ORM these days.
I enjoy the security of typescript especially when working with lots of external data sources. It can make your head spin trying to remember the data structures of a headless CMS, plus a database, plus a myriad of other services so typescript helps there. However, I find that typescript / javascript apps are best if you are working on them every day. If you build something then come back a few months later you may spend the next day debugging the build (babel, webpack, typescript...), the ecosystem in JS is really what gets me down.
Recently I'm getting more into Go for back end work for first class types support and a nice simple language with amazing speed. That being said the front end tooling and templating stuff that Go offers is a little lackluster so if working on a monolith I'd say Go may not be the best pick and is more of an amazing API language.