If you asked chatgpt to generate a document, its generates one that reads well but has terrible content. Eg. Super broad or just plain contradictory. But given some not so well written piece of writing, it can clean that up fairly well.
504 karma · joined January 1, 2011
If you asked chatgpt to generate a document, its generates one that reads well but has terrible content. Eg. Super broad or just plain contradictory. But given some not so well written piece of writing, it can clean that up fairly well.
Basically I created a small app to streamline the workflow. https://henshu.ai
My other favorites are Pandemic Legacy (Season 0 came out in 2020) and The Crew (2019)
https://www.google.com/amp/s/wccftech.com/the-much-battered-...
Sounds like he has the best of both worlds holding the stocks and staying out of the board.
My answer to the first is yes. The second however is a bit more nuanced.
The first case is when employers find the best and brightest talent from all around the world and expect these employees to work together and deliver similar value. In this case I think globally fixed base salary * a cost of living index multiplier capped at 10-15% difference makes the most sense. You don't want the pay discrepancy here to be too large as these people work together on the same level. For example, using local market rates, a Bay Area employee will likely earn double someone in the EU for the same role.
The second case is when employers want to outsource work to a cheaper labor market. In this case, expectation is that the workers will not be of equal skill and/or the work can be done with little training. Another way to look at this, the relationship is more hierarchal. The HQ is managing the remote worker for work for example. In this case I think a competitive pay relative to the location's market rate make sense.
Not sure if eli5, but you can compress that message. Counter example: Huffman encoding that message.
The big blocker most monolith faces as the application gets bigger and is deployed into more and more machines is that _releases becomes a bottleneck_. Scaling monolith's applications are difficult because partial rollout is usually not possible as "services" are often tightly coupled.
Micro-service architecture forces services behind a set of APIs. While the APIs may have breaking changes, each can be independently deployed. In other words, teams can do releases at their own pace.
The main cost-benefit analysis here is how important is independent releases vs the cost of operational overhead?