David Mytton
@davidmytton.social
Building the security platform that ships with your code at http://arcjet.com. Writing the http://console.dev devtools newsletter.
Great writeup: buttondown.com/whatever_jam...
The many, many, many JavaScript runtimes of the last decade
This last decade has seen an inundation of new JavaScript runtimes (and engines in equal measure), enabling us to run JavaScript in all manner of contexts...
buttondown.com
August 2, 2025 at 12:53 PM
Great writeup: buttondown.com/whatever_jam...
Reposted by David Mytton
One of the best examples of LLM developer tooling I've heard is from a team that supports software from the 80s-90s. Their only source of documentation is *video interviews* with retired employees. So they feed them into transcription software and get summarized searchable notes out the other end.
June 3, 2025 at 11:20 PM
One of the best examples of LLM developer tooling I've heard is from a team that supports software from the 80s-90s. Their only source of documentation is *video interviews* with retired employees. So they feed them into transcription software and get summarized searchable notes out the other end.
Reposted by David Mytton
Creating an email parser requires combining local part parsing with domain parsing to ensure we validate the syntax against the RFCs...but of course just following the RFC doesn't quite work in the real world!
November 15, 2024 at 10:56 AM
Creating an email parser requires combining local part parsing with domain parsing to ensure we validate the syntax against the RFCs...but of course just following the RFC doesn't quite work in the real world!
Isn't that's something AI should be able to help with? 🤔
November 14, 2024 at 7:52 PM
Isn't that's something AI should be able to help with? 🤔
How can we improve the DX?
- Meet developers in their workflow - the code editor e.g. Trunk & Semgrep.
- Idiomatic toolkits that feel natural where developers work - in code e.g. Clerk & WorkOS.
- Interact with developers where they're comfortable - the CLI e.g. Trufflehog and Socket.
- Meet developers in their workflow - the code editor e.g. Trunk & Semgrep.
- Idiomatic toolkits that feel natural where developers work - in code e.g. Clerk & WorkOS.
- Interact with developers where they're comfortable - the CLI e.g. Trufflehog and Socket.
November 14, 2024 at 7:51 PM
How can we improve the DX?
- Meet developers in their workflow - the code editor e.g. Trunk & Semgrep.
- Idiomatic toolkits that feel natural where developers work - in code e.g. Clerk & WorkOS.
- Interact with developers where they're comfortable - the CLI e.g. Trufflehog and Socket.
- Meet developers in their workflow - the code editor e.g. Trunk & Semgrep.
- Idiomatic toolkits that feel natural where developers work - in code e.g. Clerk & WorkOS.
- Interact with developers where they're comfortable - the CLI e.g. Trufflehog and Socket.
2) The product team forwards a customer security questionnaire or has a compliance certification requirement.
Developers are forced into a rapid sprint to rebuild, reimplement or refactor as quickly as possible to close a deal.
Developers are forced into a rapid sprint to rebuild, reimplement or refactor as quickly as possible to close a deal.
November 14, 2024 at 7:51 PM
2) The product team forwards a customer security questionnaire or has a compliance certification requirement.
Developers are forced into a rapid sprint to rebuild, reimplement or refactor as quickly as possible to close a deal.
Developers are forced into a rapid sprint to rebuild, reimplement or refactor as quickly as possible to close a deal.
1) The security team finds a problem. Developers are forced into painful refactoring or installing bad security software.
Things break, usually in production because you can't test locally.
Things break, usually in production because you can't test locally.
November 14, 2024 at 7:51 PM
1) The security team finds a problem. Developers are forced into painful refactoring or installing bad security software.
Things break, usually in production because you can't test locally.
Things break, usually in production because you can't test locally.