borisandcrispin

I just use Happy https://happy.engineering/

Just tried it. I think this has a lot of potential and I'm planning to revisit in a few months. Right now I'm running into issues with the orchestrator itself, both bugs and difficulty adapting it to my use case. I found myself spending more time fighting the framework than building my actual agent.

A few weeks ago I participated in a Nano Banana hackathon and built a mobile app that takes photos in different decades. Its called Time Machine: https://apps.apple.com/us/app/time-machine-retro-camera/id67...

We used it a lot some years ago when we built a chatbot for FB Messenger. It was a great surprise. FB analytics was very hidden, but once you got there their product was quite good. Simple to use and gave us 95% of everything we needed to know.

The problem was that you obviously needed to use it with Facebook. As we started building a FB chatbot, that was not an issue, but for any other product it didn't make sense.

We considered:

- Mixpanel was way too expensive for us.

- Google analytics is definitely not a product analytics tool.

- Game Analytics was a good tool, but too much focused on games.

Analytics tools can be very expensive and there weren't many good free alternatives that we were aware of.

This is really cool and easy to use!

Recently I've been checking what can be customized in VS Code and my approach was to just check what was modified by the theme. This makes the whole process more intuitive as you can just tweak the settings and see how it would look like.

Exactly! That experience but on top of any website.

Hi folks! We are building GitDuck (YC S20) to help software teams talk and collaborate. When we think about the how teams interact (and when we look at how we work as a team), it is normal that many of our interactions consists of showing something and talking about it. We could be sharing the code, a drawing and a lot of times we are sharing a website.

Traditional screen sharing was one way of doing this. Sharing 60 frames of your screen per second and allowing your team to see it. The screen resolution was a problem, because if we had a bad connection, the image quality could reduce.

Another problem was the lack of interactivity and that was too annoying to ignore. Come one, it's 2021 and why were we still doing screen sharing the same way we did in the mid-2000s?

People need to narrate what their team should see ...

"Can you click on that button?"

"What button?"

"Wait, scroll back a little bit"

These tiny frictions build up and the flow of information slow. Screen sharing without interaction is like talking on a walkie-talkie instead of having a real-time conversation.

We want to be able to share any website and allow people to view and control it as if they had opened that website themselves. People can scroll, click on things, see everyone's cursors and even type. It is an interactive screen sharing experience.

What do you think? It would be great to hear your thoughts on this topic!

There’s a lot of stuff to do and configure. You need to set up ssh forwarding and some times it may mean configuring firewalls, ssh keys, or VMs/servers.

GitDuck is just one command, the other peers don’t need to do/install anything and very easy to control permissions (read only vs read+write)

(' ᴗ' )

ʘ‿ʘ

•ᴗ•

It's really built for the use cases that we face when developing software. It has direct integrations to your IDE and terminal, so you can share your code and collaborate with people (without having to combine a lot of different tools for the job).

It also works cross-IDE, so you can be using VSCode and your colleague IntelliJ and that's fine.

The previous version of our extension for VSCode was open source, but some months ago we rebuilt GitDuck and this new version is not. We have been thinking how do it (and if we should do it), but no decision yet.

I'd argue that most developers are not on VSCode, although it's the most popular IDE.

The advantage is that you can have the video chat with pair programming that works with any IDE + the other integrations that we are building.

You can use it for free! The premium features are there if you are part of a big team or need more advanced things.

We discussed a lot about this and we were very close to have Webstorm today. We decided to launch anyway because we already previously postponed it and we didn't want to be finding excuses to not launch.

Btw you can signup and select Webstorm and will tell you as soon as we have it.

> was why would I use this when slack video and live share has been fine

To be able to share your code with people not using VSC. We are also optimizing a lot the video quality and we are going to add more integrations soon to the video chat. As we are focused only on developers we can do a lot of things that Slack video can't.

It's because of the rubber duck methodology and in the early days we thought it would be cool to have a command `git duck` that starts a video to explain a commit.

It's a video chat tool with direct integrations to the IDE and other dev tools.

Zoom is just a reference like Google Meet, but they have a longer name.

Terminal sharing is super important and we will work on it soon. This is one of the things that we need the most when we use GD internally.

Connections are P2P btw, no code touches our servers. But yeah, I understand this is not enough to get approval.

Yes, the remote worker can save and the file will be saved in the host.

Tracking changes is coming soon! This is super needed.

We are going to add soon better tools to manage (and share) the local server. So you as a guest can edit, save and see how this is impacts the local server of the host.

Let me know how it goes!

What IDE do you use?

The way it works is that you are sharing your local files to the other people and when they edit the file, all the changes are being applied to your file. So in the end you are the one saving all the changes and making the commits.

You can be working in parallel in different files or just following around. It really depends on what you are trying to achieve.

One cool thing to try with GD is mob programming. :)

Definitely! We'll support it very soon. You would be surprised with the amount of people requesting it.

JetBrains is coming in the next few days! We are already using it internally.

The main advantage is that you can collaborate with people using other IDEs. So I could be using VSC, other person Webstorm and a third one Vim.

What error did you get when loading the page and demo?

By Zoom we mean a video chat tool, but built for developers. I think it's hard to have a tool for every type of work and I can think some use cases that Zoom is great (like in big conferences) and others that is really bad (for debugging for example).

We are just focused on having a great experience for developers, so no big conferences or webinar features.

We could have said "Google Meet for developers", but Zoom is shorter. :)

But yeah, the point is that you can video chat and we are adding other integrations for developers. Pair programming is one, terminal and server sharing is coming.

Some years ago I built a digital piggy bank to help people save money automatically. The psychology behind the product is really hard. The biggest challenges is that you only see the value of saving money after a long time. Everybody knows they should do it, but it's easier to postpone as it's painful and hard to do in a daily basis.

Yotta solves this with an amazing approach. You get the long term reward of saving money at the some time that you get the exciting possibility of winning a short time reward. It's genius.