I'm making a surf forecasting site a la surfline.com, I started mostly to have an API to use for my tidbyt, but I figured I might as well make it a full thing and built my own features! It's on quickswell.com but it's only Socal at this time (fewer spots to compute)
Even when using google docs, I dropped the paper format, and at that point it's better to edit/read in a richer editor like Confluence which has better support for interactive widgets, expand zones, code blocks, etc. It's also been better at navigating a tree of documents.
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.
If we're going to give anecdotal data, when I lived in NYC I was hired as an H1B, and every single other H1B I knew was paid way more than the median wage. But these were companies not trying to abuse the system. I do not doubt that there are bad actors.
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.
I like the idea, but also it wouldn't feel fair for some services that I use like Twitch, or some cooking websites. I get that they sometimes really abuse all that stuff, but also I feel like they deserve some kind of compensation.
Hello - I checked with somebody internal at Spotify and the recruiting team could not find these job openings. They are not on the normal Spotify recruiting portal: https://www.lifeatspotify.com/jobs?l=los-angeles
Maybe they're cranking out AI SaaS products to see what sticks. I was going to say low effort, but it's not zero effort and does offer some kind of service. I could have used some AI help for my kitchen design, I hated the process.
It's cool conceptually, but I think for family I haven't known, for family I have known and is aging/deceased that would make me pretty sad so I probably wouldn't use it.
That's a robot's take. You can have days where you slept poorly or need a nap to get back on track or just lack motivation.
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.
I think it's interesting to read people voicing concerns and limitations of the projects in the comments (that's why I came to read them), but I was hoping more people would be excited about the idea. Even if it doesn't work out, I root for people who try out ideas like this.
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.
They did use Temporal at Netflix, they gave a couple presentations 2 years ago. I think this is very much not-Temporal because it relies on a DSL instead of workflow as code.
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?
What do you mean? That as a sysadmin he should also have solved the product/sales/marketing woes of the company? You can only do so much at certain positions. Even if you go out of your way to make people aware that they are making a costly mistake, it's can be really hard to sway them.
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.
I found out about Temporal 2+y ago now and were early adopters of their cloud. It's a bit of a paradigm shift when you start using it, but it is amazing at solving some types of problems in a very simple manner. There are some trade-offs, there always are, for us that was migrating long lived workflows. But the resulting simplicity and maintainability of the code has been great. One thing that was hard with Temporal was to "sell it" to business leaders because it's not a turn key solution, it's more like a piece of infra for engineers to build on top of. Kind of a higher level database-queue-workflow engine thing that simplifies work for engineers.
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).
I found the intro video pacing and music a little unpleasant. It's going a little fast too, slow down, I gotta absorb what's going on and how it's going to make my life easier!