evntdrvn

thanks for the work that your team does!

What brand/models of contacts ended up working well with your astigmatism? I find that one of my eyes has issues with the contact losing alignment too frequently, and so I’m always looking for other options. Thanks!

I got a MSc in Controls Systems, spent over a decade getting crap pay for highly technical and extremely stressful work, then made a conscious decision to go to the bottom of the software Eng ladder and climb my way up.

Ended up getting 3-4x the pay for 3-4x less stress.

IMO it’s also difficult when you’re in the initial phases of a new company/product, because the system is evolving fast and that doesn’t play nice with single-table-design needing upfront design to work well.

I have had much better luck sticking to a plain old relational DB stack for those phases, because it’s fast to iterate, and then consider moving to single-table NOSQL when the system/DDD has “gelled” and traffic is starting to hockey-stick

If you raise issues on the asp.net repo and tag David Fowler, he's pretty passionate about removing allocations whereever possible :)

Michal Strehovsky rocks. I appreciate that he pushes the edge from within Microsoft :)

yup, unless that's changed recently. he and Nick Craver have been making some great impacts there.

Thank you to everyone at TS involved in this feature!! It will solve a big pain point for us re reserved CGNAT ranges that were causing conflicts. Cheers

nu acknowledged powershell as one of its inspirations, yeah!!

Ah thanks, jless is actually the one I was originally thinking of and trying to find! :D

There's also this awesome tool to make JSON interactively navigable in the terminal:

https://fx.wtf

ah oops thanks!!

if you look at the images in this particular patent of theirs, I think it helps understand what you're asking about: https://patentimages.storage.googleapis.com/93/1e/5d/6ad89e2...

Hope that helps!

icymi, Dave Cutler's got a great YouTube channel!

https://www.youtube.com/@DavesGarage

thanks, and also thanks for everyone's work on the SDK! It's very exciting for it to hit GA :)

The answer, as you might expect, is "valves" as part of the integrated MEMS :) https://patents.google.com/?assignee=frore+systems

Cheers!

I’m curious about this aspect that you mentioned:

> forcing a library provider to maintain familiarity with all their consumers' codebases and business areas

In my experience, this hasn’t been an issue—the library authors are inherently intimately familiar with how to accomplish transparent upgrades of any of their library’s API changes in a consuming codebase. Or if there are breaking API changes that make it impossible/infeasible to maintain the current consumer behavior, that’s a very useful signal that it’s time for the library producer to go back to the drawing board because the proposed library update has issues—before it’s “too late” to rethink because the library update was formally released :) Or at least, helps trigger a conversation between the producer and consumers to see if the breakage can be accommodated without too much heartburn, or if it’s a non-starter and a pun upstream solution that works for both parties needs to be discussed/implemented.

Overall, it really reduces the “library producer in their ivory tower releases changes without fully considering the downstream impacts, causing a crapload of burden/schedule slip for XX teams” issue. And when you multiply that by N library producers in a company of a given scale, it’s easy for app/service dev teams to have a lot of their time non-productively taken up just trying to keep up with the constant treadmill of poorly handled upstream changes. So removing the externality effect by having the producers have some “skin in the game” can really help improve the experience for the consuming teams.

hth

You’ll also see the first type referred to as “lightweight tags”, if that helps anyone :)

What I’ve heard from friends working at places where the monorepo model has worked well, is that it also involved a culture shift such that the burden of upgrading the consuming services is put on the shoulders of the _providers_ of the library, rather than the consumers. This implicitly brings along some benefits, like making the providers not cause excessive/unnecessary version churn and ensuring easy upgrade paths, because they experience the pain rather than it being externalized onto the consumers :) Also, good tooling helps—and I think that this model also encourages investing in that.

I have faith that it'll happen eventually, in some form

I just really really want someone to create a SQL Server offering...

I can't resist mentioning F# Units of Measure aka UoM :)

https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...

Hopefully this sounds like helpful feedback instead of annoying nitpicking: I found that the substantial "flash of unstyled content" when the page first loads to be very jarring/unappetizing. I think it would be worthwhile to investigate one of the approaches that can mitigate this FOUC effect.

Cheers and good luck!!!

On the flip side, within the last few years, upgrading .NET versions has become typically a very easy exercise.

The ASP.NET team tends to churn stuff wayyy more often than I'd like for questionable reasons, which can make keeping more painful than I'd like - but tbh I often just keep using the older ways of doing things in ASP.NET since it's almost always still supported...

“very competent experienced pragmatic X” is a good target for early employees

There's lots of people that would be willing to help!!

I know that the .NET CLR team adjusted its behavior to address this scenario, fwiw!

yeah Steve Sanderson is a force :)

I hope you can pass on my appreciation for Sentry's support of OSS authors and maintainers!

I was expecting to read “… a stork” lol