Here at The @DuckbillGroup we have a new Principal Cloud Economist starting in two weeks. Guess who it is in a reply and win a @LastWeekinAWS swag pack.
Let the speculation begin!
I will point out that this person is subject to the infamous @awscloud noncompete.
AWS has a history of calling new employers to low-key threaten them out of not hiring ex-employees or restrict their work.
I'm thrilled to negotiate via hitting AWS with a chair: 833-AWS-BILL
AWS is welcome to tell me what types of work this person should not be allowed to perform.
I in turn will tell them what kinds of chair I have handy.
(Note that we are not asking, will not ask, and do not want NDA'd material. That's different.)
As pleased as I am to watch AWS attempt to dictate terms around a former employee they weren't able to retain, I'm prepared to make @IsForAt's press blitz look like a low budget PR stunt by comparison.
Sometimes it's vague threats around competing with the new company.
Please, AWS! Get better at cost cutting / storytelling!
Other times it's threatening partner status. Actually... threatening to make me an AWS partner would be a good threat.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Here at the @DuckbillGroup we're intentional about hiring. We're fully remote, we work largely asynchronously, and we solve fun / fascinating / maddening problems.
We're bootstrapped (no outside investment), so we hire slowly and with great intention / care.
There are two primary issues with hiring junior folks here.
A teardown analysis of the Duckbill Group's @awscloud bill for April.
Big spenders are RDS (up $200 a month), Fargate, EC2, Glue.
I previously talked about my Lambda Whoopsie that cost ~$80 more than it should have last month. That's a shame badge that's easier to pay than burn AWS credibility asking the Lambda team to fix it.
(I resolved the problem by discovering it was a JS callback / event loop issue so I rewrote the thing in Python. This is a Thought Leader Best Practice.)
The @awscloud marketing page isn't up yet, but the user guide speaks a lot about things that FinServ doesn't care nearly so much about (ETL and data lake issues) as they do other things (supporting insecure FTP from their partners for transaction data runs nightly).
This is a fascinating release, just because it focuses so clearly on a specific industry segment (a vast and lucrative one, to be sure; if you haven't worked in this space you'd be forgiven for underestimating it).
This is very clearly targeted to some customers, not the rest.