Um finally ready to start streaming. Tune in tomorrow (23 December) as I start building my TweetTextarea React component which I will be using with my app Threadder. I will post the time for the start of the stream tomorrow. Hope you can join me. #buildinpublic#DEVCommunity
The intention was always to make it into a React component, so I thought it would be much easier to start working on it now. This will also be my first foray into streaming. Would love it if you can join me on the ride. I'll keep u posted for when um ready to start #buildinpublic
Bit by bit, I am improving my vanilla-JS prototype for a Twitter-like input area. The goal of this prototype is to figure out what I need to do, so I can eventually build a React component to use in my web app, Threadder. #buildinpublic Prototype demo: amsaid1989.github.io/TweetTextareaP…
The struggle is real 🤣 Read and follow to learn about my experience aa I slowly descend into the rabbit hole that is frontend web development 😅 #100DaysOfCode#buildinpublic#DEVCommunity
Ah, the joys of frontend web development 😂 My prototype for the tweet input area is finally starting to behave on desktop browsers, so I wanted to test it on mobile browsers. Turns out it behaves very weirdly, so, I decided to try figuring out why 🧵#buildinpublic#100DaysOfCode
Ah, the joys of frontend web development 😂 My prototype for the tweet input area is finally starting to behave on desktop browsers, so I wanted to test it on mobile browsers. Turns out it behaves very weirdly, so, I decided to try figuring out why 🧵#buildinpublic#100DaysOfCode
However, I can use the same time to stream my attempts at learning, engage with other people who are interested in programming and embarrass myself in public 🤣 #buildinpublic
I decides I want to give streaming a go. Making videos on YouTube or consistently writing threads on Twitter is not my thing as it takes time, and I'd rather dedicate any free time I have to improving my programming skills by building projects #buildinpublic
I am trying to embrace the browsers' debuggers more in my workflow. Constantly adding and removing console.log calls to debug the code can be quite tedious and hindering to my productivity (1/2) #buildinpublic
My tweet input area prototype is progressing really well. It supports various user input scenarios and it seems to work well in all of them. Just need to test it extensively to make sure everything works properly and add some missing things #buildinpublic amsaid1989.github.io/TweetTextareaP…
If anyone is interested in how I am trying to implement my own tweet input area, I am currently doing that in a CodePen. The code is very rough and it is still not working properly, but I think it is still interesting to share #buildinpublic Check it here: codepen.io/amsaid1989/pen…
I've hit a major roadblock trying to integrate Quill editor into my app to use it as a tweet input textarea. Looked for solutions everywhere I can think of with no luck. This prompted me to go back to trying to implement my own tweet input. #buildinpublic
I'm getting really close to solving this challenge. I initally wanted to implement it from scratch, but that turned out to be a difficult task. So I opted for using the Quill rich text editor and integrated it into my app quilljs.com #100DaysOfCode#buildinpublic
Achieving the same in the thread input area is a bit more complex and I still haven't figured how to do it. I know how Twitter does it in their tweet input area, but I still can't replicate it in my app. Hopefully I will be able to do it soon.