Activity

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

Call for Insights turns 45

On the 15th of January 2026 myself and Ujjwal Kumar Singh joined a call and pressed record. We were curious to see what would happen. A few weeks later I’d done the same with Neil Taylor and Clare ...

"Update: I am totally a doer, I am not a developer! But I could be if I wanted to be, I choose not to. Thanks to my manager @Neil Younger for helping me make the realisation that sometimes the words I use do not accurately represent the value I bring ..."

This badge is awarded to members who indicate they are open to work, writing, teaching, speaking, mentoring, CV reviewing or internships.

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

How would you define a guardrail?

How would you define a guardrail?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

What's the hardest part of defining "expected behaviour" for a system that produces different output every time?

When a system improvises like a jazz soloist, "different" stops meaning "wrong"

What's the simplest guardrail you've used that had the biggest impact?

How would you define a guardrail?

What's the simplest guardrail you've used that had the biggest impact?

Prevention is the highest form of testing: The value of zero bugs

This badge is awarded to members who give their first "thanks" on a piece of content.

AI needs guardrails to play by the rules and work better

How would you define a guardrail?

How would you define a guardrail?

How would you define a guardrail?