HNHacker News
TopNewBestAskShowJobs

sytse

12,257 karma · joined December 15, 2009

I'm a co-founder and executive chair of GitLab https://about.gitlab.com/ and co-founder of Kilo Code. More information about me is on http://sytse.com/ I'm also a general partner at Open Core Ventures https://opencoreventures.com/ (portfolio companies are listed on the website)
submissionscomments
sytse··on Asking developers to do QA is broken – why anyone should own QA
Thanks Russell. In our experience a lot of QA improvements require automation which is more of a software engineering job than a product management one.
sytse··on Asking developers to do QA is broken – why anyone should own QA
I agree with not asking the developers of the feature. I don't think it should be part of product. QA is a deeply technical job. At GitLab QA gets own department called Quality. They are on the same level as development, design, development, and infrastructure. The people in it are mostly Software engineers in test. For more information please see https://about.gitlab.com/handbook/engineering/quality/
sytse··on Meltano raises $4.2M seed round
Meltano is a open source platform for automating ELT pipelines.
sytse··on How a Jenkins Job Broke our Jenkins UI
Yes, GitLab CI supports Windows Docker containers, see https://docs.gitlab.com/runner/executors/docker.html#using-w...
sytse··on Phacility is winding down, Phabricator no longer actively maintained
Phabricator was an inspiration to me when starting GitLab. It is shutting down now. Many of its features were years ahead of its time https://news.ycombinator.com/item?id=27334511 and there was a lot of humor in the product. As a tribute to it shall we add Clowcoptarize as a way to merge? This would be an opt in option introduced in GitLab 14.0 https://gitlab.com/gitlab-org/gitlab/-/issues/332215
sytse··on What if remote work didn’t mean working from home?
Remote work shouldn't mean working from home. Not everyone can do that physically (having space) and mentally. At GitLab we pay for an office if you decide you want to work outside your home. Most people end up working from home but before the pandemic many opted to work a few months from an office to make the transition more gradual.
sytse··on Complexity is a source of income in open source ecosystems (2019)
The incentive to make open source products more complex is worse for consultancy business models than product driven ones.
sytse··on What to do about GPU packages on PyPI?
Central registries for many languages have a hard time keeping up with the increased use by automated processes.

In GitLab we have a mirror functionality for docker container images, I look forward to us extending it to other package types as well. This should reduce load in the central registry, speed up the download, and improve the overview of what packages are in use at the organization.

sytse··on What to do about GPU packages on PyPI?
Does GitLab have a hardcover limit on docket images? Or do you hit a timeout?
sytse··on Next-generation Deploy Previews, plus Netlify acquires FeaturePeek (YC S19)
We're exploring how to reduce or remove this set up work with https://gitlab.com/gitlab-org/gitlab/-/issues/35322
sytse··on WeWork CEO Says Least Engaged Employees Enjoy Working from Home
I agree that some working for home for all people makes sense.

With hybrid I refer to some people never being in the office https://www.wired.com/story/hybrid-remote-work-offers-the-wo...

sytse··on WeWork CEO Says Least Engaged Employees Enjoy Working from Home
Hybrid remote is the worst of both worlds. The best remote employees will move to fully remote companies so they can move out of the B-team. Over time Sandeep will be right when he says: "Those who are least engaged are very comfortable working from home."
sytse··on Write Gitlab CI Pipelines in Python Code
At GitLab we take the 'Release notes' section of each issue and use it to automatically generate the release post. For an example of a release post see https://about.gitlab.com/releases/2021/04/22/gitlab-13-11-re...
sytse··on Semgrep: Semantic grep for code
I agree it is an excellent tool. At GitLab we released our Semgrep integration today https://news.ycombinator.com/item?id=26903114

"GitLab SAST historically has been powered by over a dozen open-source static analysis security analyzers. These analyzers have proactively identified millions of vulnerabilities for developers using GitLab every month. Each of these analyzers is language-specific and has different technology approaches to scanning. These differences produce overhead for updating, managing, and maintaining additional features we build on top of these tools, and they create confusion for anyone attempting to debug.

The GitLab Static Analysis team is continuously evaluating new security analyzers. We have been impressed by a relatively new tool from the development team at r2c called Semgrep. It’s a fast, open-source, static analysis tool for finding bugs and enforcing code standards. Semgrep’s rules look like the code you are searching for; this means you can write your own rules without having to understand abstract syntax trees (ASTs) or wrestle with regexes.

Semgrep’s flexible rule syntax is ideal for streamlining GitLab’s Custom Rulesets feature for extending and modifying detection rules, a popular request from GitLab SAST customers. Semgrep also has a growing open-source registry of 1,000+ community rules.

We are in the process of transitioning many of our lint-based SAST analyzers to Semgrep. This transition will help increase stability, performance, rule coverage, and allow GitLab customers access to Semgrep’s community rules and additional custom ruleset capabilities that we will be adding in the future. We have enjoyed working with the r2c team and we cannot wait to transition more of our analyzers to Semgrep. You can read more in our transition epic, or try out our first experimental Semgrep analyzers for JavaScript, TypeScript, and Python.

