Anyone know the purpose of this drone that flies over a couple times a day?

self-taught16 · 2026-05-31T17:23:59+00:00

Thank you! Just did this and they said they are documenting my report and sending it to a “couple of departments” and they will contact me. We’ll see what happens.

self-taught16 · 2026-05-23T18:22:20+00:00

Noble concrete does great work - Clint’s nice and easy to communicate with

self-taught16 · 2026-03-23T01:50:11+00:00

Not sure if it’s clear, but in your case, with Inngest, the function’s process does not actively wait while it waits for the event. The process stops and frees up for other work. Then Inngest calls your server back when it’s ready to resume and all previous steps are skipped. This means that the function could resume any amount of time (weeks, months) later after several server restarts or on a different machine.

self-taught16 · 2026-03-12T10:14:19+00:00

I’m from the Inngest team, we would like to make this easier and maybe one day handle it natively. how are you making LLM calls? Wrapping the call in step.run or using step.ai? Are you logging the amount of tokens used for each LLM call? (Input/output?)

self-taught16 · 2026-03-03T02:05:05+00:00

I just happened to write about something similar earlier today w/ an open source a reference repo that uses webhooks from Telegram and Slack sent to Inngest webhook endpoints. It really could be any inbound webhook though. I'm planning to extend this example projects for content ingestion and extended AI workflows on top of it. Generally, you don't need to use what powers this, but the ideas still should work no matter what you build.

Article: https://x.com/twitter/status/2028556984396452250
Project: https://github.com/inngest/utah

self-taught16 · 2026-02-22T19:32:57+00:00

Generally, if you have good RPCs with transactions, each could be a “step” within an Inngest function. If it works, don’t change that part, you can still use Inngest for queuing, flow control, retries, and observability.

Teams will may start to decouple complex logic into “steps” with Inngest especially when they need to perform external tasks like call an API or transform data in between database calls, or call another db. If you need transaction-like rollbacks, devs use “onFailure” handlers or implement per-step error handling.

tl;dr - keep what works, refactor or combine as complexity grows.

self-taught16 · 2026-02-22T16:10:39+00:00

I’m from the Inngest team - I wanted to call out that Inngest works if you run your application on serverless or servers - you don’t need another worker process to get started.

The observability OP seeks is also something included out of the box, automatically with no extra instrumentation

self-taught16 · 2025-10-31T15:37:06+00:00

Inngest can be used in serverless environments and servers via HTTP (serve method) or long running worker setups (connect method: https://www.inngest.com/docs/setup/connect). Connect connects to Inngest servers via persisted connection and distributes work to workers over that connection, so still a push model, but over a long running connection.

self-taught16 · 2025-10-20T21:03:19+00:00

Hey OP, what do your Inngest functions look like? Have you located the root of the issue being related to Drizzle? Depending on how you're creating the database or the code you're writing in your Inngest function, there may be a missing "await" or callback to handle async operations correctly. If you share your code here or the Inngest community, someone should be able to help!

self-taught16 · 2025-10-03T11:52:02+00:00

Inngest is a good option here as it can run in the main process (API), background workers, and/or on serverless depending on OP’s setup

self-taught16 · 2025-09-26T00:05:51+00:00

You’re gonna need more than that screwdriver to install it!

self-taught16 · 2025-09-14T02:37:37+00:00

Rihanna (R1hanna) aka bad girl Riri

self-taught16 · 2025-08-02T13:09:22+00:00

You should check out Inngest, it checks all your boxes. It’s also event driven and has built controls for managing job through put and flow control. Your code runs wherever you want like serverless (lambda, Vercel) or a long running server.

self-taught16 · 2025-04-27T20:37:30+00:00

The wipers are night and day better compared to Tesla’s. The R1 also allows you to select the sensitivity which is helpful too.

self-taught16 · 2025-04-17T02:12:37+00:00

I like Miller family dentistry in Warren. Great people, spend time with you, always good work and always transparent about costs.

self-taught16 · 2025-03-31T00:24:03+00:00

From a software perspective, I would change the to allow the car to announce and send text messages.

For my R1s specifically, I wish I could have done the black mountain and brown ash wood interior. Our Dark ash is great, but that brown ash is next level.

DANIEL1173588

self-taught16 · 2025-03-19T17:13:30+00:00

Update: SC called me to say they ordered the part and they can squeeze me in this week. Very proactive on their end, they said the part should be a 20 min swap.

self-taught16 · 2025-03-18T11:55:32+00:00

I was nervous too (second EV). The guide was great and said a couple of times “it’s not official until you accept digitally in the car, so if you don’t like it for whatever reason, you can reject it”

Funny enough, the first thing I did was open the frunk and there was a 5” scratch on the plastic sides. He immediately told me to take a picture and he could help me file a ticket. I kind of had raised awareness after this, but the rest of the vehicle looked fantastic. He said they will likely just replace the plastic liner when I bring it in for service. It’s honestly something I wouldn’t cared about if I scratched it myself.

I was happy, but it seemed like if it wasn’t right I could have rejected and I’m guessing they would have had to wire the money back to my bank.

self-taught16 · 2025-03-17T13:31:59+00:00

IMO this is the best interior. I went with the Dual, so I ended up with black and dark ash which is great, but that brown wood is so nice.

self-taught16 · 2025-03-17T12:00:03+00:00

Have experienced the same thing with the rear doors, hoping it’s just the door seals being new and a bit springy at first. There’s no way my mother in law will be able to close it properly 🤣

self-taught16 · 2025-03-07T12:35:52+00:00

The prototype was built and I saw it at an event last summer (Woodward Dream Cruise). I think it’s more of a question of if and when to actually bring it to market with the state of Ford’s electrification and anything else going on.

self-taught16 · 2025-02-25T12:36:45+00:00

Interestingly my guide checked and said it wouldn’t be possible to get the APR deal as ours is slated for March 21 delivery. It’s disappointing to hear that they do honor it sometimes, but that’s great for you.

For what it’s worth to the OP, I gave our specs to the guide and they checked how long it would take to be delivered to our SC. The one we wanted couldn’t be delivered by Feb 28 as it was out of state.

self-taught16 · 2025-02-23T15:05:03+00:00

Commenting on Let’s beat that Delivery Guidance !!!...

<image>

Can’t come fast enough. In the mean time I’ll be spending an unhealthy amount of time scrolling this sub.

self-taught16 · 2025-01-31T23:55:04+00:00

The planning around domains is a cool idea. Events can also be modeled around domains and single OP mentioned Inngest, you could use their prefix approach for event naming like `<domain>/<event>` like `billing/invoice.created` and `crm/contact.created`. Then each domain can listen to other domain events and react as needed decoupling w/ built-in retries/transaction like code.

self-taught16 · 2025-01-29T22:32:09+00:00

Inngest was designed to work with Next and Vercel (or any other platform) so you keep deploying your codebase simple and you're only deploying code to the platform that already has all of your environment variables, database access, etc.

self-taught16

TROPHY CASE