sine

@sine@programming.dev

• ⁨Comment⁩ on ⁨What benefits do you get for being on-call? - programming.dev⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I get nothing. So after a while I told my bosses I would simply stop doing it, since the work to compensate us was still “in progress”. It helped the rest of the team get a free day per on call week, which I guess is something, but still not enough for me personally.

  I told them I wasn’t even sure it was legal in my country (Spain) which I guess they didn’t even discuss with legal, or legal didn’t even blink.

• ⁨Comment⁩ on ⁨The future of back-end development⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  To make things worse consulting companies live of cheap developers (like interns) and Microsoft and their platform makes things easier for anyone to code and deploy

  You’re saying this as it is a bad thing when it is not though; better defined APIs and ecosystems that lift cognitive load from you is always a good thing, there is no way to spin that as a negative.

  I think dotnet offers an incredibly good ecosystem for development, and I say this as someone that wants to jump ship and change the stack. What pains me the most about the stack is nothing technical. It’s not even the past predatory moves of microsoft, but the developer culture that surrounds it. Most dotnet devs I’ve worked with and talked to seem to be people that simply use visual studio as a window to the rest of the world. They tend to have very poor knowledge about almost everything with barely any fundamentals.

  Regarding your open source point I’m not sure I follow, I think everything we use at work is open source already. Everything is on github and there are quite a lot of discussions in how to steer the language and ecosystem being made in the wide open. It reminds me of the openjdk and python ecosystems.

• ⁨Comment⁩ on ⁨The future of back-end development⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Thousands of requests per minute can mean many things so maybe you’re referring to several hundred requests per minute. One of our services at work gets 300 requests/second which is ~18K requests per minute and it’s really not that much. We’re using pretty cheap cloud services. Even thrice the traffic is pretty much a slow walk for your average production-grade web framework.

  Web frameworks are built to support an insane amount of incoming requests, including node. The issue with node is the single threading and having to scale with worker threads AFAIK.