Jim Seconde
A trained actor with a curious background: from Theatre Studies, to Q/A, to Business Intelligence development, to full stack web development, I am the resident specialist PHP Developer Advocate at Global Cloud Communications giant Vonage. I founded Birmingham, UK’s current PHP usergroup BrumPHP, hosted the Fusion Meetup Series, and organised the TechMids Developer Conference. I mentor, write and speak on PHP, JavaScript, DevOps, DevRel and tech culture. I pretended to be a DJ on the way.
Senior Developer Advocate @ Vonage
CLIs Aren't As Easy As You Might Think
Session Type: Talk
It's built in the muscle memory - you do the same commands over and over each day as part of your job. Designing a CLI tool is probably quite simple, right? Erm, no. Making a CLI for thousands of other developers to use every day takes a lot of thought. We're going to look at the art of the CLI.
This talk was written by Chuck Reeves and I earlier this year: Chuck realised that, when writing the new version of the company CLI, developers have to make a mountain of decisions that have tech debt repercussions for years if shortcutted. Which way round do arguments go? I like shiny emojis, I'll put those in to make an accessibility disaster. It also gives a chance to show some of the absolutely bizarre everyday things we are doing as developers in our day-to-day, because Alex in 1982 had to make a decision on terminal command orders.
In this talk, while I amuse the audience with examples of _terrible_ design choices that for some reason include me talking about a failed 2008 video game that has the best ending ever, an energy drink that shouldn't exist and me standing and pointing at a coffee shop putting out weird signs. While it's fun to laugh at bad stuff, it's time to use those examples of how to write _good_ CLIs that are consumed by developers. After all, if we're all going to supposedly be prompt engineers, we should probably learn how to sanitise our inputs.
This talk was written by Chuck Reeves and I earlier this year: Chuck realised that, when writing the new version of the company CLI, developers have to make a mountain of decisions that have tech debt repercussions for years if shortcutted. Which way round do arguments go? I like shiny emojis, I'll put those in to make an accessibility disaster. It also gives a chance to show some of the absolutely bizarre everyday things we are doing as developers in our day-to-day, because Alex in 1982 had to make a decision on terminal command orders.
In this talk, while I amuse the audience with examples of _terrible_ design choices that for some reason include me talking about a failed 2008 video game that has the best ending ever, an energy drink that shouldn't exist and me standing and pointing at a coffee shop putting out weird signs. While it's fun to laugh at bad stuff, it's time to use those examples of how to write _good_ CLIs that are consumed by developers. After all, if we're all going to supposedly be prompt engineers, we should probably learn how to sanitise our inputs.
Headline Sponsor
Silver Sponsor
Bronze Sponsors
We are looking for sponsors!
Sponsors make this conference possible, we're actively looking for people to support!