Things just keep changing constantly, another job another mess… a repetitive process of seeing code that may once have been produced to good business needs.
But while business changes are happening, there’s a lack of poor coding standard among the fast pace environment.
Factors may include limited time, short fall on talent, to miss communication between colleagues or teams, or just the nature of employment to human error.
I see that trending… a.. lot, even in well documented or reading materials, just check my Instagram feed out, pretty basic examples, but yet one may not see it straight away…
And here I am learning programming, how dynamic languages from learning JQuery to vanilla JS using React.js and Vue.js all work behind the scene, noticing state cycles and how interactive elements on markup react, whether it’s a button or a URL link.
Seeing data races when elements on pageload load slow or when users react to events on a page.
Or, when functions are buried within function and script files bundled randomly that causes conflicts among execution.
But, I’ve fixed the mess with some history behind what it should and shouldn’t do and where to look for these files to edit.
Sure it took several days or some week or two to get it correct, but not bad to say I don’t have the correct qualifications, just a heck of a lot minor qualifications and plenty of experience in and out my career progression.
Understanding ones code and then attempting to fix it, would be suicidal – it’s not easy as building something new with the common known tools one may use.
One true thing that does amazes me, how each user tries to navigate their way through a website or software looking for what they need/want in information or running certain tasks.
The way how one uses it, whether it was designed to do so or was designed to do something alternative – always look outside the box.
And now I’ve come to my senses there’s a lot I could do, but my time is worth so much more, only look at the bigger picture by prioritize crucial tasks first given working in scrum and using sprints to weed out the least irrelevant requirements, and when those fall together, the least irrelevant follow as if it becomes a waterfall of working code.
I still have lots to learn and cover, yet striding the tech stack swiftly with self motivation and some help from the smartest people I’ve come across, but one advice I’d give to all… Nothing is correct and not everything is also wrong, it’s finding that right balance of what is true and false using your own instincts, most likely from experience.
Those starting fresh, start early and make as many errors as possible, as later you’ll realise your strengths and collaborate where ever possible in teams or departments.
