No post body was provided.
Ask HN: What are some developer tools you wish existed?
1–10 of 12 posts
Re: Ask HN: What are some developer tools you wish existed?
#2A way to surface code quality -- across various metrics -- at any level of code (individual token, line of code, file, directory, package, library, application, ...).
Metrics could include: code style consistency, stability (has the area of code changed much over time), risk (is there potential for security vulnerabilities related to the code area), and test coverage.
The metrics - if displayed visually - might look something like a Heat Map[1], and would ideally be represented in the same place as the code itself, perhaps via background colours.
Re: Ask HN: What are some developer tools you wish existed?
#3A way to surface code quality -- across various metrics -- at any level of code (individual token, line of code, file, directory, package, library, application, ...). Metrics could include: code style consistency, stability (has the area of code changed much over time), risk (is there potential for security vulnerabilities related to the code area), and test coverage. The metrics - if displayed visually - might look…
(in fact, resource usage efficiency for each code area could be a helpful metric too; CPU, memory, network, etc)
Re: Ask HN: What are some developer tools you wish existed?
#4Something that could ingest an app's GUI code then render it as some accessible and editable... thing? So that users (and devs?) can easily produce mocks and proposed feature screenshots.
Like some sort of generic reverse wireframe sketcher.
Re: Ask HN: What are some developer tools you wish existed?
#5A way to surface code quality -- across various metrics -- at any level of code (individual token, line of code, file, directory, package, library, application, ...). Metrics could include: code style consistency, stability (has the area of code changed much over time), risk (is there potential for security vulnerabilities related to the code area), and test coverage. The metrics - if displayed visually - might look…
So either IDE and/or repository would show these? Sounds very useful and somewhat straightforward (if involved) to create, so I expect it to exist in some form. Will report back if I find anything.
Re: Ask HN: What are some developer tools you wish existed?
#6A tool to autogenerate sequence diagrams for when I'm working on a method or function
Re: Ask HN: What are some developer tools you wish existed?
#7A no-code/little code platform that is open-source, well designed, powerful but simple, and does the GUI as well.
Like Hasura but not only for the data, or Microsoft Access but without Microsoft or vba.
Re: Ask HN: What are some developer tools you wish existed?
#8A machine that dispenses chocolate for every 100 lines of code I write.
Re: Ask HN: What are some developer tools you wish existed?
#9A heat-map of sorts for a codebase showing the files that have the most-frequent/most-recent edits as hottest. Purpose being to help acclimate new developers to a project by easily seeing which parts of the codebase are most actively worked on.
Re: Ask HN: What are some developer tools you wish existed?
#10A way to surface code quality -- across various metrics -- at any level of code (individual token, line of code, file, directory, package, library, application, ...). Metrics could include: code style consistency, stability (has the area of code changed much over time), risk (is there potential for security vulnerabilities related to the code area), and test coverage. The metrics - if displayed visually - might look…
So either IDE and/or repository would show these? Sounds very useful and somewhat straightforward (if involved) to create, so I expect it to exist in some form. Will report back if I find anything.
Yep, it wouldn't be too surprising if it does already exist. It'd also potentially function something like a more advanced diff tool that can provide time-saving efforts to those who use it.
If mature and reliable enough it could actually be used to predict which changes are likely to cause future problems, and then the code reviewer(s) would have to decide how they'd like to act based on that information.