When it comes to coding as a career, there's often a lot of pressure to conform to certain norms and standards. From choosing the "right" programming language to working for the "right" company, it can be easy to lose sight of what truly matters: your own preferences and passions.
Top CodeNewbie Daily Discussions in April touched on a lot of different aspects of programming, such as language preference, work environment preference, and specialty focus. It’s not too late to join these discussions:
At its core, coding is a creative process. It involves problem-solving, critical thinking, and a healthy dose of experimentation. There's no one "right" way to code. Each developer brings their own unique set of skills, experiences, and preferences to the table, and that's what makes the field so exciting and dynamic. Find a community that supports your interests and values, like DEV! Connecting with others who share your passion can be incredibly empowering. So keep connecting with us in May. ❣️
Top comments (3)
By being the lead developer sometimes. It awes me that we have a Functional Request come one for a check for one or more objects.
Then some other developer codes it for only one object, writes Unit Tests and Functional Tests.
Then the PR gets checked, and the person has to redo half of the work because they didn't read it correct.
That I what I do, I double check everything. I except everyone to get it wrong. So I check everything (And yes I also make a lot of mistakes, but that is what PR approvals are for).
So I would say that I leave a mark by being stricter and making sure the feature gets implemented correctly with the least amount of possible up-front bugs.
The last paragraph sound like My Metaphore Story.
Am a Software Freestyle Engineer and Metaphor Storyteller.
The final paragraph reads like an episode of My Metaphor Story.
8 ball pool