nieksand

It seems like this policy would lead to shortages in less common sizes of clothing.

Nor will human generated market research.

Unexpected, runaway AWS cost is a real problem.

"Tunable spending limit" has consequences that can create other, equally real, problems.

Best effort: Turn off all compute resources, drop dynamically-adjustable persistent resources to their minimums (e.g. dynamo write and read capacity of 1 on every table), leave EBS volumes and S3 alone. In some cases, a user might find their business effectively offline while still racking up a massive AWS bill.

Hard cutoff: Very close to deleting an AWS account. In addition to compute and dynamically-adjustable resources to minimums, this means deleting S3 buckets, Dynamo tables, EBS volumes and snapshots, and everything else that racks up cost by the hour.

The best effort approach sounds reasonable to me. The hard cutoff solution sounds worse than the problem it purports to solve.

Agreed that AWS is poorly incentivized to fix the problem.

What semantics do you expect when your spending limit is hit?

Turning off all compute resources (EC2, Lambda, Fargate, etc) seems obvious, but what about systems managing state like S3, EBS, and DynamoDB? Should buckets, volumes, and tables be deleted?

I find it fascinating that this article only calls for young men to change their behavior but demands nothing of young women.

I think periodic off-sites (or on-sites in the era of remote) are incredibly valuable even without a specific business issue to address.

It's easy to say that strategic thinking and planning should be continuous, but in reality there's always a storm of immediate tactical tasks sucking up your attention. That's true for both software engineers (living in Jira tickets, sprints, and one-to-two quarter projects) and the c-suite.

These sessions can force you to make time, put aside the tactical noise, and think.

My last use of FogBugz was in 2012. After replying to FogBugz's fake bill, I noticed an auto-reply in my gmail spam:

Title: "Notification - Please visit support team"

Sender: "Sales and Success"

The short body declares that I have to go to their support portal.

I can't tell whether this stems from incompetence or if their aiming for Spam on purpose. Given their behavior, I assume the latter.

You could work your way through some of the "Linux Programming Interface" by Kerrisk.

Even if you only use high level languages, the LPI provides insight on what's happening under the hood. It also gives important context for when you do performance analysis and program optimization. Each chapter has a bunch of exercises at the end.

I've heard that publish-or-parish is a challenge for all theologians.

The questionnaire looks pretty reasonable, but I'd be concerned about the sketchy looking "Psychometric assessments" that's next in the list.

Also, at what point will the candidate be able to vet whether Canonical is a suitable match? Is that only after this questionnaire, psych test, and take-home assignment?

Building first and talking after isn't likely to end well, especially for B2B. Trying to buy online ads after the fact is not likely to get you anywhere... you are just one of a million voices screaming out in a crowd.

If you don't feel comfortable talking, consider partnering with somebody who does.