Discover and read the best of Twitter Threads about #developerExperience
Most recents (4)
🤖👨💻 The results are in! Github's survey of 500 U.S.-based developers at enterprise companies reveals the impact of AI on the developer experience. 92% of developers are already using AI coding tools both in and outside of work. #GithubSurvey #AI #DeveloperExperience 
🛠️ Despite industry-wide investments in DevOps, waiting on builds and tests is still a problem. The most important thing for developers is the developer experience, which determines how efficiently and productively they can exceed standards and drive impact. #DevOps
💻 Developers want more collaboration and believe AI will help with this. 70% of developers believe that AI coding tools will offer them an advantage at work, with better code quality, completion time, and resolving incidents as some of the top anticipated benefits. #AI
Even though I haven't been a big fan of Twitter threads so far, a lot of people I know have made 100-tweet threads for @threadapalooza so I thought I'll give it a try as well. I will start with #APIs and hopefully end up connecting them with the #FutureOfWork. Let's go ...
🧵⬇️
🧵⬇️
First of all, when I talk about #APIs, I mean HTTP-based interfaces connecting apps and backend servers as well as different services with each other. For now, the technical details, such as whether they use REST, GraphQL, gRPC etc., shall not matter. (1/100)
When humans interact with computers they require a user interface (UI), and when machines interact with each other they need application programming interfaces (APIs). At the end of the day, however, these have to be implemented by humans. Good #APIDesign considers both. (2/100)
re: adding code comments with respect to the single responsibility principle
As a #selfDocumentingCode fanatic, I do appreciate that some kinds of comments go a long way:
1/3
As a #selfDocumentingCode fanatic, I do appreciate that some kinds of comments go a long way:
1/3
One comment/ blurb (1-3 lines):
- at the top of a class about the single responsibility of the class
- in the project readme/wiki about the single responsibility of the application
2/3
- at the top of a class about the single responsibility of the class
- in the project readme/wiki about the single responsibility of the application
2/3
Some benefits:
- helps keep the class/application at the appropriate size
- helps make the class/application be easier to understand/work-with
3/3
- helps keep the class/application at the appropriate size
- helps make the class/application be easier to understand/work-with
3/3
@bonniea @goldsmithaaron @AllDayDevOps @nnja @oscon @MaggieFero I'd love for you to hear @appsecjosh 's experiences working with dev teams reviewing, merging, and deploying code...
@bonniea @goldsmithaaron @AllDayDevOps @nnja @oscon @MaggieFero @appsecjosh If you're interested in #automation around pull requests, I know some devs like @github 's #security vulnerability remediation #opensource
help.github.com/en/articles/co…
help.github.com/en/articles/co…
@bonniea @goldsmithaaron @AllDayDevOps @nnja @oscon @MaggieFero @appsecjosh @github For a non-dev-centric perspective, you might try
@mheusser 's How a tester can contribute to the code review process searchsoftwarequality.techtarget.com/tip/How-a-test… #testing #whitebox
@mheusser 's How a tester can contribute to the code review process searchsoftwarequality.techtarget.com/tip/How-a-test… #testing #whitebox
