HN user

Olphs

127 karma
Posts1
Comments41
View on HN

Seems interesting

For Coda this makes sense to kind of kickstart/boost their AI efforts.

But not immediately clear to me why Grammarly is interested in building their own doc builder tool?

It does, if the company has any branch/office/agent or similar in the EU, or if it targets their services/website to EU residents.

What "targets" means exactly in this case I'm not sure, but given that YC actively markets to EU based companies too, I would think that GDPR applies to them as well.

From employee perspective I have been mostly happy with these services.

There has been some minor issues and extra hazzle, but nothing major, and the 2-3x salary compared to local levels certainly helps offset any small issues

Employer wanting to terminate an employee or employer going bankrupt, while maybe not common certainly happens, and it is built-in to their business model. Most of these services do require deposit that covers at least 1-2 months of salary + costs (up to even 6 months of salary), which is meant for these type of cases.

That being said, I do think many of these services are at least partly skirting the laws, or at least threading on a very thin line. As far as I know, most especially EU jurisdictions don't really have exact laws for EOR specifically. In general labor laws do apply though, of which these services sometimes have quite interesting/creative interpretations. But as long as things go well and everyone is happy, I don't think anyone really cares.

Yeah most companies simply don't care, and/or they don't have the processes the address issues like that

They also likely get dozens of similarly looking messages each day from "developing country" "pentesters" for irrelevant issues, so your message could have also ended up with similar looking "spam"

9/11 in Realtime 3 years ago

Hmm the times are somehow all messed up, current time shows 4:xx PM, the timeline shows things happening from 2:xx AM, and the controls show 8:xx AM

Do you think it's good idea to migrate from monolith to microservices before scaling the team?

We are essentially doing this right now, I personally don't think the teams are yet large enough to warrant this migration, but leadership says that we can't scale further before we have microservices. Imo most of the problems could be solved with increased testing and knowledge about the system. The tech also could definitely still scale with just by boosting the hardware and occasional performance passes on slow endpoints/queries.

25 million in profit with 22 million in turnover last year. Not sure how that works exactly, but seems like money wasn't an issue at least.

This is all publicly available since the company behind it, is based in Finland

Small Teams 4 years ago

It's just couple million a year business, so nothing that extraordinary

dedicated "production support" team

That's interesting, so if some bug pops up during the weekend they will just revert back? And then that bug gets handled later. Or is there also so rigorous QA process that bugs rarely happen, and it's more like infra issues that the "product support" team can handle on their own?

The interesting part is that I think on-call is not only about infra issues etc., but could also be bugs in the application or some other weird behavior, which I'm assuming the "production support" wouldn't know how to handle. Maybe there is some huge amount of process to handle all that I'm just oblivious of, never having heard of this before?