HNHacker News
TopNewBestAskShowJobs

tomatohs

411 karma · joined September 13, 2010

Founder of https://testdriver.ai and https://dashcam.io

email ian [at] testdriver.ai

submissionscomments
tomatohs··on Ask HN: Who is hiring? (June 2024)
TestDriver.ai | https://testdriver.ai | Austin TX, ONSITE (Flex) | Everything

We are a small team building an AI QA Agent for GitHub - on a mission to eliminate repetitive work from developers. Our v2 agent (released this week) is the best desktop automation agent on the market today.

We're a very early stage startup seeking incredibly motivated engineers, sales, and customer success to join our team.

We work from home in Austin TX and meet in person 2x a week.

Email ian@dashcam.io to get in touch.

tomatohs··on Ask HN: Who is hiring? (May 2024)
TestDriver.ai | https://testdriver.ai | Austin TX, Flex | Everything

We are a small team building an AI QA Agent for GitHub - on a mission to eliminate repetitive work from developers. Our v2 agent (released this week) is the best desktop automation agent on the market today.

We're a very early stage startup seeking incredibly motivated engineers, sales, and customer success to join our team.

We work from home in Austin TX and meet in person 2x a week.

Email ian@dashcam.io to get in touch.

tomatohs··on Show HN: 5 Years Ago I made the Recovery Kit, I just made the RK2
I made a mini Arduino-powered smart home that was used for demos at tradeshows [1]. It had to be shipped first to San Fran, then it went to Vegas for CES and a few more places.

I had the same thought at first, "I should really solder these wires."

But then I realized that wires coming loose was inevitable given the hell this project was going to endure being handled by airlines, rolled across different terrain, and poked and proded by trade show attendees.

So I opted to use color coded jumper cables and include extra. In the manual, I included a simple wiring diagram to show how to hook everything up. No solder needed.

In the hands of a consumer, yes, everything should be soldered because there's a higher force needed to break the connection, but repair is also harder. Consumers typically do not repair, so the trade off leans toward solder. I suspect this is the perspective that inspires this comment.

In the hands of a hacker looking for durability, it's actually better for things to be replaceable. Because the hacker can repair, the advantage gained by soldering isn't worth the the friction added repair.

1. https://www.youtube.com/watch?v=BWcm1S_wAz0

tomatohs··on I recorded a screen capture of a task. Gemini generated code to replicate it
We're building an AI Agent that can perform manual testing on feature branches [1]. I can tell you, it works, and it's going to get better, and it's going to happen fast. It's not hard at all for an AI to read text on the screen and click it.

What's amazing is the social impact this has - often people don't believe it's real. It feels like when I had to explain to my parents that in my online multiplayer game, that the other characters were other kids at home on their own computers.

I think it's a matter of denial. Yes, software is made for humans and we will always need to validate that humans can use that software. But should a human really be required to manually test every PR in 10k person teams?

Again, as a founder of an AI Agent for E2E testing, we work with this every day. If I was a QA professional right now, I would watch the space closely in the next 6 months. The other option is to specialize in the emotional human part like in gaming. You can't test for "fun."

1. https://testdriver.ai. Demo: https://www.youtube.com/watch?v=HZQxgQ1jt4g

tomatohs··on Atlassian Acquires Loom
We are building "Loom for devs" at https://dashcam.io
tomatohs··on Take more screenshots (2022)
It's always bugged me that software breaks so easily. Even with the full source code, it can be impossible to get something running again just months later. I've documented my entire work history with screenshots in my portfolio [1], which is sort of weird considering the heavy backend work put into it that isn't reflected.

[1] http://jnnngs.com/

tomatohs··on Take more screenshots (2022)
We're building a startup based on this idea, though we find that the #1 use cases is catching unexpected bugs. Is that what you find as well, when recording with OBS? Check out http://replayable.io.
tomatohs··on Launch HN: Dots (YC S21) – Bot Builder for Discord
Few annoying things:

  - I really want Zapier integration but I don't want to ask you for it
  - Needing to join discord to get an invite code
  - I need to auth and give your bot all my permissions before I know what it can do
tomatohs··on Light mode, Dark mode, and Gen-Z mode?
The Partiful tagline on Twitter is “Facebook events for hot people,” which shows that they’re fully aware they’re they anti-facebook. It’s the entire schtick.
tomatohs··on Ask HN: Do you pull and run code as part of code review?
I'm working on an "instant replay for developers" desktop app for exactly this case. Create desktop instant-replays to embed in pull requests:

http://replayable.io/

tomatohs··on The technical interview practice gap
A big reason we use leetcode style challenges is because they can be automatically scored, while take-homes take a lot more to review.

I'm building a developer screens sharing app that, among other things, automates non-whiteboard interviews. Typically we can review a 60 minute take-home in 10 minutes, without cloning the repo. http://paircast.io

