Episode 79: The Toxicity of "Certainty"
18:29
Episode 74: Musketeering
11:14
Ай бұрын
Episode 70: Resource Engineering
22:34
Episode 56: AI-Driven Testing
24:27
Episode 54: Shadow Your Colleagues
14:05
Episode 52: The Two-Clock Problem
10:00
Пікірлер
@tommy10001
@tommy10001 4 ай бұрын
I thought this was a great topic. Felt it was a bit short though!
@MikeAndes
@MikeAndes 8 ай бұрын
LETS GOOO! White Label CRM is thankful for Dustin and Isaac's help!
@jorgehester5864
@jorgehester5864 9 ай бұрын
Promo'SM 💦
@CodyEngel
@CodyEngel Жыл бұрын
It's wild how quickly a solution can be scrapped and rewritten when it comes to trying to document it. Have had plenty of situations myself where as I was writing the documentation I thought "wow this is a really dumb idea" and then I instead started by writing out how this class or function should work and then I scrap what I had and follow the documentation I just wrote.
@CodyEngel
@CodyEngel Жыл бұрын
I don't think I like AI writing documentation. As long as someone is going to proof-read whatever the AI writes then sure, but if we relying on AI to do something fairly trivial then I don't have faith we'd go and read the documentation to make sure it's correct. Something that would be neat though is using AI to make sure the documentation is up to date. I think that's something AI could do, alert us if a recent change made the documentation go out of date.
@NeverRewrite
@NeverRewrite Жыл бұрын
I agree! And even if there is proof-reading, I feel like over time users will become lazy and just auto-approve what the AI does, further muddying things. Bad documentation can be worse than no documentation. It can mislead us longer than trying to figure it out ourselves with no documentation. Using AI to comment on expired documentation is an interesting idea... - Isaac