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.
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.
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 ^^
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.
You should visit New Zealand one day, they have very strict rules about bringing anything in, but I've found their customs people to be the most friendly, even shared a few jokes and tips on snowboard gear with one of the officers while passing through the nothing to declare line last winter.
I'm not sure what the point of this is, Material Design is built on solid design principles which create well spaced and easy to understand interfaces, none of which are goals of Bootstrap.
Combining Bootstrap with Material is like putting salt in coffee, and hiding with some sort of identity crisis. You've named expansion panels; accordions, which sure, they do follow a similar pattern, but which library are you basing the naming on?
As a front-end developer and designer, this makes me cringe.
As the Prime Minister said, it was load tested to handle 1M form submissions an hour. Which is all of Australia completing it in 24 hours. The problem is everyone did it at once, so we only have ourselves to blame.
But seriously, handling 23M form submissions in 1 hour, isn't too hard to do. The 2 major considerations are: 1. How fast can we make the app handle that submission, which honestly is probably just writing to a DB, 2. How many servers so we need to scale out to do the work. You could do this on AWS pretty well, there's much bigger customers on there doing much more load. I've personally seen apps on AWS doing a sustained 1M concurrent requests per minute with less than 10 servers.
The point is, out-sourcing government IT to Companies that are satisfied with meeting the bare minimum requirements without any logical discussion about the maximum requirements, results in CensusFail.
> A phone number uniquely identifies an individual
As someone who travels a lot I can attest to the annoyance of messaging apps which identify users by phone number. WhatsApp is a good example.
Another terrible design is one time passcodes which are sent over SMS. When a number gets recycled it can become impossible to recover access to a service which you forgot was associated with the number you had at the time of signing up in another country.
Being that this is true of getting anything done in the real world I was hoping to frame the question without needing to preface it with that, or listing any qualifications of my own or my team on a pseudonymous account, but needless to say we get things done.
You've mentioned many times, more so recently, that YC is committed to investing in hard tech problems. When considering companies solving these problems for the next batch, knowing that often times even getting a prototype ready is a massive undertaking, how much chance does one have applying with nothing more than an idea and some research? And the possibility that it won't generate revenue for 5+ years?
It certainly gives you a feel for how they do development internally. End of the readme mentions a new version coming soon, instead of say, iterating on this one. Also, the main contributor is stripped of any personally identifiable information.
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.