arpinum

Because I could write 5 pages filled with these potential factors and it would be confusing to most candidates. Why specify Welsh when less than 1% of staff or candidates speak it?

"level" can be an internal designation to communicate to others about the problems you can take on. Says nothing about pay. Many ways for a company to operate.

It's mainly specialties, not just levels. Are you a graphic designer that can also build your designs for the web? Were you previously consulting for our largest customer? Do you speak Welsh for our important client in Pembroke? Did you previously work in tech stack X and want to get back to it, and could lead our effort into that market? I'll pay more for these even if they come in at the same grade. Pay is very subjective, it is a prediction about the value an employee can or does bring balanced against their next best option.

No, work with a recruiter who understands your business and is similarly aligned to spotting value at a good price. By the time I have an initial phone screen with a candidate I know their CV and their salary expectation and I have agreed to be in range of their expectations. Direct inbounds go through a 10-minute screen with a recruiter to collect additional details.

I often look at a CV and notice specific skills that can benefit the business even if they aren't part of a normal job description. Imagine a software developer who used to be a graphic designer. I can save handoff time and have this person take on additional tasks, but it won't be in the job ad because the hit rate is too low. I can afford to pay that person more than others with comparable programming skills.

Or, I find value in areas that get overlooked in the market. Career transition people for example might not have many other options and I can take a gamble on how fast they ramp up.

This is about job ads, not their internal designation. I don't put out 8 different job ads when 2 are sufficient.

I can take multiple types of people, I'm casting a wide net to find value.

When hiring I don't have a narrow range in mind, it can be 50% or more. I look at the individual and make a judgment call on their impact to the business. For software we don't have a widget factory where employees are easily substitutable.

I've tried the opposite, paid everyone the same. But there were clear differences in ability and more importantly outside options. It became a problem when it came to retention and the business didn't have the ability to overpay everyone to keep the top performers.

I am not a normal case because I don't live in USA. The USA government estimates 50-80 hours to complete all my forms.

I have foreign income and foreign businesses, my partner has foreign income from two countries. The tax law is then based on tax treaties, most tax preparers do not have sufficient knowledge to complete a return, and tax software doesn't handle these cases.

The tax treaties are not clear, tax professionals will disagree on interpretation, and tax benefits in one country will not apply to another.

Then there is a thing called AMT, alternative minimum tax, which is a second way to calculate your taxes that you need to submit as well.

They changed the FBAR page recently, no longer an interactive PDF.

Correct, it first did it in a spreadsheet, then filled out 59 pages of returns and supplement forms and I printed and posted it. It also filed my FBAR.

I'm also in a non-trivial tax situation, GPT Sol did better than my specialist accountant this year. It needed a lot of steering from me and about 2B tokens, but that is better than spending $3-4k in preparation fees. Total time to prepare and handle steering was still less than I normally spend on tax prep with my accountant.

I think what helped is giving it 100+ pdf and csv documents of my full situation so it knew everything about me and could cross-reference with all my bank statements.

Oh, maybe they combined savings plan discounts and private pricing?

AWS private rates gives PingCAP ~47% off list price. Wonder which services got the biggest discounts? Unsurprisingly for a db company the cross-az traffic is 15% of their bill.

This is similar to how wind and solar actually work, except CfD payments are taken from consumers directly rather than indirectly through taxes. Price at £5 in summer - wind still gets £90. Wholesale price in UK has little relation to actual cost.

Selling Renault 5 in actual colours is smart, everyone notices them against the sea of grey.

Gives me hope for an inevitable electric Mazda mx-5 to not suck.

It's in Moscow, they have strong air defences.

luckily in UK (and probably EU) jam, jelly, and marmalade are all defined in law with specific sugar to fruit ratios.

They said they are profitable aside from funding purchase orders, they don't need capital to fund growth. If they said they raised in order to grow faster and that they were not profitable then I would agree with you.

20PB in 48 hours over a 1Tbps connection. Seems big enough for a lot of customers to recover their data or preserve backups.

They can likely fund the purchase orders for 10% while they grow. Sounds cheaper than giving away a percent of all future profits. This is very common.

Seems like a mistake to stagger these hits, doing both in the same hour could have taken out backups before they had a chance to replicate elsewhere.

I'm surprised they didn't go the debt route, trade finance could cover their customer orders. I know they are risk averse in case companies back out of orders, but bringing on more shareholders is its own form of risk.

Is something else going on here, are they locking in orders from AMD and other suppliers beyond their current order backlog?

Funny fact, DynamoDB local fails about 100 of my conformance tests. Mainly around error message formatting and text. Just be careful about parsing those.

Here are some bugs: - `ADD m.a.c :inc` update expression wrote a literal top-level m.a.c attribute but didn't change the nested number. - TransactGetItems returned fields not requested. - update expression can update the same key multiple times.

In total my conformance suite found 583 failures out of 1279 tests.

"46 at true 100% conformance". This is factually incorrect. Inspected their DynamoDB service and it comes nowhere close to implementing the full api.

Alternative theory - the board and new CEO understood their actions had high risk of termination and needed compensation for that risk.

In a JWT this is simple, the signature checks the entire sig and data sections. In XML signatures it checks whatever it says it checks, a list of URIs, which may also be transformed.

So it is possible to have an XML signature that points to an element that does not include some important piece of data.

SAML is even worse than the article describes, problems like needing to check what the signature actually signs. But I'm optimistic about the future, instead of relying on libraries that do a lot, such as general xml parsing, we can support a subset of SAML and only the dialects of the top ~10 providers. Extreme niche providers can be added ad-hoc and only if the deal size makes it worthwhile.