Devlog

• 

  @coders_fail

  18 days ago

  RT @SimJoSt: The importance of hyphens became clear once again, while listening to a @vercel ad on @svelteradio talking about "zero-config…

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  RT @nuxt_js: It's time for 3.0 ✨ https://t.co/PXTNWKmkbq https://t.co/Hz9FBGoavK

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  RT @SvelteSociety: It’s time to announce our next Svelte Summit sponsor! It’s everyone’s favourite @Cloudflare 🥳 If you haven’t checked out…

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  RT @lukeed05: Svelte & Cloudflare have been a match made in h̶e̶a̶v̶e̶n̶ the cloud for a very long time. I've been shipping this power coup…

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  RT @lukeed05: 🆕 SvelteKit adapter for Cloudflare Pages is now available! 🥳 You keep all of SvelteKit & gain all of Pages' benefits: auto…

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  The results were all of our ideas based on @CloudflareDev Workers. Limited scope in requirements (no frontend, limited by the stack), high value & impact for customers, no upfront investment & running cost but the development time. https://t.co/eyRhPwEGhJ

  View full converastion on twitter

  • 

    @coders_fail

    2 months ago

    The first simple one was done after a few hours. Great results! Unfortunately, @Cloudflare silently closed the beta of the Apps with Workers feature, which offered a public marketplace for easy monetization: https://t.co/0BjrKfZ027 https://t.co/EoagmouS5l https://t.co/murCUBtB0A

  • 

    @coders_fail

    2 months ago

    Owing to this, a new idea formed: Our own Workers shop 🛒🛍️ As we couldn't find one & there are some challenges of automatically distributing Workers to accounts, we went back to the drawing board and sketched a much more complex idea.

  • 

    @coders_fail

    2 months ago

    The next days were trying and validating each step of the desired workflow. For the shop backend @swellcommerce with @nuxt_js on @CloudflareDev Workers as the frontend, turned out to be a great solution reducing our work massively.

  • 

    @coders_fail

    2 months ago

    Still, the idea was complex, presented new challenges every day & far exceeded the scope of our work framework of wanting to launch an idea in a month. Our time in person came to an end, and we had to recalibrate.

  • 

    @coders_fail

    2 months ago

    One of the challenges, and our solution to it, presented as the obvious next step. Solving the issue of not being able to deploy multiple @CloudflareDev Workers to the same route with an intermediate Worker and a Worker manager with its own interface.

  • 

    @coders_fail

    2 months ago

    Again, finding a lot of solutions for every hitch in the road on the difficult path to a Worker manager, we realized, we were still thinking about a v2, v3 or v4 feature of an idea that should be much simpler. Enter: Just building workers purchasable in a shop 🤣

  • 

    @coders_fail

    2 months ago

    No automatic deployment, no license verification, no multiple workers on routes, no proprietary code protection, no marketplace for other users to sell their own workers as well. Just building products people want to buy and launching them.

  • 

    @coders_fail

    2 months ago

    Again, grabbing @swellcommerce, @nuxt_js, @CloudflareDev, @tailwindcss & @tailwindui we finally had a tightly scoped goal and a very enjoyable stack. As soon as it's launched, we can extend, iterate and improve.

• 

  @coders_fail

  2 months ago

  Our first #lessonlearned was how much time it takes to get the basics right. Setting up all the base systems (@PayPal, @stripe, etc.). And most of all, finding the right (domain) name, rating system for ideas and actually rating them. 2 days went by before we started coding!

  View full converastion on twitter
• 

  @coders_fail

  2 months ago

  After 1 month of collecting business ideas, exchanging thoughts every few days, jotting them down in a @WhatsApp group, documenting the details in @NotionHQ and looking to other people in the space for inspiration, we accumulated 70+ concepts.

  View full converastion on twitter

  • 

    @coders_fail

    2 months ago

    To decide on which to choose first, we added onto our work framework a rubric to rate our ideas. The categories were: - financial potential - implementable within a month - automation potential - Independence from user-generated content - marketing potential with our options

  • 

    @coders_fail

    2 months ago

    For each, we awarded a value from 1 to 5. Making it easy to calculate an overall average for the idea. @NotionHQ made it easy to create additional table views, to only show ideas that a minimum score in specific categories, like feasibility & financial potential.

  • 

    @coders_fail

    2 months ago

    We assigned each value in each category a specific meaning, so we would always rate each idea the same and could communicate about more than just a gut feeling. The details only became apparent while already evaluating the first ideas, getting better with each one.

• 

  @coders_fail

  2 months ago

  Instead of starting out with one business idea that we wanted to make a reality, we had a vision on how we want to work, create and live. Before even starting brainstorming the first concept, we laid out some rules on how to implement & #validate them quickly.

  View full converastion on twitter

  • 

    @coders_fail

    2 months ago

    The most important ones were: - launch rapidly - embrace failure as lessons - learn & reiterate As well as: - try new things & approaches - communicate our needs and thoughts honestly & clearly - learn from other people - connect with the community

  • 

    @coders_fail

    2 months ago

    They lead to a framework with which we want to approach the implementation & assessment of every idea: - focus on building for 2 weeks, preferably in person - polishing it for another 2 weeks for marketing & monetization - making the first purchase after the month

  • 

    @coders_fail

    2 months ago

    This meant a v1 of an idea should only take a month, and we could validate its viability immediately. And the requirements needed to be simple enough to build on weekends and after work. If we could take a few days off, that would a bonus and the exception.

• 

  @coders_fail

  2 months ago

  Initially thinking about creating projects together on our company #workation in #Ibiza, we started #brainstorming business ideas and drawing up our preferred way of tackling them at the @PangeaFestival. It was a great space to disconnect and rethink our previous approaches. https://t.co/O8T3pYDhId https://t.co/irUZKFZmfV

  

  View full converastion on twitter

  • 

    @coders_fail

    2 months ago

    Spending the whole 4 days together gave us the opportunity to switch it up between work, leisure and personal reflection to keep our energy high and our minds from melting. New ideas kept randomly popping into our heads, the more we got into it and got used this type of thinking. https://t.co/3xBjMnMmYW

    3_1590821000408702999
  • 

    @coders_fail

    2 months ago

    The longest time was spent on the name we wanted to operate under, how we want to implement our ideas and which started we wanted to use while working near full-time and wanting to validate ideas quickly. It became clear, that #bootstrapping & #BuildInPublic was the way to go. https://t.co/3zfUma9ipt

    3_1590821009271267337
• 

  @coders_fail

  3 months ago

  RT @SimJoSt: Just starting our #buildinpublic "bootcamp" for the next 2 weeks after work with @RobReckham. Putting our heads together what…

  View full converastion on twitter