eYrKEC2

Here's the recipe.

1. come in on Monday and need to solve some stupid problem with a stupid regex

2. Ask a question about negative lookbehind or negative lookahead regex syntax in python and why it doesn't match the text you thought it should, because.... it's Monday.

3. Have people virtually spit-take all over you and heap their scorn for a n-millionth duplicate regex question.

Enjoy!

@bcantril,

Although it sounds like migrating to another DB is not a good choice for Oxide _today_, why didn't you start with yugabyte db? If you were starting from scratch today, which one would you choose for your situation?

See also https://peterattiamd.com/xylitol-and-cvd/

External play stores can't come too soon.

His contrarian post got to front page of Hacker news. I think he won. His message to redirect funds to sub-maintainers is being heard.

My conversational skills really increased by going to lunch with people every single day instead of staying in my cubicle over lunch, working or watching YouTube. I'm very thankful to my boss who made this part of our group's culture.

a.k.a. "regulatory capture" - https://en.wikipedia.org/wiki/Regulatory_capture

Peter Attia had an interesting post about this study - https://peterattiamd.com/xylitol-and-cvd/

The one thing I like the most when I'm hungry is an I.T. problem.

Dual boot Linux and windows isn't a big deal to me. Doing it for 10 years. Only boot into windows for some games.

Advocating for graphql as a red flag. I like it.

It may not be an exact analog, but "swagger UI" for openapi is the best I've seen like GraphiQL. Example https://petstore.swagger.io/ . Not sure of other alternatives.

No analog for "subgraph federation systems", unless a load balancer will suffice.

Taking complete systems off the shelf and using them smells a lot like money. If/when your app requires enterprise integration, you'll be fanatically happy that you chose Keycloak over having to implement okta... then ldap... then.. Saml... then.. Kerberos... then ldap again with custom mappers..

I coach multiple rec-level soccer teams in my kids ages. I am ruthlessly fair about play time on the field. You may not get to play center midfielder, but you will get the same amount of time.

Some of my children are naturally good at soccer and some aren't. Doesn't matter. I don't play favorites with them or any other kids on my soccer team.

I started coaching soccer for my kids, because one of my more naturally-gifted children had a horrible coach. Even though she played my kid more, I hated her favoritism and I hated her lack of sportsmanship.

That's it -- I started coaching.

My team is probably never going to win the league, because the best players _still_ get sub'd out on my teams. I don't care.

Be the change you wish to see.

Golang is indeed much more opinionated. To quote @bcantril, "Go is like steampunk for programming."

I'm liking the standardization in web. I think it's possible that you'll see something in web like you see with C/C++. D is better than C++, but it isn't compelling enough to jump. You need a very compelling set of features to leave the very comfortable, though dangerous, home of C/C++ for the domain that it excels in. With web, you'll need compelling features to leave the comfortable home of Typescript + React.

I read a statistic years ago that said that taking care of grandkids had a u-shaped mortality response. If you took care of them 2 days a weeks, it was optimal for mortality. More than that and you died younger. Less than that and you died younger.

Yes, correlation is not causation, but that correlation is interesting.

Most people don't know _the names_ of all 8 grandparents, but those people are the root culture of the family you grew up in.

Sorry for your loss. Just met him vicariously and watched his first "Security Engineering Lecture 1" and I miss him already. He seems like a genuine soul.

"privacy partner" seems like an oxymoron.

You can but a 1TB microsd card for $21 on amazon.com. Maybe app archiving feature should be eol'd.

The blue background isn't lock-in -- it's branding and fashion. It's labeling the in-group and the out-group. The cool kids with their Nike shoes and the kids who got their shoes from Payless Shoe Store. The Abercrombie & Fitch wearing kids vs Costco or Walmart wearing kids.

The sooner it can be learned that a symbol on a shoe is ... kind of a silly status symbol, the better. Same with blue background or blue check mark.

We do a react app on the frontend and actix+diesel REST API, with Keycloak JWTs for user management. The actix+diesel REST API is much more solid and less troubling than another python flask API we have.

I still think frontend/backend split is useful for the types of applications my team works on. Stateful, interactive UI clients written in React, without round trips for full page loads is going to be our choice until a Rust WASM frontend client system reaches maturity.

Is there "open hardware" in this space? Someone was selling laser-cut frames and sofas that you assemble, which made me wonder if anyone has gone whole-hog and created reasonable open designs for laser-cut, diy sofas.

You need to configure the "client" in keyclock that corresponds with you front-end.

Hopefully Canadian citizens are the "lender of last resort", just like we Americans are the "lender of last resort".

The bankers must be made whole -- nothing else matters.

More likely that they just planted it. They operate black sites and torture people -- are they above planting evidence?

If the return on investment for purchasing a s/w engineer's salary, properly scaled by the probability/risk that the investment will yield no result, beats the absolutely certain return on investment of purchasing treasury bonds and every other class of probable-yield-adjusted investment, then investors will invest in s/w engineer salaries rather than t-bills or other investments.

I agree with Boeing board members flying Boeing, and likely they already do, but have you ever floated beings above the aether in metal machines? Do we not live in the age of magic?

The grandparent post is incorrect. H/w silicon validation or constrained random testing hasn't been the norm for 10 years, it's at least 20, which us when I first got into that industry.

And yes, we had coverage driven verification back in 2005 as well. No, we didn't "tape out" our CPUs until we'd hit our testing plan which was defined by coverage metrics.

P.s. pre-si verification had testing pipelines way back then before they became the norm in s/w.