If you're an engineering manager that wants to move away from the leetcode challenges, please get in touch with me. ian@haxor.sh

Also see http://they.whiteboarded.me/

tomatohs··on Mobile Home Skyscrapers: The Elusive Dream of Vertical Urban Trailer Parks
Jeff Wilson, the founder of Kasita, is working on a new housing startup called "Jupe." His pitch to me was that Jupe solves a lot of the zoning and foundation problems he encountered while selling Kasitas.

https://jupe.com/

tomatohs··on Can developer productivity be measured?
The problem is that we do not have a standard "output unit."

> Productivity: the effectiveness of productive effort, especially in industry, as measured in terms of the rate of output per unit of input.

We can all agree "lines of code" is a shit metric, and we can't say "# of bugs closed," because each will have variable difficulty and value. Programmers employed by a business are in charge of automating repetitive tasks, not performing them (the classic measure of productivity).

I perform UX research on APIs. Here, we standardize the "output unit" and therefore can get a better idea of a developer's productivity. Every developer performs the same task, so we can simply measure time spent.

There will never be an ethical solution to measure developer productivity during the workday; this isn't Ford's assembly line.

tomatohs··on Document your code just by hitting “record”
Here's an example of readme output: https://gist.github.com/ianjennings/15a65d05f1112e6b9cfc31ca...
tomatohs··on Document your code just by hitting “record”
Here you can click on a line of code and be brought to that point in the video: https://github.com/haxordx/paircast-demo-1/blame/main/main.j...
tomatohs··on Document your code just by hitting “record”
Why not both?
tomatohs··on Document your code just by hitting “record”
Yes! Asciinema and similar tools were huge inspirations. Editing the video from transcript (like Descript) is certainly a feature for the future. For now, you can use "highlights" to isolate the "the good parts." See this image: https://i.imgur.com/wBLPyAI.png
tomatohs··on Document your code just by hitting “record”
I think the audience here is missing that the code diffs are included in the markdown below, probably because you need to scroll to see them. See around 3:38: https://app.paircast.io/replay/fa41d539-aea0-4d62-a192-3cd77...

Because the Paircast git commits include a timestamped link to the video, using something like gitlens in VS Code would allow you to click from code to video. https://github.com/eamodio/vscode-gitlens#autolink-settings

tomatohs··on Document your code just by hitting “record”
The git commit hash is included at the top of every diff in the transcript. You can `git checkout [the hash]` to get the code at that point.
tomatohs··on Document your code just by hitting “record”
Video at this resolution is a common use case, so feedback like this is helpful. No developer wants to reduce their screen resolution to record a screencast, it totally breaks flow.

There is a huge focus on text, which is why the full markdown transcript is included.

tomatohs··on Document your code just by hitting “record”
Recorded this yesterday pretty quickly and submitted it here not thinking much of it. Turned the iframe into a CTA.
tomatohs··on Document your code just by hitting “record”
It's a three-way link between video, git commits, and markdown. You can edit the markdown on the cast as well. None of this is explained as well as it should be.
tomatohs··on Document your code just by hitting “record”
Hadn't thought of storing only audio, that would definitely be possible, but doesn't seem very useful.
tomatohs··on Document your code just by hitting “record”
Wish this were higher up; lots of discussion here assumes this is for reference documentation when it's only relevant for usage docs.
tomatohs··on Document your code just by hitting “record”
I would have loved to store the media within the git repo that Paircast creates, but unfortunately that requires `git-lfs` which developers absolutely hate.
tomatohs··on Document your code just by hitting “record”
This is actually one of the more advanced features.

Since Paircast works with git, we can link each LOC to the point in the video where it was created. Take a look at the `git blame` and the Paircast links in the sidebar.

https://github.com/haxordx/paircast-demo-1/blame/main/main.j...

tomatohs··on Document your code just by hitting “record”
I feel the same way which is why we're building this. Paircast outputs a markdown tutorial for anyone who's making coding videos. Facecam (and using the product) is optional.
tomatohs··on Document your code just by hitting “record”
Header has been updated with pricing. http://paircast.io/pricing.
tomatohs··on Document your code just by hitting “record”
The idea isn't to avoid writing documentation, it's to create any documentation where there was none. It's inspired by this quote from a GitHub survey.

> 93 percent of the respondents noted that incomplete or outdated documentation is a pervasive problem, but 60 percent say they rarely or never contribute to documentation.

The bet is that it's easier to talk about coding while you do it than sit down and write the docs.

https://opensourcesurvey.org/2017/

tomatohs··on Document your code just by hitting “record”
We're not explicitly blocking video controls. I think this is due to the iframe embed.
← PreviousPage 2 of 5Next →