#buildinpublic refactored some more on the views, now introducing state management (Zustand, remember it's a Chrome Xtension and I use preact.) Then on to saving project data locally IndexedDB. Still not too late for you to tell me why not :)
#buildinpublic Giving a bit of structure to the project. Here's the rough roadmap and my questions to myself. All neatly documented. Probably flawed from not knowing the unknowns. But hey, it's a start. What are you up to?
Initial researching two Cloud related reqs (#remote#UK) after a quick run/jog in the morning. Active sourcing from tomorrow. Also, looked at PPC on Google Adwords (way complicated for me) for my #buildinpublic - I know, I know not typical. Phew, a heavy day.
#buildinpublic it's not just happening but after years and years of ideating and half assed trials. Finally, I feel the take off. Can't wait to drop v0.1 in private beta.
#buildinpublic goes ahead... but equally, I reached out to somebody who knows the build part better.
I realize there's plenty of learning and a bigger leverage on my time outside debuggin shitty #javascript I wrote. Do you sometimes think about teaming up on your project?
#buildinpublic (re)learnt tons of stuff, worked a bit more than 5 hrs on it, and my little extension opens on every new tab :) Tomorrow, I'll add the JS and style (may need to iterate one or two, but won't hold it back too long.) Then it's out for testing.
Another project I postponed way too long is a huge knowledge-base for #talentacquisition. That I started to build a while back to facilitate my understanding of the parts. I build it on top of @obsdmd and --for v0.1 -- @jekyllrb and of course @Netlify ... #buildinpublic
While I cool down my family's Summer wanderlust and gear myself up to #buildinpublic. A bit of introspection into my core values helped me realize a few things. I'll share with you one of them now. Ready? One of my core values is: 𝙃𝙚𝙙𝙤𝙣𝙞𝙨𝙢