With so many remote job boards, some of them could do more to be useful to target customers (people looking for jobs, not companies posting them) by not simply being "remote job board for X, Y or Z", rather focus on the facets of what makes working remote actually work.
Time zones, for example. A lot of remote jobs are with companies that only consider remote work to be work done from your home and only if in the same city as their office, and during the same hours. While this technically shouldn't matter, it greatly limits the success and talent pool available when you don't consider all the available time zones and cities which are great for remote workers.
Additionally, I've found working remote for companies that don't have a remote first culture to feel more like grunt in the corner that is ignored than part of a team and as an experienced professional with values and insights to contribute to the team. While that might seem like a great deal on paper — lower on costs — it works out terribly in the long run with ROI.
Working with a completely distributed team (no HQ) on the other hand is the best job I've had in 10 years, both in terms of culture, team dynamics, subject matter, salary, location, work environment, etc etc.
I am European and something that bothers me a lot are companies that are hiring remotely, but then ask me to relocate or are US-only. That's why I added a category on every RemoteML job post: Anywhere, Remote US and Remote near HQ
Unfortunately that's a reality. This happens to me a lot. Remote work JUST for US citizens. The irony is that most of those companies pay attention to not discriminate people (minorities, sex orientation, disabilities and other things) but they discriminate those that don't have USA passport :-(
Facebook might be known as a US company, but they pay taxes in Ireland (amongst other low tax territories) and hold most of their assets there to avoid paying taxes in US.
Personal attacks will get you banned here, so please don't post like this.
You've unfortunately posted other uncivil comments in the past, too; could you please (re-)read the site rules at https://news.ycombinator.com/newsguidelines.html and use HN as intended from now on?
You can definitely do all those things with JMeter, although the user experience is pretty naf, Gatling[3] is definitely much better at that front if you're comfortable writing Scala.
When it comes to Protocol Level Testing, those two tools are still pretty much the best bang for buck, and by far the most popular open source load generators.
If the target you're hitting is a web app and you want to create a more realistic load scenario without crafting individual requests, check out a tool called Flood Chrome, which uses thousands of instances of Google Chrome[1] to generate load. It uses the same scripting language as SeleniumJS, so it's quite easy to learn.
Also on the topic of Flood [2], they're a very good platform for abstracting away the server orchestration and results collection you'll face when you try to scale up from 1 to N servers running either Gatling or JMeter.
Oh hey Sandeep, sorry about that, I came across this as a suggested article on Medium and thought I'd post it to HN. For all reading this: See correct link above ^^
Qantas also holds the record for the longest duration commercial flights: the 27-33 hour Double Sunrise service between Perth and Ceylon during WW2. At the time they were also the longest distance non-stop flights.
I've done a few projects like this. I'd recommend checking out https://plaid.com for bank feeds if you're in America, otherwise something like nightmare.js for scraping your bank.
Time zones, for example. A lot of remote jobs are with companies that only consider remote work to be work done from your home and only if in the same city as their office, and during the same hours. While this technically shouldn't matter, it greatly limits the success and talent pool available when you don't consider all the available time zones and cities which are great for remote workers.
Additionally, I've found working remote for companies that don't have a remote first culture to feel more like grunt in the corner that is ignored than part of a team and as an experienced professional with values and insights to contribute to the team. While that might seem like a great deal on paper — lower on costs — it works out terribly in the long run with ROI.
Working with a completely distributed team (no HQ) on the other hand is the best job I've had in 10 years, both in terms of culture, team dynamics, subject matter, salary, location, work environment, etc etc.