Perihelion
Joined 16 years ago
Karma
340
Submissions
74
Member since
Mar 11
Recent submissions
Comment · 5 years ago
Meltano | All positions are full time and remote | https://meltano.com (follow the code blocks on our website for a demo!)
We're a seed stage startup that recently spun out of GitLab. A bit about us:
Meltano is an open source DataOps platform that brings together best-in-class open source tools and technologies for the data lifecycle, including the Singer standard for data integration, dbt for transformation, Airflow for orchestration, and soon Superset for visualization. It simplifies configuration, deployment, and monitoring, and lets data teams benefit from DevOps best practices such as version control, code review, and CI/CD.
Stack: Meltano and the Meltano SDK are written in Python. Vue.js (as part of VuePress) and Bulma CSS are used on the front end.
Open Roles:
- Backend Engineer - Senior Backend Engineer - Senior Frontend Engineer - Head of Partnerships - Content Marketing Manager - DataOps Evangelist - Senior Support Engineer - Technical Marketing Manager - Senior UI/UX Designer
Apply online at https://meltano.com/jobs. If you have questions please reach out to us on Slack: https://meltano.com/slack
Comment · 5 years ago
Thanks! This is really useful feedback. To date, Meltano has been geared towards data folks who are likely to understand these concepts and acronyms, but there's definitely a need to explain it for folks who aren't as familiar. We're going to be working on the website copy in the coming weeks to make it easier to understand with as little digging as possible. If you think of anything else please feel free to reach out to us.
Comment · 7 years ago
Definitely. That they're trying to position this as an oversight is frankly disgusting. That code was intentional.
Comment · 7 years ago
This so much. It works really for your house too. I find that decluttering my physical and digital workspace at the end of the day means I'm not stressed about mess in the morning.
Comment · 9 years ago
Yeah, it was there (along with a note on how to get free stickers) but now it's gone. Keybase stuff is still there though. Random.
Comment · 9 years ago
Thanks so much for your kind words! We're always trying to improve, so even though some of the comments are negative, it's still good to hear about pain points so we can fix them.
Comment · 9 years ago
Hmm, not sure what happened. It was there, now it's not. It's [email protected] -- sorry about that.
Comment · 9 years ago
I've actually experienced this exact thing. Usually a refresh fixes it for me so I never gave it too much thought. I'm not sure what causes it exactly but I'll follow up with the team about it. It usually happens to me on merge requests -- do you notice it on specific pages at all?
Comment · 9 years ago
I'm really sorry to hear about the crappy experience you've had with GitLab. If you'd like to detail some more complaints, I'd love to hear them and open some issues about these things. Feel free to shoot me an email (located in my profile) or reply here. Either way, thanks for the feedback you've provided here.
As far as the frequent upgrades go, we've been using .com as a way of dogfooding GitLab at scale. Sometimes this goes well and other times it doesn't. We're actively working to improve this process so that downtime and breaking changes are less frequent. The end goal is to eradicate both issues so that upgrades are seamless.
Comment · 9 years ago
Since the first part of your comment is addressed to Sasha I'll let her reply to it, but to address the second part:
There are multiple people involved in the hiring process here at GitLab, specifically several people who handle phone screens and resumes. The responsibility of vetting doesn't rest solely on one person and is actually a pretty collaborative process in my experience. As an example, I was able to vet every single candidate's resume myself for roles I was involved in hiring for.
Comment · 9 years ago
Totally agree with this. Having to join 10+ Slack-like groups to collaborate on open source projects is unrealistic for me. As a result, I don't frequent some projects' chats and stick to bug trackers/mailing lists -- as a result of that I miss out on a lot of the camaraderie that comes with contributing to open source. I've missed out on a few conversations where decisions were made too. Being in multiple groups on these services is a huge pain point for me, whereas being on multiple IRC servers in multiple channels is far less invasive to my time and computer resources ;D. I'm not necessarily advocating that everyone use IRC for everything, but it seems like a lot of us had standardized on IRC for OSS before most of these services came along.
Also I'm salty that most of these Slack-like services have no ignore feature/minimal moderation tools which are both things I've leaned on heavily when working with communities. That's probably a rant for another day, but it's related to why I really dislike using some of these things.
This might just be my perception, but it seems like most people I come across in this field were on IRC at some point.
Comment · 9 years ago
Valid point, but there are other things to consider. The reason I buy Windex is because it saves me time. Instead of buying vinegar, lemons, and rubbing alcohol and mixing them together with water every time I want to clean a something, I just grab the Windex/Lysol/etc. Likewise, I can spend time messing around with getting configs for various things in order, or I can one click deploy something to Heroku/AWS/DO/etc and not have to worry about it too much. It all depends on what's valuable to you.
Comment · 9 years ago
We're in the process of migrating the swag store to another provider. Shoot me an email (see bio) and I'll see what I can do for you in the mean time.
Comment · 9 years ago
No problem, thanks for clarifying.
Amanda Folson - Developer Relations @ Meltano