Kevin

Great insights, so true. I Could you eventually elaborate the initial questions you ask? I'm used to ask questions in user interviews in terms of product design but I'm always curious and of course want the best for the time I ask from customers/users. Btw, Morgen seems to be a good fit/replacement for the tools in my productivity stack. 🙌🏼

if it needs code: Laravel + Vue As you mentioned, as a solo-founder Laravel's Spark gives me all the basic things I need to test traction and scale it until it doesn't work anymore.

It may sound cheesy and like such a cliché but it always comes down to the "why". Why I started what I'm doing and "what" I expect out of it. Because of that probably also a lot of reflection.

Good question, I actually don't know but I guess it was either an iOS app (Tweety) or a DVD (Trainspotting). Or maybe something way back than 2008. What about you @nabeel_amir?

So many great replies already! I find and found mine through the communities (Slack & Discord) of the apps I build the integrations on – which makes it easy to also ask for features they'd like to see which maybe the services they use already won't build but fit into my product.

First Job (during school): designing websites, repairing computers and coding

1. Break it into smaller chunks 2. If "1." doesn't work: eliminate, archive and/or remove due-dates. Most of the todos that make a todo-list or backlog grow are self-imposed, and most of the time people who mentioned something don't even remember. I also use a "next" or "this week" label which I use to filter. "next" can contain a lot of todos but combined with Projects or other Labels you...

Like you and others already mentioned, it really depends on the use-case or the desired outcome. I try to keep systems (in this case no- or low-code) in place as long as they do what they are expected to do. When there's a need for more customizations I'll replace them with "code"-alternatives.

1. Agenda: if there's no clear agenda - send an email or something asynchronous, looks like there's no real need for a meeting 2. Minutes: max 30 minutes. Except workshops, all-hands, ... 3. Next actions: everyone should have next actions after the meeting; you also can consider if it's necessary to have specific people on board if they don't have next actions - for updates -> email or...

Like Abadesi and George I'm currently bootstrapping and do everything to keep doing it. I want to build and grow a healthy company with healthy people working on a specific solution. VC often leads finding a problem for the solution not the other way around. It's like putting makeup on a wound that's still there. I personally can't stand things like hyper-growth, scale at all costs and just...

do you know a co-working space with people you know? Maybe it helps if you know them but they are also aware of selling or pitching things so that they can give you valuable feedback and you don't pitch in front of complete strangers the first few times. That's what helped me most.

I feel guilty for ignoring it sometimes. It somehow already became muscle memory to just "Ignore it for 15 minutes".

It may not be exactly what you need but you could build something like this with almost no code with IFTTT or Zappier (given that your company allows integrations for Google Docs). You can send me an email with more details and potential use cases to hi@augusteight.at

Hey everyone. Currently, I'm building Bardo, a Tool for Software- and Product-Teams. Bardo's goal is to remove uncertainty while building products with the help of a community and your team's knowledge + history. You can check out the landing page here: https://bardoapp.com/ And the community: https://bardoapp.com/community So if you are a CTO, PM, Dev, Designer and work in a product team...

Headspace