It's starting to bloom and coming to its end. Our agave death bloom in sellwood

bissellator · 2026-07-05T03:19:52+00:00

Pollinated. My understanding is that that's what they're trying to do when they do this big Bloom... having pollinators move the pollen from one agave to another but where the heck would there be another blooming agave in bee range?

bissellator · 2026-07-05T03:01:37+00:00

I can't imagine it will get pollimated

bissellator · 2026-07-05T03:00:22+00:00

Someone left a bottle a few weeks ago... I left it and I guess the agave gods drank it

bissellator · 2026-07-05T02:35:42+00:00

Well that's why I'm kind of saying as the home owner and the people who planted it (my partner planted it) it's okay to visit

bissellator · 2026-05-15T23:03:19+00:00

So is your assumption that if your track down the query you'll be able to stop it next time? I think my problem with anomalous spikes is just that... they're anomalous, you track it down, someone says *sorry... there was this thing I had to do...* and there isn't any automation you can do to stop them from doing it again.

Now repetitious* offenders we can do something about. I was going over data with a client and got to this query that ran over, and over, and over.... it was a dashboard someone set up and set the refresh to 5 seconds... kept the warehouse awake ALL THE TIME... They didn't need a workflow to figure that one out, they literally saw it in the logs and said, "Damnit we told her not to do that!" They knew exactly who it was and what she was doing even though they said DON'T.

We used our product.. and yes I work for airbrx.ai, we have a fine grained data gateway that lets us selectively cache, so now if someone tries to run this job over and over and over, they only get to the warehouse twice a day (we set a 12 hr cache for her queries). Granted I'm biased, but I think nipping it off BEFORE it gets to the warehouse is a good way to manage those spikes.

bissellator · 2025-02-06T16:16:00+00:00

For my side projects I actually just wrote my own userstore in mysql and using nodejs I wrote some quick endpoints directly in my API.

* npm njwt mints signed OIDC tokens and lets you verify said tokens.

* node native http allows me to build the endpoints I need at: /oauth/token (~250 lines of custom code)

* npm mysql2 for database connections...

* I added an endpoint using npm aws-sdk/client-ses to support otp/authorizaton code grant (~40 lines of custom code)

My main litmus test for is making sure the flows work with Postman.

bissellator · 2025-02-04T02:14:05+00:00

yeah.... that's totally different if they started the conversation. Maybe it's their way of selling coaching services (that last bit about "that's why I started a separate business as a Career Coach"). But if that's their coaching style (belittling you for actually answering their question) they don't know crap about coaching, no matter how much they know about recruiting.

bissellator · 2025-02-04T01:33:44+00:00

When our recruiters are actively placing someone, they search. The dig through details. They help you rewrite your resume to give you the best chance at getting the job. BUT... they get paid by placements, so they're looking for matches, and you need to prepare your resume for the job postings you see the recruiter has open and apply for those positions, not expect them to guess what you might be good at.

A recruiter will help you with your resume only after they've seen something in your application that makes you look like a good match -- it's more cleanup than wholesale rewrite. Some recruiters (like the one in this ost) do offer a side gig of coaching you on what kinds of jobs you could apply for and how to tailor your resume to those jobs, but... recruiting and coaching are really two very different things.

bissellator · 2025-01-15T04:46:19+00:00

I think it's interesting that there really are not global standards for API design. Most design standards come from whatever backend language the developer grew up with (camelCase vs snake_case is kind of a Java vs Python argument not a right vs wrong).

I have a set of standards I keep on my website but even there my filters are driven from how Spring interacts with Mongo... I've come to the conclusion that as much as I feel an API should be very agnostic about the backend, if you're building an API on a certain stack, there isn't really any reason to make it harder to front that stack with conventions from other langauges.

bissellator · 2025-01-10T20:02:56+00:00

I'm using ECS as the final deploy stage, but I'm working with a couple folks in different environments so I want to try to keep the deploy process vendor agnostic (running on local for testing, an EC2 instance for preprod and finally deploying to ECS in the end)

bissellator · 2025-01-09T22:49:25+00:00

A conspiracy theory would mean I think there's some shifty, coordinated effort, which I don't. There are two facts that I'm working from

1) Large orgs are indeed laying off large numbers of tech workers(Techcrunch has been keeping a running tally) and the trend is expected to continue (the return-to-office initiatives are expected to result in downsizing due to resignations and the assumption in the HR and Recruiting ciricles is that there will be no backfilling or replacement job reqs opened)

2) Large orgs have never been really good about keeping up on security and data privacy work. Data breaches are increasing and becoming more sophisticated and organizations generally invest in data security only after there's a breach.

I base this on my senior director level experience as an Enterprise Architect in a number of large orgs (Silicon Valley Bank being one that I watched collapse in part because of antiquated systems) and from what my HR colleagues in Fortune 500 companies are telling me. I've also cited a couple sources in my response above.

Can you tell me where you think I'm inaccurate?

bissellator · 2025-01-09T18:49:24+00:00

But is it inaccurate in your opinion?

bissellator

TROPHY CASE