a union is not an unalloyed good for the employees. I also worked at a unionized grocery for about 3 months. At our shop, it was clear that the union was set up to protect the senior employees at the expense of the junior employees. There were about 10-ish people on the checkout stands during my shifts, 4 of them were employees who had been working there for 10+ years, and 6 of them were people who had been working there for less than a year. The senior employees worked maybe 15% of their shift when it was particularly busy, otherwise they'd have "meetings" in the break room or hang outside smoking. The junior employees were worked hard and burned out and left.
The point is, the things that make the economy work and grow is the production of things. Regardless of how many investments a retired person has, they by definition do not produce things.
"Oligarchs" are people who were friends with Boris Yeltsin in the 90s. USSR was collapsing, government upheaval, etc. In this period, the government of Russia sold off state owned enterprises for extremely cheap prices, fractions of a penny on the dollar, to Russian nationals. The state owned enterprises were things like mines, shipping companies, iron smelting, etc. The people who bought these state owned enterprises are "the oligarchs". They have extreme political power in Russia and own or have monopolistic control of huge parts of the Russian economy.
Car ownership is highly correlated with income, people in the bottom 10%ile of income are much less likely to have a car than people of higher income. If you look at modeshare for people in the bottom 10% it’s a much much larger share of biking, public transit, walking, and carpooling than others. Cars are one of the top sources of bankruptcy for people in the bottom 10% of income (car repairs, car accidents, making car payments). Car dependent life is a huge stressor to people in the bottom 10% of income
The benefit of 1 shot is very high for the first 6 months, it prevents the large majority of hospitalizations and deaths, but it does not prevent transmission. The decision to have a 1 month period between doses was determined by "time to market" not the ideal dosing schedule. Had drug makers tried to optimize for the ideal dosing schedule, then we would have had 6 more months of deaths while we waited for result which was a negative outcome. Now that the drugs are on the market, and we have sufficient evidence without running an additional stage 2 and 3 trial, the FDA should change guidance to suggest 2nd dose at 6 months instead of 1 month for people who aren't at high risk.
The main issue IMO is that the original dose schedule of 2 doses 1 month apart is stupid, goes against pretty much all of our first principles understanding of immunology, and was driven by a regulatory need for a short time window for testing/deployment (it’s quicker to test a vaccine w 1 month window than one with 6 month window), not due to science. The optimal dosing schedule is more likely to be once mRNA vaccine and a second one 6 months later. Source: family member is a chief scientist at a few drug discovery startups. Most people will have a durable immune response with the schedule above.
Defaults matter, and defaults encode the behavioral choices of like 80% of users. The downstream effects of this are that the default options have the most support. Its totally rational to complain about a bad default option.
The issue is that the 3x cost doesn’t include the cost to staff the team that runs your in-house platform software on your colo setup, and the mixed incentives you get when a sizable part of your team is not shipping product but instead shipping say, Kafka queues. My previous employer has one of the largest colo deployments of the f500 companies and it was a mess technically and organizationally. At the end a few hundred infra devs were laid off and projects scrapped after ~24 months of no visible progress on platform stability and support.
The issue with low APRs on high risk short term debt for consumers that need it is that it generally makes it expensive to issue the debt almost regardless of the risk of the person.
Hypothetically if you need a $700 payday advance today, paid back in 2 weeks when you are paid, a credit card level (25% apr) would be an extremely small amount of money paid to the servicer (like 7 dollars total).
The other thing you don't see is how stupid the p05 patient is. Its not someone reading primary sources or coming in well informed. Its someone coming in saying Dr Oz says that eating blueberries cures cancer.
1) Founder/cofounders
2) investors
3) people who do not work at the company and are not investors that people in groups 1 and 2 think will be on their side during important votes
I’m a remote team manager and I’ve considered putting tracking software on low performers computers, and have not gone through with it yet. I’m super happy to put in the time to coach someone who is trying to make it work but if they’re putting in 2 hrs/day on a remote job and not making the cut it’s not worth my effort to try to coach them out of that.
yes, I personally am not into gaming at all. "Among us" is a goofy game that I'm terrible at. I've found that having some structure to hangouts by having a very simple thing to do together has made the actual bonding part much better.
You sign an offer letter, not a contract. Its basically a promise that if you show up on a given date that your employer will give you the necessary documents to sign to start employment, and what the terms of employment would look like. There is no legal protection for candidates who have had offers rescinded. Employment in the US is 'at will'. You can leave with zero days notice, your employer can fire you with zero days notice.
you create a graphql API spec and amplify builds all of the appsync resolvers and dynamo tables for you. Pretty good support for different auth methods and table schemas.
Looking at the newest version of the docs it seems they are indeed deprecating some of the weird niche features and doubling down on the things that already work well.
My team (5 engineers, 18 months building so far) currently runs the largest amplify based project in terms of number of resources used. We have a direct connection to the core team and their support has been great. Things were quite rough until about 6 month ago. The new releases in version 7.5.x unwind a ton of technical debt that caused serious instability. If I were to start our project over again knowing what I know now I might use SAM or the serverless framework instead of amplify, but I am not sure. The graphQL spec definition to dynamo table feature is the entirety of the magic in amplify IMO, and it has seriously sped up our development time. I strongly recommend against using any of the UI components, or many of the features that appear to be "tacked on the side" because in my experience they are tacked on and don't work well. Happy to answer any questions.
I'm not saying this is a super common thing, but I am saying this is going to happen more than it used to happen. We routinely see people who want start dates 3 months after offer acceptance, they want to travel, take time off, spend time doing hobbies. Its great! Maybe 1 in 20 times the team that person was accepted to ceases to exist in that 3 month period, and the company doesn't want to or can't rematch them to another team because the job literally doesn't exist, their skillsets aren't needed, maybe the hiring manager responsible for the hire left and there is no one who is the "champion" of the new employee/prospective hire. The reality is your job doesn't exist for you and has no legal protections until you sign your onboarding docs on your first day, and even then its at will employment.
It's a transactional relationship. I have had a few candidates pull out after signing for various reasons (some personal issues, some for better offers). If they apply a year later, I would likely still give them an offer. There are no "permanent black marks" on you, at worst it is a note in your candidate CRM in one specific company that won't follow you elsewhere and won't impact you at that company after 12 months.
I'm not saying we should normalize it, I'm saying in a world where senior engineering talent is routinely paid 400k+ USD comp packages is a world in which employers will be extremely picky about who they give those 400k comp packages to, and if the business use case doesn't shake out in the small time between offer acceptance and joining the team then naturally these businesses will pull out more frequently than they used to pull out. I'm not saying its good, I'm saying its a consequence of very high pay for engineers.
Engineering and tech compensation packages are increasing extremely quickly. Engineers in particular have market power to get great jobs with high pay. In an environment where the rate companies pay for labor is increasing, we're going to see more companies do things like rescind offers for shifting business priorities (or something wild a candidate said after offer acceptance, which has happened to me) or fire people after a few weeks at the company for non performance/poor match because the cost of maintaining an employee on payroll has increased and the consequences to that individual have decreased. At a high level broadly speaking the consequences to the employees are decreasing over time (its easier to change jobs), the consequences to the company are increasing over time (compensation is increasing). As an individual, you are directionally incentivized to behave more like a free agent/mercenary than you were 4 years ago, and its only going further in that direction. Just move forward and live in that future, its a good place for all of us, just realize that that is where we are now and behave accordingly. Most companies won't _really_ care if you sign and then rescind your acceptance if you get a better offer. It won't destroy your career it will likely be good for it.
You don't need to launder money through GBTC to get exposure to the assets that money launderers use (BTC) to launder money and reap the upside of a growth market in cryptocurrency based moneylaundering. its a smart play tbh, but the 99% off chain economic benefit from crypto today is money laundering, evading KYC protocols, tax evasion, ransomware related transfers.
marketcaps in crypto mean nothing. The universe is full of wash sales, there is not 2.6T of liquidity, a ton of volume is insanely leveraged and amplified through defi pools, and looking at a transaction volume adjusted view of the world, like 99.9% of transactions are valueless gambling OR money laundering. Lets see what happens after the run on tether happens, then we can talk about what the crypto world looks like.
By increasing value like this, they can raise more funding/sell debt to fund growth. The moves themself do not impact the company but the downstream impacts can be great. Most large businesses run on debt, most growth is fueled by debt, and increasing the total amount of money that investors are willing to give to companies by reorganizing organizations to make more attractive debt sales is a nearly costless way to fund growth.
This isn't true at all. Its obvious for a senior/staff/principal engineer to claim that their skillset is infinitely transferrable to any job role that needs a staff level skillse, but its simply not true. There are tooling agnostic skills you learn (managing complexity, upleveling team members, how to actually be a technical leader and make improvements that a manager doesn't explicitly tell you to do) and there are tooling specific skills that you need in an organization (EX: dependency management in java, performance issues in certain DBs, the unwritten/not explicit API issues in different cloud platforms). If I am hiring for a staff engineer, I will be trying to get the combination of "tooling agnostic" staff engineering skills AND "tooling specific" staff engineering skills for my job opening because you don't end up paying more for an engineer that has a well matched "tooling specific" skillset, but they will be more productive. The net cost to me as an employer is simply time, I might need to source 3x the candidates to get a good fit, but its worth it.