Avatar of Cameron Sadler

Cameron Sadler

CEO at NewCraft
CEO at NewCraft·

We're doing weekend hackathons with customers to help them implement our API faster. So, I'm searching for a great remote pair programming tool with seamless onboarding/set-up. Want it to be as close to a Collison Install ("hand me your laptop, and I'll install Stripe right now") experience as possible.

Has anyone used GitDuck, Tuple, etc. for something like this? I would love suggestions.

READ MORE
4 upvotes·9.4K views
Replies (1)
Recommends
on
GitDuck

Gitduck is multiIDE (VSC is obviously not) and includes video/audio conferencing, so it solves several issues at once. Installation of the plugin is not difficult (search in the IDE plugin store, install, then click on a link you send them to join the pair programming room).

Hope it helps!

READ MORE
3 upvotes·2.5K views
Shared insights
on
TypeScriptTypeScript
at

TypeScript has been a win because, in general, it makes codebase maintenance less brittle. It's significantly easier to refactor in TS than JS, which encourages incremental improvements, file re-organizing, etc. Our developers are happier with the overall development experience.

The downside is that TS sometimes exacerbates problems caused by Node's fragmented ecosystem. Sometimes @types/ don't work, other times types are outdated. This can lead to problems with newly-installed libraries.

If your project is big enough, I'd say TS is nearly always worth it, but it can make selecting libraries annoying.

#typescript #NewCraft

READ MORE
4 upvotes·1.9K views
Shared insights
on
FirebaseFirebase
at

Firebase let's us iterate quickly. We've used the Realtime Database to build rich UX features– like push notifications– fast. Likewise, Firebase Authentication and Cloud Functions save us from having to rebuild redundant server infrastructure. Even though Firebase can get pricey, we've saved money in developer time. Firebase

READ MORE
3 upvotes·1.4K views
Shared insights
on
TypeScriptTypeScript
at

Typescript has been a win because, in general, it makes codebase maintenance less brittle. It's significantly easier to refactor in TS than JS, which encourages incremental improvements, file re-organizing, etc. Our developers are happier with the overall development experience.

The downside is that TS sometimes exacerbates problems caused by Node's fragmented ecosystem. Sometimes @types/ don't work, other times types are outdated. This can lead to problems with newly-installed libraries.

If your project is big enough, I'd say TS is nearly always worth it, but it can make selecting libraries a pain. TypeScript

READ MORE
3 upvotes·1.1K views