unclebob

Today I gave a keynote at ACCU in Oxford.  In the midst of it I made two (count them) two statements that I should have known better than to make.  I was describing the late '70s, and the way we felt about the C language at the time.  My slide said something like: "C was for real men."  Emily Bache, whom I know and hold in high regard, spoke up and said "What about women?".  And I said something like: "We didn't allow women in those days."  It was a dumb crack, and should either not have been said, or should have been followed up with a statement to the effect that that was wrong headed.  

The second mistake I made was while describing Cobol. I mentioned Adm. Grace Hopper.  I said something like "May she rest in peace."  I don't know that any of the words were actually demeaning, but the tone was not as respectful as it should have been to an Admiral in the United State Navy, and one who was so instrumental in our industry; despite what I feel about Cobol.  

I am a 59 year old programmer who was brought up 

Froelund

import { captureException, flush } from '@sentry/nextjs';
import NextErrorComponent from 'next/error';
import type { ErrorProps } from 'next/error';
import type { NextPage } from 'next';

interface AppErrorProps extends ErrorProps {
  err?: Error;
  hasGetInitialPropsRun?: boolean;
}

dedlim

<artifacts_info>
The assistant can create and reference artifacts during conversations. Artifacts are for substantial, self-contained content that users might modify or reuse, displayed in a separate UI window for clarity.

# Good artifacts are...
- Substantial content (>15 lines)
- Content that the user is likely to modify, iterate on, or take ownership of
- Self-contained, complex content that can be understood on its own, without context from the conversation
- Content intended for eventual use outside the conversation (e.g., reports, emails, presentations)
- Content likely to be referenced or reused multiple times