We are excited about what this transition means for the future of GitLab SAST and the larger Semgrep community. GitLab will be contributing to the Semgrep open-source project including additional rules to ensure coverage matches or exceeds our existing analyzers."

sytse··on Show HN: I'm working on a open-source, self-hosted alternative to Disqus
Very cool! I would love to switch away but a Disqus import would be needed before we can do so.
sytse··on Modern CI is too complex and misdirected
"I almost want to say it's been around longer or as long as docker?"

I had to look it up but GitLab CI has been around longer than Docker! Docker was released as open-source in March 2013. GitLab CI was first released in 2012.

sytse··on We are far from a better Heroku for production apps in a hyper cloud
It is fair game to judge us based on our blog. At the same time it is a free-for-all for employees for blog posts marked Unfiltered as this one is. The author apologized in https://news.ycombinator.com/item?id=26555617 and we've made 8+ updates to the article to reduce the bias https://gitlab.com/gitlab-com/www-gitlab-com/-/commits/maste...
sytse··on We are far from a better Heroku for production apps in a hyper cloud
A production app has stateful services that retain data between deployments. The ambition of the 5 minute production app is to make this faster than doing it on Heroku.

The article doesn't make this case at all. Heroku is suitable for production and we didn't intent to suggest otherwise.

sytse··on We are far from a better Heroku for production apps in a hyper cloud
It was a bad blog post, we're sorry. Also see the comment by the author https://news.ycombinator.com/item?id=26555617
sytse··on We are far from a better Heroku for production apps in a hyper cloud
I fully agree, this should have been about it production app, not a development app which is already great on Heroku. Also see this post by the author https://news.ycombinator.com/item?id=26555617
sytse··on We are far from a better Heroku for production apps in a hyper cloud
Convox is an inspiration. This is using GitLab CI and Terraform.
sytse··on We are far from a better Heroku for production apps in a hyper cloud
I agree the blog post isn’t clear on that.

I agree a simple production app can be great on Heroku. However besides being costly it is also hard when you want a managed service that isn’t on the platform. There are other reasons, https://gitlab.com/gitlab-org/5-minute-production-app/deploy... lists 9 in total.

While a production app on Heroku isn’t hard it isn’t trivial either. We’re trying to make the 5 minute production app faster to set up than Heroku for production apps by automatically configuring a bunch of services. We’re not there yet but that is the goal.

sytse··on We are far from a better Heroku for production apps in a hyper cloud
In the West it means AWS, Azure, or GCP. See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...
sytse··on We are far from a better Heroku for production apps in a hyper cloud
The article isn’t clear about it but the 5 minute production app is an ambition, not a reality.

Setting up IAM is indeed hard. The most workable idea we have so far is having the user run as CloudFormation script to set it up, see https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

sytse··on We are far from a better Heroku for production apps in a hyper cloud
I agree Heroku has the perfect dev environment, not much to improve there.

We’re trying to make the perfect production environment. Most people end up hosting at a hyper cloud (edit: like AWS). We’re trying to make the app on a hyper cloud in production as easy as Heroku is in development.

We’re still building that, it is t done by any means. And the article doesn’t do a good job of showing what we are trying to make easier. Setting up managed services on AWS is time consuming and that is what we want to solve. See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

The contents of the blog post doesn’t warrant the title. We regret it.

sytse··on We are far from a better Heroku for production apps in a hyper cloud
I’ll ignore the last word.

The article doesn’t do a great job of showing it, but the 5 minute production app makes it easier to setup stateful services on the hyper clouds.

And it does spin up a new environment for every merge request.

sytse··on We are far from a better Heroku for production apps in a hyper cloud
The 5 minute production app is a fancy GitLab CI script that uses Terraform to provision managed services.

The goal is to “quickly make a stateful app that is deployed on a hypercloud” https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

sytse··on We are far from a better Heroku for production apps in a hyper cloud
Yeah, I think it would have been better to differentiate in the article based on setting up state.

It takes a while to configure a persistent database, redis, and storage on Heroku. That is what we’re trying to make easier, as well as hosting it on a hyper cloud.

See https://gitlab.com/gitlab-org/5-minute-production-app/deploy...

sytse··on Gitlab 13.10 Released
Thanks for these! Some people at GitLab are looking at your post.
sytse··on Gitlab 13.10 Released
I'm inspired by products like Zoom, Chrome, VScode, and Slack that are both user friendly and full featured.

Any examples of features that we probably shouldn't have added and should consider removing?

We intent to replace the DIY DevOps toolchain with GitLab. Something that consists of many applications and interfaces. Just having it in a single application would already be a big quality of life improvement for the users. And so far the most common hurdle is being able to match the functionality of the point solutions.

← PreviousPage 5 of 34Next →