HNHacker News
TopNewBestAskShowJobs

jpincheira

242 karma · joined September 11, 2007

Co-founder at https://doola.com — the one-stop-shop for US and non-US residents to launch a US LLC.

Contact me via jpincheira at gmail.com

submissionscomments
jpincheira··on A productive environment for remote work
Many envision & dream about the best environment for remote work.

Most think that what makes remote work great is to work from a beach, or an idyllic place sipping on cold drinks.

But the best environment is the one you set with the right processes and toolset.

jpincheira··on Ask HN: Remote people: Do you have a constant voice/video call running all day?
Nope. Being sync, and being so extremely "sync" like that is just detrimental for remote work. You have to go async in order to really leverage the benefits from remote work in your organization.
jpincheira··on Show HN: Cashbar app – your SaaS revenue in your menu bar
No worries! You can basically have a native macOS app using JS — without using Swift, with the potential of having native mobile apps and web apps (react-native-web, which is what Twitter is using these days), all using the same JS codebase — over 90% code share. Happy to chat anytime. :)
jpincheira··on Show HN: Cashbar app – your SaaS revenue in your menu bar
react native + catalyst[1] would be best for you — to prepare for the future and be multi-platform, which is what we'll be releasing in my team[2] in the next few weeks.

[1] https://github.com/react-native-community/discussions-and-pr...

[2] https://standups.io

jpincheira··on FUSE for macOS is no longer open source
If he made a software that is making companies using it millions, and he still doesn't benefit a dime from his work and explicitly wants to, I think he has the right to go this way.
jpincheira··on How to Make Remote a Success
This is exactly why I decided to work on building a platform for async video / voice discussions.

You end up getting rid of meetings — people gathering in real-time :)

jpincheira··on How to Make Remote a Success
Completely on point. I've heard this from our users at Standups, that async lets them have the time to think and note down what to say, and don't come unprepared to a live/sync daily update meeting, for example.
jpincheira··on How to Make Remote a Success
Love this. For those interested:

https://signalvnoise.com/posts/1430-hire-managers-of-one

jpincheira··on How to Make Remote a Success
Totally agreed! I've seen this at other startups, and it works great.
jpincheira··on How to Make Remote a Success
Nice catch @kull.

@samanthalee233 That's great! I tried to log in to suggest the change, but it did not work with my normal Gitlab account.

jpincheira··on How to Make Remote a Success
Yes, just like Gitlab does. [1]

[1] https://about.gitlab.com/handbook

jpincheira··on How to Make Remote a Success
I'm totally convinced that video & voice communication –not only chat/text personas– is what will allow any remote organization to be successful, by bringing their teams together, improving culture, team spirit, their sense of belonging and ultimately having more productive and happier teams.

Sync/real-time communication is not needed for all the processes in a remote team, and you should go async by default and only use sync for cases where you _really_ have to get together. This is how companies Gitlab [1] have really become successful in doing remote work.

A remote team can be successful by using async/non-real-time communication, especially when you're pairing it with an async platform like Standups which is built from the ground up to support the async comm style. I wrote a blog article about how async is determinant to make remote work "work" within your team/org [2].

[1] https://about.gitlab.com/handbook/communication/

[2] https://standups.io/blog/how-async-communication-can-help-yo...

jpincheira··on A Guide to Distributed Teams
Totally agree with this, and it's how companies like Gitlab have leveraged going async [1]. I wrote a piece around the benefits of going async [2] by the default within your org.

I'd keep sync processes limited to as few as possible, and default everything else to async.

[1] https://about.gitlab.com/handbook/communication/

[2] https://standups.io/blog/how-async-communication-can-help-yo...

jpincheira··on A Guide to Distributed Teams
The culture bit is what I think makes remote teams more productive, more engaged and in the end happier, when nailed in the right way. This is why I am building a platform [1] to help alleviate the cultural challenges around remote teams.

Not being in the same place, at the same time, not having the kitchen conversation by the coffee machine is something that _can_ be worked around by using the right tools and implementing the right processes where those types of conversations can happen.

[1] https://standups.io

jpincheira··on Moto Razr 2019: A foldable smartphone with no display crease
I had the phone, and I love the form factor. I wish Apple could come up with something like this, as I could not move from iOS, to be honest.
jpincheira··on Makers, Don't Let Yourself Be Forced into the 'Manager Schedule'
Because to do creative (product: code/design) work I have to really get uninterrupted streaks of work.

But to do sales, talking to users, I have to do it on the manager's schedule, with the typical slots within a day calendar schedule.

jpincheira··on Show HN: Avoid editing while writing your first draft
I saw other options, but I love how minimal this is. Really.
jpincheira··on Makers, Don't Let Yourself Be Forced into the 'Manager Schedule'
Totally. These days what I do is I allocate time for features/product and just go hard on it for Standups [1]. I do say 1-2 weeks building product as if it were a hackathon. When I am done, I go back to marketing & sales, in the manager's schedule.

