xando

Some context: One of the richest guys in Poland, who became famous for creating a product that people genuinely like (https://inpost.pl), got really angry with Meta for allowing fake and offensive ads. He decided to use his money to take them on.

The article is in Polish. Google Translate version linked.

Happy Kagi user.

I switched to Orion at some point, but due to bugs and battery drain, I had to switch back (to Safari!) As soon as those are fixed, I’m back again.

I’d also pay for it, if that changes anything. Actually, I would pay for the browser, period, if it was good, respected privacy, was efficient and fast on mobile, and synced things between devices.

Eventplicity | Fullstack, Frontend, Backend Engineer | Gainesville, FL | REMOTE (anywhere) | Full-time | http://www.eventplicity.com

We are seeking both a Senior Backend Engineer and a Senior FrontEnd Engineer. (Fullstack developers also welcome.)

About Eventplicity Eventplicity provides planning and logistics software that helps restaurants book private parties and special events. We're a startup with an exciting growth trajectory. This isn't restaurant reservations. We book private events that involve the planning and execution of many intricate details. We provide a modern web application that tackles the surprising number of complexities involved in planning private parties from start to finish. Every venue is different, every event is different, and every booking is different. Join our team and help us build the right set of abstractions and the modern interface that will wrangle these complexities into a smooth, easy-to-understand online booking experience.

Our Stack:

Front-End: Modern Javascript stack (ES 2015+ syntax, babel, webpack, jest, React, Redux, Socket.io, Bootstrap)

Back-End: Python, Flask, Small amount of Node.js & Go, Redis, PostgreSQL

DevOps: AWS, Docker, CircleCI, Git / Github

Development Culture

* We greatly value high quality code and strong technical acumen.

* Since we're a startup, we understand there are tradeoffs and there will be technical debt. We can't make everything perfect. While we greatly value high quality code, we know it's equally important to move fast and learn from our users in order to succeed.

* We prefer stable technologies, but we also want to use modern tools.

* We do not make artificial deadlines. We work hard to be productive, but it's never a push for an arbitrary date.

* There is no bureaucracy (our software team is small).

Got questions? Sounds interesting? Feel free to contact us at devjobs@eventplicity.com

HN's "Who is Hiring" jobs only filter https://whoishiring.io/search/36.6845/-92.8938/4?source=hn

Speaking from the perspective of someone who did some amount of web stuff with maps.

Mapbox feels really good. API, docs and rendering performance all of this is really good. Although it's not an obvious choice if you are starting fresh. I personally find the pricing impossible to digest. Probably sounds reasonable for well-founded startups from developed countries. If your doing a bootstrapped product and can't pay 500$ it's not for you.

Google Maps. the v3 it's here for a while. The API feels good, but not great, Stack Overflow is your documentation. Rendering performance is bad, rendering performance with (many) markers without some hacks is terrible, rendering performance on mobile is even worse. I'm trying to figure out what new the pricing means for me.

Leaflet and OpenStreetMap look like a better choice for all hobby projects and small product from now on.

I wasn't planning to go that broad, extending this outside IT would need serious research in HR mechanism for each of those categories. I'm not calming that that I know HR in IT but this project kind of evolved from my needs.

You can filter using the category filter. Link bellow is for design jobs.

https://whoishiring.io/search/39.4871/-110.8740/3?category=d...

Disclaimer: I wrote whoishiring.io, and I'm not doing too good job to present that other categories ar available (the filter is missing on the index page). But yes my main focus in the beginning were dev jobs.

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io/

https://whoishiring.io/hn (just HN items)

There is a report button if I've mismatched something.

If you post here (and want to have your post on the map) please check this format (https://gist.github.com/xando/5c2ba312184ad0356335a87ec3a750...) it helps with parsing. If you won’t, no worries, I will do my best to get all the things right.

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io

https://whoishiring.io/search/36.0440/-90.8984/4?source=hn (just HN items)

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {location} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the first line, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

Check bellow for the SALARY regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

you can test it as well https://regex101.com/r/SRWkMz/2/

Also there is a report button if I've mismatched something.

Despite the best efforts, sometimes jobs items might have wrong matches.

There is a report button though, I usually fix them in few moments if my keyboard is around.

Thanks!

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io

https://whoishiring.io/search/36.0440/-90.8984/4?source=hn (just HN items)

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {location} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the first line, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

Check bellow for the SALARY regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

and you can test it as well https://regex101.com/r/SRWkMz/2/

Great idea go for it!

lanyrd.com is long dead without any good replacement. I'm not too sure why they keep the website up. What it does it only confuses people. I know that this probably out of their control right now. Eventbrite killed the really good website.

The service they had was solving real problem. Now you are solving real problem. Good luck!

I'm surprised that no one here actually mentioned HN's "Who is Hiring" thread. I'm my personal option this one is most valuable place and good staring point if you are looking for a job.

Also it's happening right now go and check it -> Ask HN: Who is hiring? (July 2017) https://news.ycombinator.com/item?id=14688684

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

- https://whoishiring.io,

- or just HN items https://whoishiring.io/search/36.0440/-90.8984/4?source=hn

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {locations} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the first line, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

Check bellow for the SALARY regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

and you can test it as well https://regex101.com/r/SRWkMz/2/

---

There is a "REPORT" button in footer of job offers, please complain if I did something wrong.

I'm sorry, I can't right now, the script finished after first match. I also know that creating multiple entries for this scenario would be just ridiculous, and you shouldn't do it.

I will spend some time think about multiple location, but this probably will be limited only to those placed in the first line.

Thanks for the feedback.

Thanks. Every 20 minutes.

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on https://whoishiring.io or just HN items https://whoishiring.io/search/36.0440/-90.8984/4?source=hn If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {locations} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the first line, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

Check bellow for the SALARY regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

and you can test it as well https://regex101.com/r/SRWkMz/2/

There is the "report" button in footer of job offers, please complain if I did something wrong.

Please send me console logs / screenshot. sebastian@whoishiring.io

This sounds like a really good feature to have. I will try to build something to flag "broken" jobs.

I think I get it. I didn't want to stretch HN formatting too much, but since this was raised before, looks like a real issue. My thoughs:

- We could extend the locations format to comma separated values. Although some people will use "London, UK" or "Philadelphia, PA" so comma doesn't look like a good idea.

- use ";" instead of ",' to separate values eg. " ... Lead Engineer | London, UK; Philadelphia, PA | ... "

Other ideas welcome.

Every 20 minutes from https://hacker-news.firebaseio.com/. Sometimes update delays could be caused by HN to firebase push (which happens every X interval as well)

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io or just HN items https://whoishiring.io/search/36.0440/-90.8984/4?source=hn

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {locations} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the first line, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

Check bellow for the SALARY regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

and you can test it as well https://regex101.com/r/SRWkMz/2/

Thanks for letting me know, fixed.

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io or just HN items https://whoishiring.io/search/36.0440/-90.8984/4?source=hn

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {locations} | {attrs: ONSITE, REMOTE, INTERNS, VISA, SALARY, company-url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA, SALARY:100k-120k
  Facebook | Web-developer | Zurich | SALARY:120k CHF 
  Google | Site Reliability Engineer | London | SALARY:120k GBP, VISA, REMOTE

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | Sydney
  Facebook | Web-developer | Zurich

I’m using this regex to test the firstline, you can test it here https://regex101.com/r/relwQD/3

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

NEW THING. There were requests for salary, so since this edition attrs section will handle salary as well. Check bellow for the regex.

  SALARY:(?P<salary_min>\d+(?:k|K)?)(?:\s*\-\s*(?P<salary_max>\d+(?:k|K)?)?)?(?:\s?(?P<currency>[A-Z]{3}))?

and you can test it as well https://regex101.com/r/SRWkMz/2/

It looks like something related LocalStorage in browsers. I'm logging those events with Sentry. For now it looks like I have 3 events like this from FF.

I will see what I can do about it.

Salaries will appear as a filter soon, hopefully before next edition. I get this request a lot.

For now you can keep salary in the first line in {attrs} section for, or somewhere below the first line.

What kind of the format you would like to see for salaries?

Ok I see

https://en.wikipedia.org/wiki/Null_Island

I've decided to leave them there. Since I can't figure where to put them on the map, the address in most of them is "remote".

That is not ok. Could you give me an example? I will try to fix it

Hey, a friendly reminder. I’m parsing the thread, all job offers added here are also available on the map on

https://whoishiring.io

or just HN items

https://whoishiring.io/search/36.0440/-90.8984/4?source=hn

If you post here, please use the below format to help me with parsing. If you won’t, no worries, I will do my best to get all the things right.

  1) {company} | {job title} | {locations} | {attrs: REMOTE, INTERNS, VISA, company url}
  Google | Software Developer | SF | VISA https://google.com
  DuckDuckGo | Software Developer | Paoli PA | REMOTE, VISA

or

  2) {company} | {job title} | {location}
  Google | Site Reliability Engineer | London, Zurich, Sydney
  Facebook | Web-developer | London, Zurich

I’m using this regex to test the firstline.

  \s*(?P<company>[^|]+?)\s*\|\s*(?P<title>[^|]+?)\s*\|\s*(?P<locations>[^|]+?)\s*(?:\|\s*(?P<attrs>.+))?$

You can test it in Python or here https://regex101.com/r/relwQD/3 (for the match look right).

Thanks for the reply. I will have look and try to test it.

But if you think this is something ready to use in commercial projects, ask for money. I usually feel personally better to if I can pay for things, also paying for things opens a window for to have quality requirements.