one func man

[one func man @onefuncman]

"Now that I’m older, doing well personally is not enough to get me up and going in the morning. I’ve started to focus on service to my community." - @RukaiyahAdams

[one func man @onefuncman]

@JoeDudekJD @Jungroan https://t.co/vgptYxF6SB

[Jared Short @ShortJared]

Numbers like this out of Quickwit don't surprise me anymore. We run it in Lambda functions and get sub-second on 10s of millions of records doing fairly complex aggregates on multi-field searches and filtering. It's wild.

[Doug Madory (also on Bluesky) @DougMadory]

From the Tortured Traffic Department:

Release of #TaylorSwift album leads to music streaming surge, according to @kentikinc traffic stats.
https://t.co/GN3opfw8SZ
#thetorturedpoetsdepartment

[🔎Julia Evans🔍 @b0rk]

inside .git
https://t.co/EgXbXrvDoD

[gray ❄️🫧 @graycrawford]

I realized chess pieces can be redesigned to be purely geometric attack directions

[one func man @onefuncman]

I just scored 177 in #FlapjackFwop! Can you beat me? https://t.co/KNDwhXjbcq via @cassidoo

[one func man @onefuncman]

@theburningmonk They have a waitlist / application process gating access to GPT4 via API.

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy In order for the lambdas to reach out to NewRelic — I was using a VPC endpoint to access DynamoDB up until then.

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy I only needed VPC for Opensearch at first, then I had to deploy lambdas into that VPC, then used my 2nd OS cluster as a chance to prove out the extraction from my stateless stack, and THEN I extracted the 1st VPC to another stack when I realized I needed to add NAT to both…

[one func man @onefuncman]

@theburningmonk They launched GPT4 with rate limits to prevent these attacks and keep access somewhat fair. It was 25 messages every 3 hours, I think you need tens or hundreds of thousands of messages to use this method

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy Fortunately I made my Opensearch environments completely ephemeral. Friends don’t let friends use search as the primary db. Still couldn’t get around deleting and recreating a vpc to fix nat issues though.

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy I’m still kicking myself over putting opensearch in my shared backend infra stack before I got the concepts a little more cemented in my thoughts I guess. Unresolved stack organization angst, ha ha

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy This follow-up article is what I meant by your caveats. Having worked with lots of AWS services, I can generally intuit which ones will cause trouble being commingled in a CDK project, but for newcomers I don't think it's clear between serverful, stateful and serverless services

[one func man @onefuncman]

@focusotter I've been tying stuff together with ARNs as StackProps out of laziness, but SSM works better than CloudFormation exports.

[one func man @onefuncman]

@focusotter I've been using a single stack for each CDK project but I split out to separate projects pretty quickly. Current project ended up with separate CDK repos per domain and/or team ownership, with one central "backend" repo for easily managed stateful components like Dynamo tables

[one func man @onefuncman]

@theburningmonk @focusotter @MrConerMurphy I've had trouble reconciling what you say your position is vs the caveats you express around RDS, OpenSearch, etc. I separate stacks based on what things should change together or not. f/e, I never want my OpenSearch stack to change when I'm changing the lambdas that index docs

[one func man @onefuncman]

@NatTowsen Weird Al Yankovic, full stop.

[one func man @onefuncman]

@andrew_westwick @BrantAshe #sorrynotsorry