Google docs is still great when you need to make something you mean to print, it just tends to not be that often anymore.

I even use markdown shortcuts to format in google docs nowadays.

We're a company based in the US focusing on helping small and medium businesses be on top of their IT with the help of software and automation, even if they have limited IT & security knowledge.

We're looking for a senior frontend engineer, we're react shop with a standard stack. We're a mix of US and South America based engineers on the team.

email: cmVtaS5jYXJ0b25AZWxlY3RyaWMuYWk=

I do agree that there should be minima to prevent abuse. I do not agree that every H1B hire was to abuse the system.

In the early 2010s there were hiring shortages, the startup that hired me would have probably preferred saving on the attorney fees and the 6+ months it took between the offer and the start date. For a new H1B you have to prepare the paperwork in March at the latest, apply the first week of April, for a start date of October 1st. And not only that, but with the quotas and the lottery you're absolutely not guaranteed that your hire is going to make it. All things being equal without a shortage or the ability to underpay, it is not an attractive solution.

H1Bs do push salaries down, because there is more "supply" of workers, so it should probably only be used for hiring for areas with shortages, but even then you can have downturn like what we're having in tech, and some companies may keep their H1Bs over FTE because they are less of a flight risk and can't negotiate their salaries as well. Even with a shortage, this means that employees with that specific skill will be paid less, now it's more of a matter of which one is better for the economy/society.

Could you prove that these are real positions?

Personally I try to take on tasks that don't require as much brainpower. If I'm really too tired I'll just take a nap, because it's better to take a 20 minute nap and do work for the rest of the afternoon than feeling terrible and doing hardly anything for a whole afternoon.

Every once in a while some crazy idea like breaking down atoms to generate electricity works out and we're all better off thanks to it.

I don't know if it's a scale-thing, I'm not a workflow expert but this seems more in line with the map-reduce of yore, as in you get some big fat steps and you coordinate them, although you could have coarse-grained activities in Temporal workflows.

I'd be curious to see what the tradeoffs are between the two and if they still have usages for Temporal. Maybe Maestro is better for less technical people? Latency? Scale?

If the marketing team does a shit job, maybe I can tell the marketing is shit, but I can't do more than trying to make people aware of it. Even with the best diplomacy skills you often can't fix that from the engineering side unless you are high enough on the totem pole. I've once expressed polite concerns about a marketing decision to the CEO whose good friend was newly appointed head of marketing, got told off by the CEO and the marketing lady proceeded to wreck our branding and confuse our customers.

In short we were working on automating things like onboarding a new employee, which involves creating accounts for their saas apps, buying and shipping their device, email confirmations, satisfactions surveys etc. So a workflow could last up to 3 months with some fully automated systems, and some that required integrating with people (listening to jira event to trigger things, etc).

The error handling was the thing that sold me on Temporal, because things can break just about anywhere in unpredictable ways (not just code, can be process, employee quits during the onboarding, customer is out of licenses etc), so we need everything to be robust and be fixable by a person. With homegrown queue based systems or with BPEL it can be hard handling these situations (what if you need to roll back 3 steps?). With code you can use exceptions, write unit tests etc. We use the typescript sdk, promises made it very intuitive to code even some otherwise complicated scenarios (say event listeners etc).