Live data from Hacker News

Ask HN: What developer tools would you like to see?

news.ycombinator.com

11–20 of 230 posts

Re: Ask HN: What developer tools would you like to see?

#12

I don't know if this exists or not, but it's something I've always wanted. I love and hate unit testing. It's a fantastic idea that I've never seen successfully implemented in practice, mostly because the tests invariably fall by the wayside. At the very least, it's a burden to support them. I'd love a tool that would observe my code during runtime - capturing all inputs and outputs from every function, as well as th…

Not sure this would be great for new code, because the tests are supposed to dictate the function’s behaviour, and not the other way around.

Yet, this would be amazing for legacy projects with no unit tests: you could record the code in production, and generate unit tests from there, and add them to the non-tested project.

It would bring you a safety net allowing you to better work on that legacy project IMO.

This actually reminds me a an attempt at an internal tool I saw pass by whose goal was to save all IO for a given request (aka db call, log calls, network request, file read) for a given backend, and allow you to replay those locally for testing purposes independently from the language used by the backend. I think this didn’t lead anywhere, because it was harder than expected, some things couldn’t be recorded easily (like RNG use), and it also meant finding a way to have all IO libs use the precomputed values.

Re: Ask HN: What developer tools would you like to see?

#15
post #12

I don't know if this exists or not, but it's something I've always wanted. I love and hate unit testing. It's a fantastic idea that I've never seen successfully implemented in practice, mostly because the tests invariably fall by the wayside. At the very least, it's a burden to support them. I'd love a tool that would observe my code during runtime - capturing all inputs and outputs from every function, as well as th…

Not sure this would be great for new code, because the tests are supposed to dictate the function’s behaviour, and not the other way around. Yet, this would be amazing for legacy projects with no unit tests: you could record the code in production, and generate unit tests from there, and add them to the non-tested project. It would bring you a safety net allowing you to better work on that legacy project IMO. This ac…

Very true, yes. Much more useful for existing code. Although I don't think unit tests and TDD necessarily need to be aligned, the red-green-refactor flow could potentially be re-imagined with a tool like this.

Re: Ask HN: What developer tools would you like to see?

#17
A proper TypeScript debugger for React Native + Vscode that fully supports async, stepping in TS (instead of falling back to .bundle files randomly), breakpoints (instead of randomly deciding not to break) and sagas (generator functions).

A fully integrated Vscode extension that can "time travel" the app state (just like React Native Debugger standalone app does, but for the whole app not just redux).

Visual way to debug/replay/disable/change speed of animations that are applied on objects, with animation values and dependencies also listed with their realtime values (perhaps that could be progressed with a slider).

Visual way to display fragment shaders on an image/3D model, at a pane.

Just a few that came to my mind.

Re: Ask HN: What developer tools would you like to see?

#20
Remember the early web, when people used to look at existing websites to learn how it was done?

“View Source” used to be a career-starter for a lot of people, but has become largely useless today due to transpilation, frameworks, and other abstraction layers.

I’d love to see a browser extension provide an “Explain Source” context menu item, which sends you to a pane in Developer Tools that shows:

- an estimation which frameworks the page is likely using (a little like the bar chart that GitHub shows for languages);

- a list of dependencies that the website is likely pulling in, with links to their respective homepage and GitHub page;

- their version number(s), if detectable;

- language(s) in which the website was likely written; and

- a small internal API so people can contribute recognition rules for more frameworks and libraries via pull request.

The target demographic would be students of all ages (starting at elementary school), and other people who’d love to learn about web development but don’t quite know where to start.

And who knows, bringing back that explorative, hands-on philosophy may well help a single person get into web development – maybe on the other side of the planet? – and I believe that’d already be worth the effort.

Post reply on HN