johnnyAghands

The title of the post on their blog is really misleading "We have Mythos at Home: GLM 5.2 beats Claude in our Cyber Benchmarks". Mythos (or Fable) isn't even benchmarked, and there's giant caveat literally at the bottom: "We have a caveat: This is one task, one dataset, one run."

I think the post is still informative, but very a little disingenuous and clickbaity.

I feel like this sums up to where we're headed.

Does anyone know if there’s an epub version of these, 244 pages??

Does anyone know what Chainlink is?

Related post: https://medium.com/@fullscript-engineering/fullscript-become...

Stoked! The developer culture here is superb! A (so-far) hidden gem!

Wow! That's pretty slick. I've only thought of EXIF data in the context of my digital camera.

wow! didn't even think to look at that! ty!

Ok unrelated, but I'm looking for a tool for making diagrams like that, anyone know what was used on this post? ty

Yeah that was my understanding as well —- but I’m not a framework author so wasn’t sure if this was a common practice.

Trade-offs aside, I personally find the idea of re-running the request through the stack a bit hacky.

Can someone tl;dr: why there is even logic to bypass middleware in the first-place, I feel like I'm missing something obvious here...

Ah ok, yeah.. unfortnutely this type of lag/mismgmt is pretty common once a company gets big enough. Often times the right people don't get involved on first-pass... even at tech-first companies like this -- though at that point perhaps you're no longer tech-first :/

What is intersting?

Cancer :( Specifically Cholangiocarcinoma (bile duct cancer).

Wow so Brett was also autistic.

Same here. I miss the days when you were given a take home or, god forbid, a real world problem, something the company has run into that you can work through with an experienced interviewer.

Some of the worst interviews I've had I've felt like I was a lab rat, just being evaluated for specific traits/reactions. The worst part is, like you said, every Tom, Dick, and Henry does this, its somehow become some kind of lazy industry standard hiring practice, hence the explosion of these interview aid services. Some people will argue it serves a purpose, but I really don't see how. It's like memorizing an answer sheet and doing well on a test. Is that really the type of problem solving you're looking for? Don't get me wrong, I do think its important to understand foundational concepts and algorithims, but like.. it's also the first thing thats abstracted away for good reason in the real world. Anyways its shit.

The worst part is even with my experience I still feel like shit after these calls though I should know better.

Its almost as if these policy makers don't know anything about anything.

Yeah I agree, but I think this post is for those cases where this design might be inappropriate, mainly monoliths with single dbs.

I disagree with the whole "you're not Google/FB"/"over arbitary RPS" logic though. If the design makes sense then it makes sense, end of story. Just understand it.. lol

My condolences, what a good boy :(

You might say, the cat es-cat-lated it...

Wow, mad jelly their CI/CD and monitoring proceses are robust enough to trust a major rollout in December. That's a pretty badass eng culture

That being said, still some unanswered questions:

- If the issue was ipv6 configuration breaking automated cert renewals for ipv4, wouldn't they have hit this like.. a long time ago? Did I miss something here?

- Why did this take 90 minutes to resolve? I know it's like a blog post and not a real post-mortem, but some kind of timeline would have been nice to include in the post.

- Why not move to DNS provider that natively supports ipv6s?

Also I'm curious if it's worth the overhead to have a dedicated domain for scripts/packages? Do other folks do this? (excluding third-parties like package repositories).

900 Sites, 125 million accounts, 1 vulnerability, 0 Girlfriends.

> and learned an enormous amount about what it means to build and run a people-first company

He's talking about Auth0.

> And then it happened, I got the email. Slack didn't work. My laptop restarted and came back with accounts missing. It really, actually happened. And even though the writing seemed to be on the wall, I was still caught a bit off guard.

Talking about how that culture no longer existed -- it's fully Okta now. The Auth0 culture essentially erroded until it finally just no longer existed. This of course happened at a different pace across differnt organizations. Unfortunately, I'd say ours was probably one of the earliest to get hit.

---

As an aside, I was part of same team (also laid off), and had an especially unique viewpoint.

I joined Auth0 in 2020 -- months before the acquisition. I joined because of the culture and the amazing people I get to work with and learn from. I had a lot of fun and we built some amazing things. After about 18 months I decided to join a local startup, itching to get back to a much smaller arena, building something from the ground up. Applying all the great things I've learned in my career thus far. Long story short, as most starups go, especially during COVID, it didn't pan out.

I kept in touch with my old colleagues, now my friends, who approached me with a potential new opportunity. They did warn me things were different now, but I was excited to get to work with great people again.

Coming back it was starkly different. Gone was the magic that was once there. A lot of familiar faces were still around, but so too were a lot gone now. I can feel the beating of the Okta drums more loudly now.. there just felt a lot of separation between leadership and us dreamers at the bottom. I felt like I was just back at a corporate company now, more worried about writing OKRs and how they made my boss/division look good verses actually making our customers lives better. There was a constant dread in the air.. verses excitement.

It's strange, but in some ways its almost like a feeling of mourning. That meme about not knowing when you're in the good old days is very true. Goodbye Auth0 <3

Wow, this title sums up in one sentence what we all hate about Jenkins. It's like the equivelent of timeouts being worse than fast fails.

This for summing up what I couldn't find the words for!

It just felt like more of the same. I left soon after (2020) so perhaps things are changing. Was gutted to leave, IBM was always one of those mythical places to work for me, but in the end I made the right choice. Perhaps one day I'll go back, ha who knows!

> Whitehurst, on the other hand, has a history of strong execution across multiple industries, and built a reputation as someone who protected Red Hat's culture against attempts from within IBM to "Big Blueify" it (possibly to the detriment of his own role within IBM). Even as an interim, having him onboard is a good sign for how Unity is looking to repair its relationships with developers.

100%

I was at IBM at the time. We really hoped he would eventually take over from Ginni once she left... nope. We really could have used someone who wasn't drinking the blue koolaid. Well.. the rest is history.

All this other crap about Silver Lake being a giant POS is concerning though.

Huge!!

Oh man, shocked. Sadly, never met her in personally, but have always admired her work in the field and for just generally being an inspiring person. Huge loss. My sincerest condolences to her family and friends :(

I was just on this this weekend (reading up of disc breaks). Obviously, the content can be out-dated, but that's not why I keep coming back. Something about the clarity of Sheldon's writing :) plus a lot of the content provide foundational information.

Anyway, I was also thinking perhaps I could help modernize the website itself in my spare time. If anyone is interested dm me.