I hereby claim:
- I am jessmartin on github.
- I am jessmartin (https://keybase.io/jessmartin) on keybase.
- I have a public key ASAuAhIGEWwbQ-QTPdXObZ5ZVTdZO0muZppukaxFAcsqwQo
To claim this, I am signing this object:
| {"type":"permission-mode","permissionMode":"bypassPermissions","sessionId":"1f9db709-4df9-41ab-b5cd-996e8f56a7c1"} | |
| {"type":"file-history-snapshot","messageId":"a405316d-5269-4b3f-ae88-2fda4081bdf2","snapshot":{"messageId":"a405316d-5269-4b3f-ae88-2fda4081bdf2","trackedFileBackups":{},"timestamp":"2026-04-20T19:41:59.700Z"},"isSnapshotUpdate":false} | |
| {"parentUuid":null,"isSidechain":false,"type":"user","message":{"role":"user","content":"<local-command-caveat>Caveat: The messages below were generated by the user while running local commands. DO NOT respond to these messages or otherwise consider them in your response unless the user explicitly asks you to.</local-command-caveat>"},"isMeta":true,"uuid":"d1f6b1af-cdfb-45d9-9885-e917acdb8a3e","timestamp":"2026-04-20T19:41:59.699Z","userType":"external","entrypoint":"cli","cwd":"/Users/jessmartin/Documents/code/we-do-test","sessionId":"1f9db709-4df9-41ab-b5cd-996e8f56a7c1","version":"2.1.114","gitBranch":"HEAD"} |
I hereby claim:
To claim this, I am signing this object:
Original article: Conversational Programming
A month ago, I got a demo of GitHub's Copilot and I've been pondering the implications. Here's what I've realized: Copilot will change what it means to be a programmer.
Will Copilot put programmers out of a job? No more than the invention of typewriters put writers out of a job. What it will do is change the nature of the job. Copilot represents a paradigm shift for the practice of programming.
The naive interpretation of Copilot is improved autocomplete. I believe that's the wrong mental model. Instead, we should think of Copilot as a shift to a conversational model of programming.
GPT-3 Generated Summary: Copilot will change what it means to be a programmer, making it more like a conversation.
| #!/usr/bin/env ruby | |
| today = Time.now.to_s[0,10] | |
| attendees = [] | |
| puts "Who is attending?" | |
| begin | |
| name = gets.strip | |
| attendees << name if name != "" | |
| end while name != "" |
| = Entitlements and Access Control Management | |
| :neo4j-version: 2.2.0 | |
| :author: Kenny Bastani | |
| :twitter: @kennybastani | |
| :description: Graph database access control, entitlements, authorization solutions | |
| :tags: domain:finance, use-case:access-control | |
| This interactive Neo4j graph tutorial covers entitlements and access control scenarios. | |
| ''' |
| # Towards VWF 1.0 | |
| ## What VWF Is... | |
| VWF is: | |
| - Realtime state synchronization (CORE) | |
| - A set of drivers that support immersive experiences - 3D, audio, video and modern graphics (DRIVERS) | |
| With VWF, you can create: |
Listen to the MP3 or watch the performance
leg·a·cy
| # Cheatsheet : Writing Story Cards | |
| ## Remember Your Audience | |
| Each feature & task card has *all* of these readers: | |
| * **Stakeholder** - reviewing & approving the story | |
| * **Project Manager** - estimating, staffing, & planning for the implementation | |
| * **Developers** - estimating & implementing the story | |
| * **Quality Assurance** - verifying the implementation |