So in short, I do things on consecutive days:

* to code, I do maker's schedule.

* to sell/talk to users, I do manager's schedule.

I'm feeling like writing on the topic as well, as it can be valuable for other solo founders too. I struggled a lot in the beginning when building Standups.

[1] https://standups.io

jpincheira··on How Not to Die (2007)
I love this. I have read it a few times in the last years. This and Never Quit If [1] from Jason Lemkin have been essential for me to keep pursuing and never stop building my startup [2].

[1] https://www.saastr.com/never-quit-if/

[2] https://standups.io

jpincheira··on WebKit Goals for 2020
I find it incredible that MediaStream Recording is still not out there on WebKit. They have taken so long to ship this. There's an open ticket[1] since 2012, and we still don't really know if they will implement this for sure on 2020, while Opera, Chrome, and Firefox already support this for years.

This is the main reason why we at Standups don't support video recording on Safari[2]. They are on the same level as Microsoft Edge, which also does not support video recording. It's hard for me to understand they did not want to catch up with the main players.

[1] https://bugs.webkit.org/show_bug.cgi?id=85851

[2] https://standups.io/help/not-using-chrome/

jpincheira··on How Discord achieves native iOS performance with React Native
Very interesting to read how they were able to overcome their performance issues and didn't know they were such a small but effective team.

For us at Standups[1] RN has been just instrumental. As a small team, we are able to ship features, just like Discord, vertically all across the stack. Having 1 language in common (TypeScript) all across your stack is the best for small teams/startups. We share most of our code.

For those of you interested in how to share code vertically using TypeScript[2], check out this guide by Bruno Lemos, super helpful, great value there for startups and especially tech solopreneurs.

[1] https://standups.io

[2] https://dev.to/brunolemos/tutorial-100-code-sharing-between-...

jpincheira··on Launch HN: zeroheight (YC S19) – UX design docs that stay up-to-date
Thanks Jerome. And sure, no worries. I thought you’d probably had a few people working remotely apart from the office :)
jpincheira··on Launch HN: zeroheight (YC S19) – UX design docs that stay up-to-date
Super cool guys. Congrats on the launch. You're touching on a big pain. Will most definitely give it a try within our upcoming re-design of our app. [1]

By the way, if you're a remote team, I'm happy to talk with you guys and get in touch [2], love what you built. Sick landing page.

[1] https://standups.io

[2] jp at standups.io

jpincheira··on BuilderX: A Design Tool That Codes React and React Native
Congrats! This looks really great and will enable many people to shorten the dev cycle and lower the entry barrier for many startups to create their first app.

I coded myself a whole mobile version of our platform[1] using React Native and know the pains! It's fantastic that you could automate this and make it a SaaS company.

[1] https://standups.io

jpincheira··on Four kinds of documentation
Forgot to add also the guy from SimpleAnalytics, he's doing exactly the same with documentation [1] in his app.

[1] https://docs.simpleanalytics.com/

jpincheira··on Four kinds of documentation
Seems we're both in the same boat! Exactly. If on live demos, they go like "wow, didn't know this case". That's exactly what you should go write after. I have a huge list of things to write about.

Hope you enjoy the podcast, there are some gems there about SEO. Ruben Gamez —the person in the podcast— was also technical and learned his way around SEO.

Mind sharing what your product is?

jpincheira··on Four kinds of documentation
Thanks for sharing this guide. It's fitting like a ring to finger as I am in the process of setting up documentation for the features of my app [1] because I realized that as an early-stage startup one of the best ways to teach your users how to use your product is by writing great documentation. I'm finishing the setup of this site within my landing now using Gatsby, on the main domain, so that it can also help to bring in more traffic from search engines.

On the same topic, today I was listening to a podcast [2] titled "Getting traffic to a new website without blogging" which is excelent to match using Divio's guide.

[1] https://standups.io

[2] https://podcasts.apple.com/us/podcast/episode-344-getting-tr...

jpincheira··on The benefits of a more asynchronous workplace
The benefits you get from implementing asynchronous communication with your organization are huge. This is exactly why I felt the need to resign from my job last year to go build a platform that is designed from the ground up to support this.

As a remote team, implementing the async communication style will allow you to never have to depend on fixed calendar meetings. No need to have to organize everybody together in a room, at a specific time, to just make a decision.

I wrote a bit about how to do this within a remote team, which is a guideline into how to set a basic async comm process for a remote team. Hope you find it helpful:

https://standups.io/blog/a-basic-guideline-for-async-communi...

jpincheira··on All paid targeting options available on social media platforms
Didn't know that they use them, but still, if you can opt-out, not a biggie for me.
jpincheira··on Gatsby raises $15M Series A for its modern web development platform
I love Gatsby. We are about to release a new landing version of https://Standups.io entirely with it. Blog and help center. We got rid of intercom guide :)

Parse.ly also just released their new landing page all done with Gatsby.

← PreviousPage 2 of 5Next →