coding_updates's profile picture. Just code it.

coding_updates

@coding_updates

Just code it.

고정된 트윗

I have decided to work on a series of different apps, plugins, and extensions. My main issue whenever I work on side projects is finding the courage to publish them. For that reason, I will start posting daily about these projects to log my progress. #coding #day1


Day 7: Kitchen Sync Chrome Extension Tech Stack: 🎨 Vanilla JS + Chrome APIs 🔐 Supabase Auth + PostgreSQL 📧 Vercel Functions + Resend Email 💳 Stripe payments 🔄 Custom Chrome Extension ↔️ Supabase sync #codinginpublic #chromeextension #claudecode #vercel


Day 7: My new project! Building KitchenSync, a Chrome extension that makes cooking easier: 🥣 Save clear recipes 🗓️ Plan meals 🛒 Auto-generate grocery lists 📱 Send recipes to yourself with QR codes Sign up → kitchensyncextension.com #mealplanner #recipes #cookingapp #cooking

coding_updates's tweet image. Day 7: My new project!
Building KitchenSync, a Chrome extension that makes cooking easier:
🥣 Save clear recipes
🗓️ Plan meals
🛒 Auto-generate grocery lists
📱 Send recipes to yourself with QR codes
Sign up → kitchensyncextension.com

#mealplanner #recipes #cookingapp #cooking

Day 7: I decided to take a break from my Monday.com plugin for automation. I still think its a great project and will get back to it later!


Day 6: Great progress, I fixed oauth issues, connected release readiness to my test runs, and set up bug linking from Monday.com board to my failed tests if they have a bug under their name. My dashboard looks like this so far: #qaautomation #cypress #qadashbaord

coding_updates's tweet image. Day 6: 
Great progress, I fixed oauth issues, connected release readiness to my test runs, and set up bug linking from Monday.com board to my failed tests if they have a bug under their name. My dashboard looks like this so far:

#qaautomation #cypress #qadashbaord
coding_updates's tweet image. Day 6: 
Great progress, I fixed oauth issues, connected release readiness to my test runs, and set up bug linking from Monday.com board to my failed tests if they have a bug under their name. My dashboard looks like this so far:

#qaautomation #cypress #qadashbaord

Day 5: I am hitting some 429 errors with Monday.com because I am sending too many redundant requests when I open a test run. Currently working on caching some of these values in order to avoid making multiple calls at once. #qaproject #qaautomation #mondaydotcom


Day 4: I pulled the bugs into the Dashboard using the groupID's and displayed the count of each group. I also added to the settings page which group bugs should be sent and which group is considered complete. Will be working on this feature tomorrow.


Day 3: I decided that the user should create custom settings to designate the definition of duplicate bugs, what group new bugs should be sent to, different automation sections based on file path. Settings will live in a config row in db. #qa #automation #monday #plugin #sdet

coding_updates's tweet image. Day 3:

I decided that the user should create custom settings to designate the definition of duplicate bugs, what group new bugs should be sent to, different automation sections based on file path. Settings will live in a config row in db.
#qa #automation #monday #plugin #sdet

Day 3: Today I successfully was able to create a bug with an assigned user and an update with the test failure details. Next step will be to have smart linking so that customers will know if an open bug is tied to the failure already. #mondayplugin #testautomation #qaengineer


My project I’m focusing on is a Monday.com plugin that integrates Cypress & Playwright test automation from CI/CD pipelines (GitHub Actions, Azure DevOps). It adds a dashboard to track runs and automatically log + manage bugs directly in Monday #cypress #monday.com


이 계정은 아직 팔로워가 없습니다

United States 트렌드

Loading...

Something went wrong.


Something went wrong.