@jessebellingham
Consultant Developer @ Thoughtworks
Writing about my journey, as a consultant, and as a developer. Interested in teams and ways of working. Interested in ideas about what "good" code looks like.
Nothing here yet.
No blogs yet.
Really nice article Vighnesh 馃檶 super comprehensive. I have a question, and it may just be my lack of experience building with Node, but why do you use a builder function for the entity and have the validation be a separate function passed in? In .NET for example, the entity would be represented with a class (and optionally, interfaces), and if you were aiming for rich domain objects rather than anemic ones, you might have the validation be a part of the class's constructor. Is the way you've got it here a common node pattern?
Good stuff! When writing code, readability should be a priority. I can't agree with this more, and I would add that sometimes even things that aren't necessarily tricks , things like common language constructs, do more harm than good to the readability of code. An idea I've seen come up a lot is shorter == better ; so for example, people will apply ternary operators to make the code more concise, but it just means that you have to study the code for those extra few seconds.
Fantastic post! I'll be saving it for future reference 馃槄 the bit about allowing developers to reflect after finishing a task really resonated with me, and it seems tied to implementing better processes. I would argue that SCRUM and Kanban encourage team leads and product owner/managers to focus almost exclusively on story points, and developers aren't empowered or don't know how to shift the narrative away from imaginary points ticking up, and more towards the value being delivered. Functionally the same outcome though.