Hacker News Reader

Comment by richardwhiuk | Hacker News Reader

How about going forward by not focusing on using the latest JavaScript frontend, but fixing the backend issues you clearly have?

View on HN

Hey Richard, we're actively working on fixing issues on the backend of gitlab.com: https://gitlab.com/gitlab-com/infrastructure/issues/947

Much of this work isn't front-end work and we have a separate team taking care of it.

Too soon? low blow? I would imagine they have different teams for the fronted and their backend datastore, and can do both at the same time.

Thanks! We are working on the backend and the frontend at the same time. We have two separate teams.

Saying thanks to the troll... I admire your tact but just want comments like his to die a silent death.

Well that's kind.

I wasn't trolling - I'm serious. If you are operations are in this bad a state, is investing a bunch of money in changing JavaScript frameworks on the frontend really the best use of your capital resource.

Different teams dude

Same company, you just have to choose where to spend your resource, and from the analysis it looks like the operations and management side isn't where GitLab chooses to spend it's money.

So you think they should pull their front-end dev team to do operations instead? I doubt that would go down so well.

No, I think they should hire more people to do operations.

Sure. They probably will. Why should that slow down their front end dev? Or are you suggesting firing some of their front end developers to fund the ops guys?

Reply on news.ycombinator.com