HN user

tobiaslins

4 karma

Founder of splitbee.io

Posts13
Comments23
View on HN

Vercel | Remote - Germany & UK | Full stack Engineer | Analytics

At Vercel, our mission is to enable developers to create at the moment of inspiration.

https://vercel.com/careers/software-engineer-analytics-uk-48...

Other roles

Remote (US)

- Software Engineer Billing: https://vercel.com/careers/software-engineer-billing-us-4834...

- Software Engineer Cloud Platform: https://vercel.com/careers/software-engineer-cloud-platform-...

- Software Engineer Monitoring: https://vercel.com/careers/software-engineer-monitoring-us-4...

- Software Engineer Turborepo: https://vercel.com/careers/software-engineer-turborepo-us-48...

Remote (Germany/UK)

- Software Engineer Storage: https://vercel.com/careers/software-engineer-storage-uk-4895...

I've 3 sources of feedback that are working great for splitbee.io:

* Hitting up active customers on Twitter, just writing a short message: "Hi xyz, just saw that you are using Splitbee quite actively. Do you have any feedback for me, that would help a lot"

For this method I got answers from 9/10 people with amazing feedback. Very detailed and long messages. Be sure to target "power" users.

* I sent automatic emails if someone embeds splitbee successfully to their page & a mail if they don't do it within 24 hours. People often engage with them and explaining why they did not embed it yet. Also pretty helpful

* We added the feedback.fish widget to all of our https://splitbee.io/docs/embed-the-script and in our app. We get about 8-10 submissions a month which is quite a lot for our size.

1. Axcept takes care of scaling your test runners while for Cypress you will need to do it by yourself.

2. The main focus of Axcept is Screenshot testing. We provide a powerful tool that helps you going through the UI changes after a test run. Simply press "Accept" to make a screenshot to the new reference. No need to manage your screenshots.

3. Percy is focused on testing (React) components while Axcept can test your whole UI. You can create e2e tests or mock REST requests.

4. Because Axcept is hosted in the cloud it's easier to collaborate on your test suite.

With Axcept you don't need to touch your codebase to get started. Just signup and generate or create your first test. You will get a powerful test editor and screenshot management directly in your browser aswell as chrome debugging tools.

Axcept helps you creating, organizing and executing your screenshot testing suite. You write the tests with our powerful test editor, we execute them with high speed (up to 100 tests in parallel).

We solved most of the problems of screenshot testing such as: - Mocking - Screenshot Management - Scaling

You can get up and running in a matter of minutes!

The line "Loves dogs, hates JavaScript." is really unprofessional. Wojciech should write which language he likes..

I realized that passion to your work has a huge impact to your application. If you are software developer (what I excect) and have a job - yeah it is a valid opinion. If you don't want to code in your free time it is up to you.

It doesn't mean that you have a narrow set of interests. It just mean I use a part of my free time to code. Others are watching tv, playing games or doing other time wasting stuff.

A developer who loves his job/hobby also codes in his free time (because it is also a hobby)

Of course, if being a develoepr is only a "job" - this sucks.

For example, I am coding 8h+ a day during my fulltime job. When I am back at home/weekends, I also spend a lot of my time to code private projects instead of playing games

You don't need to make your source public. Just check it in as private repository and your contribution graph is going to be filled. Some recruiter can now see that you work a lot - probably also on weekends and so on.

A good looking github contribution graph looks kind of professional, also if you have starred some repositorys (which probably means you are active and love what you are doing)