Good afternoon everyone!
I just wanted to share some of the excitement that I am currently experiencing - YEN is adding another Engineer to the mix. Absolutely thrilled to have the opportunity to work alongside a founder/senior-level engineer.
One thing that I immediately thought about before sitting down with our new engineer was "crap, I need to make sure everything is ready for handoff and ownership" which is what we should be doing as developers anyways. This week I have spent a bit of time reworking some components and styles that used hardcoded values or maybe some spaghetti code. I'm looking for ways to ensure that I am always taking the time to write clean and document as I go. Even on solo projects, documenting is great practice.
How do you remind yourself to comment and document as you go? What does your documentation/comments look like?
I write docs from the word go even while the project is still same. This helps in keeping the work manageable especially as the project grows.
If you are working on the same tech stack over a long period of time and do similar projects, it's good to keep some starter markdown templates that you can reinvent on a project basis.
yup. most folks have their own "boilerplates"!
i'm very excited about this new addition!
I wanna see what you are building!
we're going to have more to see soon... :P
I’m with Rosie
we've shared quite a bit over in our project page...
... but, i don't think many people ever visit it.
we plan on releasing it publicly in 2021.