We're not accountable for others choices. It's not on the private sector to play parent
They chose to accept Uber's deal. Don't strawman
A salaried structure is not the same thing as unset hours. This is a pretty standard misconception of people new to the workforce.
It's the aspect of personal choice that you're skipping over. Uber drivers made the choice to apply to work as "independent contractors" and agreed to the terms. A bastard child has no agency in the arrangement, but a…
Sure, of course. I was hoping to point out that there's an increasingly overlooked value in having someone question complexity. The "no, you don't need React" of the frontend dev or the "our data is actually relational"…
That's most "SRE" -- it's a title arms race in that field between the underqualified and those that wish to convey they know how to do more than write system scripts in DSLs
I would offer more specifically that it was trying to solve a problem with existing workarounds for where the problem existed, without checking if anyone else cared enough to write more sgml
I think this is a case for the return of the traditional "sysadmin" as "devops"/"SRE" is now the role of unblocking deploying a solution instead of questioning it's complexity/fitness.
I was going to ask how to optimize the SQL in your post as it seems like the obvious/naive implementation of the query. If you're missing something, so am I. I can only imagine it was built up over time from googling…
We're not accountable for others choices. It's not on the private sector to play parent
They chose to accept Uber's deal. Don't strawman
A salaried structure is not the same thing as unset hours. This is a pretty standard misconception of people new to the workforce.
It's the aspect of personal choice that you're skipping over. Uber drivers made the choice to apply to work as "independent contractors" and agreed to the terms. A bastard child has no agency in the arrangement, but a…
Sure, of course. I was hoping to point out that there's an increasingly overlooked value in having someone question complexity. The "no, you don't need React" of the frontend dev or the "our data is actually relational"…
That's most "SRE" -- it's a title arms race in that field between the underqualified and those that wish to convey they know how to do more than write system scripts in DSLs
I would offer more specifically that it was trying to solve a problem with existing workarounds for where the problem existed, without checking if anyone else cared enough to write more sgml
I think this is a case for the return of the traditional "sysadmin" as "devops"/"SRE" is now the role of unblocking deploying a solution instead of questioning it's complexity/fitness.
I was going to ask how to optimize the SQL in your post as it seems like the obvious/naive implementation of the query. If you're missing something, so am I. I can only imagine it was built up over time from googling…