Live data from Hacker News

Every software system used at Gitlab

about.gitlab.com

111–120 of 123 posts

Re: Every software system used at Gitlab

#111
post #43
post #31

Gitlab has been pretty great so far, but the code review tooling is so poor I think I need to look elsewhere. The pull request pages take forever to load, they can't handle pull requests with over 800 lines well at all. It will collapse files with over 100-200 lines of changes for seemingly no reason (hiding the comments within them). You can't ignore whitespace in diffs, and the comments disappear from the diff if t…

In my experience, if you are reviewing 800+ line PRs you should be in an IDE. I believe the average human being can not review an 800 line diff reliably. Such large PRs would also probably benefit from live discussions over video (or in the good old days -- in person).

I've reviewed 4000 line MRs without problems using other tools. It is possible.

Re: Every software system used at Gitlab

#112

Very nice! Thank you for sharing, I wonder though, no fancy big-screen dashboard service in there? Do people not value that kind of thing?

They are a remote distributed team. I don't think their employees would value having to arrange their workspaces to accommodate a big screen set up high and at a distance from their workstation.

Dashboards are nice to have even on remote teams I think. Anyone can put up the dashboard or make a dashboard for their own screens if they wanted to.

Re: Every software system used at Gitlab

#115
post #29

I’m wondering where the GL is, for when we outgrow Xero (which was about six months ago).

This isn't a recommendation or advice but if you're after a ledger that's larger than what Xero can offer to a big org, Netsuite seems to be what Gitlab uses and is ironically enough also what Xero uses. Unfortunately (and somewhat ironically?) we're too big to actually have Xero run on Xero

If you’d like some feedback, for us it’s less a volume issue and more a case of design limitations. We run subledgers per customer in our own code for clearing and settlement (we’re a two-sided network), and posting the rollups back to Xero sometimes runs into edge cases and limitations. Recognition timing is one pain point, another is API-driven reconciliation.

What I’d struggle to give up is the ease of reporting. Xero’s report designer is right in my sweet spot for usability, flexibility, and domain-specific correctness, probably my favourite reporting tool in three decades of shaking down business software.

Re: Every software system used at Gitlab

#116
post #59

Earlier quoted context omitted.

Enterprise is definitely not on the menu, and Hubspot or one of the similar alternatives does sound more around the level she'd need. I had some fun messing around with Mautic and it could be fun to learn, but I'm not sure how its future looks.

I’m not a Mautic user, but its future looks brighter now that they were acquired by the company behind Drupal. https://www.acquia.com/about-us/newsroom/press-releases/acqu...

Acquisitions can go both ways and apparently the guy who invented and put a lot of sweat into it (dbhurley) has parted ways with the project. Also they used to produce a lot of media on using it, but it's all a couple of years old now. Maybe that means they got the fundamentals right back then but it does send a mixed message. I would love to try it, I've set it up and it seems to be working, but I'm just not sure what'll happen if something goes wrong (their forum moves a little slow too). I have no special knowledge, just a gut feel and outsider impressions.

Re: Every software system used at Gitlab

#117
post #99
post #43

Earlier quoted context omitted.

In my experience, if you are reviewing 800+ line PRs you should be in an IDE. I believe the average human being can not review an 800 line diff reliably. Such large PRs would also probably benefit from live discussions over video (or in the good old days -- in person).

Interesting, I’ve only went through the effort of checking out a pull request for review a couple times. What’s the workflow like? Any tips for reducing friction? I avoid checking out PRs because it’s much higher friction and because I trust CI to catch most bugs so the crappy code forge interfaces are good enough. Personally, I would kill for a one click to step review interface in IntelliJ that synced comments back…

I use gitlens extension on Visual studio.Pretty great so far.

Re: Every software system used at Gitlab

#118

Earlier quoted context omitted.

As someone who has a B2B startup there is almost nothing in the open source space for Marketing/Sales Ops. And anything that does exist is really low quality. And it's because (a) most developers aren't exposed to non-Engineering parts of the company so they have no understanding of what problem to solve and (b) it is incredibly lucrative to build a proprietary SaaS solution.

> there is almost nothing in the open source space for Marketing/Sales Ops There is https://erpnext.com/ which is completely FOSS built on Frappe framework. If anything, it is rather higher quality than most SASS solutions out there.

Word of advice: stay away from Erpnext, don't get fooled by the apparent "clean" interface.

They might have some good conceptual ideas, but the implementation is horrific, their ops/delivery infrastructure a shitshow if even there's one, bugs all over the place and a product management that basically says yes to everything and finishes nothing.

They are in part victims of their own success, but just look at their Github issues page.

Re: Every software system used at Gitlab

#120

I'm so sick of Gitlab support spam in every thread that mentions any issue, making it so that critical conversations are interrupted with self serving pitches! >I once saw Gitlab do this thing. >Hey, Bob from Gitlab thing here. We are really trying to make thing great for our customers . Our next release of thing will do foo which we hope will fix this. Here is a link to a marketing post comparing us to GitHub. Hope…

Would you rather have say, Google’s style of replying on issues with deafening silence? I see your point though. I think it’s better this way. A company can be helpful or shoot themselves in the foot while they figure out to communicate. Too much salesy self-serving talk means they don’t take you seriously so why should you return the favor? Now you can find out easily.
Post reply on HN