"The fix is diet and exercise" is not correct at all. There is no evidence on population level data or studies that diet and exercise produce durable BMI loss on a population level. From a "calories in calories out" perspective it is naively true, but in practice it doesn't work at all. The issue is that when people have BMI>30, their bodies endocrine system gets pretty messed up and their bodies will basically request 3500 calories per day. There have been a number of breakthrough medicines in the past few years that disrupt this cycle and reliably produce weight loss on a population level through hormonal changes that reduce appetite and delay gastric emptying. Some examples of these drugs are Tirzepatide and Semaglutide.
If you look at a bunch of variables, including BMI, and then you remove the impact of well known negative health impacts of obesity (prediabetes/T2D), then you see that high BMI doesn't not correlate well with mortality. IMO, what this indicates to me is that (1) BMI is not a good indicator of obesity in this study. There are many healthy people with low body fat and high BMI, I am one of them. All you need to do is be tall and lift weights occasionally. If you remove the obesity related negative health signals, you also remove obesity(2) Being fat in and of itself is not the issue, the issue is prediabetes/T2D which is extremely reliably caused by obesity, and the treatment for prediabetes/T2D is weight loss.
it happens with CTOs. At many companies, CTO is less of a management role and more of "the leader of all of the principal engineers and source of innovation for the company". VPE reports to CTO and does the administrative side of things, CTO sets technical vision. Most other c suite type roles are generally bucketed into sales, marketing, operations, and if you are particularly unlucky: product, "Information", and human resources.
I don’t think google has the capacity to become more efficient as an organization. Google is a strange mix of hyper capitalism and literal 5 year planning command economy communism. The thin interface of the company with rest of the universe, mainly made of legal policy, sales and vendor management is extremely efficient hyper capitalism. The huge gooey inside of this boundary layer, for basically all job roles, is a command economy where the inputs are determined by exec fiat, the results are interpreted through an extreme work politics lense devoid of nearly all market feedback, the consequences of failure are not firing but a 6 month delayed promo cycle, and everyone more or less is piggybacking on a more than a decade of monopoly profits. Google cannot become an efficient company again until market based success and failure mechanisms return to the inside of this massive company.
Ok, no one has given a good answer to this yet. The “internal valuation” is a 409a valuation and the primary use case is for the tax basis for options granted within 12 months of the grant date. Stripe gives double trigger RSUs so this won’t directly impact the large majority of employees getting RSUs, but they may choose to offer more equity for refreshers or new hire grants, this has little/nothing to do directly with 409a. 409a also is not used by investors to value shares, it has nothing to do with “mark to market” pricing of funds who own stripe equity communicating the value of their investment to LPs in the fund. There are 3 ways to calculate a 409a valuation, specified directly by the IRS, they’re all a very naive way to value companies, and once again the whole point is to have a tax basis for options grants. 409a vals are nearly always below the latest private financing valuation and it is generally in the employees interest to keep the 409a as low as possible for as long as possible to keep the tax basis as low for exercising options. The strike price in options directly comes from the 409a valuation, the basic idea is that (strike price) * (total number of outstanding shares) = 409a valuation. If you do this, the options the company gives you have no value according to the IRS so they are not counted as income. Thanks for coming to my TED talk.
It’s not just the parts though, it’s the expertise. Boeing has maintenance systems and programs that Russia does not have access to. The parts and schedules and materials are not really pirateable. The package needed is a combination of a part, a trained worker to do a job, a set of custom monitors/tools to do the maintenance (all owned and leased out by the US cos), and the custom parts themself. What Russia is doing right now is canabalizing their planes for used parts, which can only get you so far. Oil services is much more complicated and they’re production is going to decrease say 20% yoy for a long time as the oil services firms like schlumberger have withdrawn. I worked at an startup digitizing industrial maintenance SOPs for aerospace, oil services and manufacturing and have dealt with this extensively.
It’s a weird trick. Russia has more money but they can’t import anything so it keeps piling up. Their economy is shrinking +10% yoy because they cannot import the parts necessary to run a modern economy
You are incorrect. The bible does not support fetal personhood. The bible clearly gives fetuses a lower moral valence than a living person and discusses that an accident that results in a stillbirth is not equivalent to "killing a person". https://en.wikipedia.org/wiki/Judaism_and_abortion
A huge crash in crypto prices is a great thing for people working on regular old startup/Saas cash flow businesses. A lot of potential investment and a modest amount of talent has been siphoned out of the real productive economy into the crypto ponzi zone. I for one am excited that I will never need to think about some BS "tokenomics" story for my startup to sell to some investor and I am looking for a return to VCs that invest in businesses with solid growth, unit economics, and cashflow.
The best crypto grift was the neobank startups that were front ends for investing in anchor, a 20%APY crypto ponzi. Anchor crashed with Luna and all those startups kept their money in failed stable coins and have folded and failed to make payroll. They lost all of their money and all of their customers money. Woof
Talent is global now, but culture and time zones still matter. For the top 15% of companies and talent offshoring is less about “pay people less” and it’s more about “hire a team of 80 people in a year”. It’s extremely difficult to hire a team of 80 US based engineers in 12 months, even with top of market pay, even with fancy stock and remote work. It’s much easier to do this in Latam for example because there is more slack in the labor market.
[Levels are confusing, I was using the non amazon leveling where l3 is entry, l4 intermediate, l5 is senior, for this post I'll use amazon leveling, l4 = entry, l5 = intermediate].
> First of all, I think it’s disingenuous to compare a boot camp hire with any L5 engineer, regardless of what country they’re from. A boot camp hire should be compared to a new hire/L4. Doing an L5 comparison is moving the goal post, which I assume wasn’t intended on your part.
Lets look at this from the perspective of the Director/VP, you're looking at filling headcount in your org, 25 seats. Its May, and you're behind the targets that were given to you in January. You have easy to source from talent pools (intermediate level or fresh masters degree graduate L5 H1Bs from India) and bootcamp graduates (3 months of coding experience). Your budget can pay up to 200k/person, which is much higher than the going rate for either of these profiles, so comp isn't a problem. Your boss (VP/SVP) is largely evaluating you on your ability to staff your org and complete projects. Do you fill these 25 seats using L5 Indian immigrants, or fresh bootcamp grads?
The huge majority of H1Bs are given to L4+ (aka non entry level) engineers. These directors/VPs have headcount to fill and would prefer a productive L4 to a "needs a lot of training" L3 every day of the week. IMO the real issue here is that there is no rational incentive for any company to take on an L3 engineer now, regardless of H1B or bootcamp status. An L3 is going to join your company, receive 18 months of training where they are genuinely not worth what you are paying them AND they are a drag on your org, then leave in months 20-28 of their employment, usually shortly after a promotion to L4. So you put in 18 months and if you're lucky you get back 2 to 10 months of productivity.
Its not about the visa power imbalance, its that a person who graduates a bootcamp today will need about 4 - 5 years of highly focused coding to become as productive as the Indian L4/L5 engineer that they would be compared to in this real comparison. It's easy to hire inexperienced devs in the US, but inexperienced devs are not productive.
Shooting a gun into a crowd and not hitting anyone is also a "victimless crime", that doesn't mean it isn't high risk behavior that should be discouraged. The reality is that the large majority of drunk drivers are chronic drunks and drunk driving rules are pretty effective at taking them off the road.
because supply and demand matter, and units that are AirBnB'ed are taken off the market for long term rentals, leading to rents for locals rising higher than trend. Even given that in the perfect economy construction would keep up with demand, there is a ~5-10 year lag between demand signal and correction in construction (prices rise, new construction breaks ground, new construction opens, new constructions absorbs marginal demand, filtering from less expensive units to more expensive units, rent prices stabilize/decrease). 5-10 years is a sizeable chunk of my life and I would strongly prefer to not have a 5-10 year chunk of my life with elevated rents due to airbnb listings.
eh, in most cases I have seen, it is the product org that is dysfunctional, not the engineering org. The people who are paid to know how to make money are often not good at making money. That leads to poor morale, loss of trust of eng team, and the rise of bullshit work.
extremely incorrect. The benefits of cloud grow as the company grows. I've been in a few mega companies that from colo infra to cloud infra, it was a huge cost savings and helped enormously with product development speed.
Yea, this article isn't about that at all though. The article is about how the TSA has been crossreferencing amtrak passenger manifests with the do not fly list they maintain, and not letting people get on trains. This isn't about setting up security checkpoints.
The empirical evidence we have shows that unions consistently make these choices. There is a huge duplication of labor and responsibilities in construction unions, the trades, etc. The workers are trying to get the company to pay more money to labor, sometimes that means more increasing the pay per hour, sometimes that means increasing the total number of hours worked. I am pretty strongly in favor of germany style labor unions, sectoral barganing and labor codetermination. The caselaw and regulations around unionization in the US are bad and often lead to poor outcomes for workers and management.
Initial meeting
Tech screening
Case study/system design
Meeting with upper level manager
Meeting with peers
Doing 1 last interview on something the team felt was still and open question
The issue employers have with unions is much less about wage bargaining an almost entirely about the duplicative work/labor unions tend to lead to. As a hypothetical, lets say you run a widget factory. Line workers at your widget factory spend 6 hour of their shift making widgets, and 2 hours of their shift packing widgets up after they have completed making their widgets. A union comes in and will say "we can have experts in widget making, and experts in packing, these are 2 jobs, people who make widgets do not have the expertise to pack, and people who pack do not have the expertise to make widgets. From now on, we will have 2 separate job roles, widget makers and widget packers, and a packer will never ever be able allowed to make widgets, and widget makes will never ever be allowed to pack widgets". The company, which used to have a staff of 8 people who did both tasks, will now need a staff of 8, 6 widget makers and 2 widget packers. Seems OK right? Well christmas comes around and there are too many widgets to be packed, last year all 8 people were packing widgets 8 hours per day around the christmas rush, and there wasn't much widget making to be done because after christmas is low on sales. The company needs to hire an additional 6 temporary widget packers to pack widget and the 6 widget makers will be either idle or working with reduced efficiency. This increases the companies expenses with no real value created.