shoelessone

I really really want to use OTel for a small project but have always had a really tough time finding a path that is cheap or free for a personal project.

In theory you can send telemetry data with OTel to Cloud Watch, but I've struggle to connect the dots with the front end application (e.g. React/Next.js).

Honestly this makes me feel good, just because it always worries me that I don't see this type of issue being resolved more often. having to physically bring in a car seems like a near worse cast situation but it's good to keep this in our minds as a possibility.

I am by no means an expert, but I wrote up a bunch of words on how I did this personally for a family Xmas present here. The tl;dr; is a custom PCB in my case: https://kevinmitchell.io/blog/mitchine-esp8266-wooden-thinki...

There are so many articles these days posted on HN like this recently but I'm realizing I am too far out of touch with the technology to be able to appreciate it.

Any recommendations as to how I get a bit of hands on experience in the AI "domain" so when I read some news articles like this it means something more to me? Or is this type of thing really only relevant to a very small subset of software people?

Anytime these discussions come up I always wonder if there are any great examples in the form of a deep technical analysis of microservice architecture?

I've built things that I've called microservices, but generally have failed to do a complete job or always left with something that feels more like a monolith with a few bits broken out to match scaling patterns.

I know there are talks and papers by Netflix for example, but if anybody knows if any smaller scale, easier to grok talks or papers that go into common pitfalls and solve them for real (vs giving a handwavey solution that sounds good but isn't concrete) I'd love to check it out.

I have no first hand knowledge of this but I've heard that colonoscopies are very common in S. Korea, even starting at younger ages.

Can anybody comment on this?

This is very interesting, I held the same general belief as the person you're responding to.

Any chance you have a source for this info?

This seems like a nice option to have, and I appreciate the thought put into it.

Personally I think I'd prefer to decouple my email / phone / etc from the ownership of some credential / identifier. To me it's cognitively simple that I have a domain name, and to prove that I control the domain I have to make some change to the domain. When I say (type) it out loud it does feel a bit archaic, but to me it's simple.

It would be convenient if by clicking a validation link or something sent to my email (to prove I controlled the email in the domain) I could verify ownership. But: What about something like AWS Route53. A fairly complicated "enterprise" system for authorization is in place allowing certain team members to make changes to a DNS record in AWS. The people in the organization will change over time, the list of who "owns" a domain might be ever changing. Of course the organization itself might own the domain, but perhaps there isn't a clear single email address to assign ownership to. If the Domain Verification spec required everything to render down to a single email address or phone number or whatever, it feels like it adds potentially complicated questions to how do you distill AWS access down to an email address or phone number? It just feels like the actual service validating the DNS info is potentially taking on a lot of responsibility / complexity with implementation.

There is a lot of discussion here about how Angular is a good choice for larger enterprise applications, but as somebody with more of a "backend" set of experiences, it seems to me that Angular might be a better choice for smaller teams as well?

My struggle is that when I want to build even a simple frontend with React, if it's been a while since I've done any frontend work I find myself having to re-learn what the current set of libraries / tools / frameworks I should be using with React is. For example, if I want a three page simple website, how do I handle routing, is it still `react-router-dom`?

This is what I'm most interested in.

I'm hopeful about Tesla FSD, and don't think it necessarily needs to be perfect, just significantly better than humans. So I'm rooting for Tesla FSD/Autopilot overall. I just don't see how given the findings there is a solution without removing removing the entire FSD feature.

I dabble in electronics and have made a few PCBs over the years with success. That said, each and every time I get back into it I find I've forgotten everything I know and start over at the same place each time: Jeremy Blum's Eagle tutorial on youtube. It hits all of the key points I need to know from starting for the very first time to actually sending my part off to OSHPark or whatever.

Is there a similar resource for KiCad anybody might recommend? It's been about two years since I've done anything with electronics (I really do forget almost everything) so the gentler and broader the better.

Can somebody tell me the difference between `ESP32-WROOM-02` and `ESP32-WROOM-02-H4`?

I'll admit I just skimmed this article and don't know the source, so happy to be shown the light, but I seriously doubt it's because no one cares. https://www.ri.se/en/what-we-do/projects/replacement-of-carb...

Sorry if I missed it, but is the color material some sort of epoxy type product? When I've seen these in the past I sort of assumed it was either epoxy, plastic, or some sort of ceramic that was put through a kiln. But I didn't see any curing or finishing process. Anybody happen to know?

This looks great, but sequence diagrams are one of the things I use most with PlantUML. Most commonly I find these super useful to document various caching scenarios, and I use them all the time to help explain payment processing flows.

https://text-to-diagram.com/ says the sequence diagrams aren't supported, but your github description says

> D2 intends to integrate with a variety of layout engines, e.g. dot, as well as single-purpose layout types like sequence diagrams. You can choose whichever layout engine you like and works best for the diagram you're making.

Can you explain a bit more about this, if I wanted to create a sequence diagram with D2 today is there a simple path to follow to do this?

Thanks for the work on the project!

I'm interested in what you mean by "setup script" - I assume you have a script of some sort you run when / if you re-install the OS? I'd love to hear more about this!

This article is helpful for understanding OTel, but I still always get stuck at understanding the differences between collectors and exporters. I might wonder "why doesn't the SDK just send data directly to an exporter? Or "isn't the collectors job to export data to the exporter?"

I think a few simple examples that explain at high level the reason or need for the architecture would be really useful. Maybe something like "here is how OTel fits into a typical serverless application."

I find it a lot easier to find a Docker container with whatever service I want to use vs trying to figure out how to install it locally. Nothing super exotic, but currently I'm running OpenSearch and PostgreSQL in a VM (via Docker).

I wasn't aware they did this. Any chance you have an example of this?

I don't believe this solves the issue if your IP changes all the time.

Can anybody speak to how this story relates to prions found in deer (and so venison) in Michigan and the Midwest? My family are hunters and now send all deer to be tested before eating, but most don't.

Same (blue) boat here.

To be honest, how Cloudflare Workers work is a bit of a mystery to me as I've only done some very basic prototyping with the service (and not really focusing on the "edge" aspect of them), but it seems like the important "stuff" that makes them what they are is how they are deployed.

I am REALLY going to show my ignorance here, but is there some chance that the idea is these "workers" are intended to be deployed in the users browser for example, as actual service workers or something? i.e. is this more of a framework for creating service workers vs running in the "backend"?

This reminds me of how much I love PlantUML.

Was Girlfriend similar to this?

I'm assuming you're talking about CMS in this "space", which is to say likely used by small to medium sized companies. Others have spoken to that already.

That said, just to make sure you're aware, some companies pay hundreds of thousands if not millions of dollars (I don't know first hand about millions, but I know hundreds of thousands is easy and I'd easily guess million+ isn't unheard of) annually just in licensing for "enterprise" CMS.

I think the point is at no point is it acceptable to be in a position to be able to do something deeply damaging to a company with something as simple as a intern leaking a password. The intern should never been put in a position where this was even possible.

I’d say in all the ways that matters this was basically everybody BUT the interns fault.

I 100% agree with your statement. I also realize you are not championing HATEOAS here necessarily.

That said, I am curious if you have found this "linking" aspect of HATEOAS useful for actual implementations? I have been doing integration work with a system that strictly adheres to "REST level 3" and "HATEOAS" principles for the past few years, and I myself have found the "explore-ability" of the API super handy. That said, the self-documenting nature only goes so far, and in the end I'm not sure the internal linking stuff is preferable to robust documentation.

I'm not trying to be down on this necessarily, I actually generally push back on the adoption of GraphQL as the answer to every problem.

“ミッチン“ - an “IoT”ish Christmas present built on a bunch of AWS services with cement, MongooseOS, ThreeJS, React and basically the kitchen sink. I’ve been working on and off (but mainly off) for the past few years. Even the blog post is half baked (also quite long) :(

https://kevinmitchell.io/blog/mitchine-%E3%83%9F%E3%83%83%E3...