1. Chunk one inside a YT video
2. Chunk two inside a TikTok video
3. Chunk three on an X thread
And then just post the manifest somewhere that can be read by a client, that then pulls the data in (video, doc, anything)
Obv, not meant for speed or good UX, but if we’re going down the route of decentralization, we can probably leverage social platforms to host chunks of data.
use AI to rewrite all the spells from all the books, then try to see if AI can detect the rewritten ones. This will ensure it's not pulling from it's trained data set.
I have a groups like feature requests and backlog for catch-all tasks. Then for deadlines I use "Mid January" or "End of January" and move tasks into them, based on a rough hour estimate. Story points doesn't matter because I'm not quantifying complexity across a team members. It's just me working on it.
I work on the tasks that have the highest priority, build locally, test them in a QA instance, and then ship them to prod. I usually run smoke tests in prod just to make sure I don't break something.
I used to use GitHub tickets and JIRA, but over time I needed organization that didn't cause a lot of busy work. For myself, Todoist (paid plan) works.
If I need to add members in the future, I'll go back to using GitHub (kanban, labels, milestones). Most likely my marketing team will need a Kanban before I add another developer.
Other notes:
Use tools that get objectives done and don't create micro tasks.
Finally, create tasks during off time like during lunch, while working out, or on a walk break. I generally plan 2-3 days in advance on the exact work I need to get done. Don't over work yourself.
Right now most chatbot widgets are scripted and require forethought from the admin or business owner. So it's pretty hard figuring out the comment questions on your own or formulating them over time. Even harder when you don't know your customer journey or haven't solidified the ideal customer fit.
This is exactly why I created a bot [1] that blends chatbots and Stack Overflow together. You can have an automated first-line support system without scripting or conversational dances.
- Instead of conversations, you can reuse previous question/answers.
- Instead of guessing FAQs, you can let your users define them for you.
- When questions don't exist, they get catched in the traditional support flow (email). Then overtime, this effort declines.
https://GetChipBot.com - Crowdsource FAQ bot right on your website: Cheap, easy, and gets direct user insights from behavior events. No annoying live chat to maintain.
Value-add is for engineers who use React day to day already or want to use a minimal API to work to build their UI.
Don't take my word. Checkout the popularity of React, it's proliferation into the marketplace, and it's use on production environments. Also Vue is another popular alternative that UI engineers like to use, which also has SSR.
If you're raising 1M+ in the midwest, it's straight forward. Get a meeting with a VC associate in the region (Chicago: HP VC, Origin, OCA) and they will tell you exactly what they're looking for in a Series A.
I've never had any success with getting institutional money at the seed stage, but if you do get it, it's even easier to bypass some of the troublesome checklist items you get in the A round.
> Adwords is almost useless at this point, though neither of us has had any prior experience so it could just be us not using the tools to their full potential.
For our B2C company, AdWords turned out to be a stable revenue driver for us. I had little experience in it (I'm a software engineer) and it took about $3k burned over 60 days to really understand how to build a profitable acquisition model using AdWords. I bought a couple books and worked on a bunch of multi-variant testing. I eventually obtained a sustainable and predictable process of obtaining revenue.
Never use AdWords Express, spend about 160 hours minimum of learning how marketing and PPC works, and use only data to drive decisions. ROI comes 4 months later when first starting out. If you're an engineer, AdWords API is a really useful to combine CRM and user data to discover new keywords and personas.
1. Chunk one inside a YT video 2. Chunk two inside a TikTok video 3. Chunk three on an X thread
And then just post the manifest somewhere that can be read by a client, that then pulls the data in (video, doc, anything)
Obv, not meant for speed or good UX, but if we’re going down the route of decentralization, we can probably leverage social platforms to host chunks of data.