update

diviyeshpatel · diviyeshpatel · commit affa010f6ac6 · 2025-03-18T12:52:24.000Z
diff --git a/blog/_posts/2023-08-23-spotting-for-bottlenecks.markdown b/blog/_posts/2023-08-23-spotting-for-bottlenecks.markdown
@@ -0,0 +1,29 @@
+---
+layout: post
+title:  "Spotting for Bottlenecks"
+date:   2023-08-23 01:27:00 +0000
+categories: communication, development, planning, theories
+author: Diviyesh Patel
+---
+
+Spotting for bottlenecks around processes and production never seem quite clear at first glance.
+
+Recognising a pattern of concerns is usually the common ground to identifying where bottlenecks appear.
+
+Sometimes it could be a single point of concern down to a multitude points of concerns.
+
+From clarification, technical know how to co-operation.
+
+Aligning clarification will help the understandings of a subject matter.
+
+The technical know how comes from years of experience.
+
+Knowing this will help one to ask if unsure, without being concerned around the ability to accomplish a task.
+
+Soon or later this will become second nature.
+
+Now with co-operation, it’s always a MUST to help one another, rather than accomplishing set criteria.
+
+You just never know when the criteria could change due to evaluation and clarity.
+
+Prevent yourself from doing things over and over (unless it’s planned iteration), otherwise you’ll burn out quicker then you think.
diff --git a/blog/_posts/2023-12-10-5-years-onwards.markdown b/blog/_posts/2023-12-10-5-years-onwards.markdown
@@ -0,0 +1,44 @@
+---
+layout: post
+title:  "5 Years & Onwards"
+date:   2023-12-10 12:21:00 +0000
+categories: design, development, testing
+author: Diviyesh Patel
+---
+
+It seems such an achievement, yet not long ago it was a mission to stay a float.
+
+The struggles were long and hard, but was well worth the shot.
+
+So you want to know exactly what it is one has been working on over the last 5 years…
+
+Here’s a list of some of the objectives, some set from business requirements and others set out for industry standards and of course curiosities.
+
+<ul>
+<li>Build a system</li>
+<li>Face-lift for systems</li>
+<li>New workflows within a pre-existing system</li>
+<li>Upgrade in frameworks (Bootstrap 3 to 4)</li>
+<li>Introduce new technologies (Vue, Vuex, Router, etc)</li>
+<li>Implement quicker methods by simplicity (the use of Vue mixing)</li>
+<li>Demonstrate to teams (from features and implementations to DevOps IDE setup)</li>
+<li>Keep up with Agile sprints and clear tech debt (continuous improvement)</li>
+<li>Board new recruits and help them along the way (build confidence in making changes)</li>
+<li>Refactor code and make reusable code bases</li>
+<li>Add personality here and there for fun – after all make it enjoyable for everyone to use</li>
+<li>Remove clutter that isn’t in use</li>
+<li>Re-write shared components in newer technologies (compatibility improvement)</li>
+<li>Compile multiple apps into a master application (test trial)</li>
+<li>Learn to write test scripts (use of Jest)</li>
+<li>Implement more test scripts (in progress to prevent sudden changes)</li>
+<li>Create documentation for transformation and consistency</li>
+<li>Learning new tools with AI, check and test implementation</li>
+</ul>
+
+Of course some tasks needed team work to drive things forward, so congratulations are in favour for those that have helped one understand legacy features, implement better UI/UX and help testing for all of the above.
+
+Same goes to those who are no longer with us and sadly will be missed, but have made such an influence to one and the overall process.
+
+Now there’s one more thing left to mention that some of you may know already.
+
+To be continued…
diff --git a/blog/_posts/2024-01-18-new-year-new-challenges.markdown b/blog/_posts/2024-01-18-new-year-new-challenges.markdown
@@ -0,0 +1,36 @@
+---
+layout: post
+title:  "New Year, New Challenges"
+date:   2024-01-18 11:59:00 +0000
+categories: development, history, identity, personal, planning, reviews
+author: Diviyesh Patel
+---
+
+Focusing away for a moment from career to personal life.
+
+A whole new chapter awaits for a special arrival in the New Year.
+
+Taking the challenges to new heights – not just to learn for self nor the team, but to be a father, a husband, a son, a friend, a colleague – being there for mentoring and developing, hopefully trying to be the better version of myself to influence the very next!
+
+Feeling nervous, feeling excited, shorter cycles of restless nights appear ahead as the time comes closer. On standby it seems, waiting for the moment to arrive.
+
+Checking the list of things to do, marking them down as actioned once completed. The sense of achievement whilst overwhelmed with generosity from both sides of families/relatives/friends.
+
+Seeing other couples in the same situation and hearing from their perspective and experience, assuring a similar experience.
+
+Give or take, you’re not alone and sometime flipping the idea of thoughts upside down can surprised one that it’s all part of a normal lifestyle.
+
+The interesting part is now priorities vs expenditures. When to compromise to enjoy the finest moments vs when to set the limit to save. In search for the right balance is now the new opportunity.
+
+Leaving 2023 a year to celebrate for the things achieved and 2024 for the new beginnings, a fresh chapter.
+
+So let’s kick this off by letting you all know, with the clues above, as I mentioned previously some may already know..
+
+Say hello!
+
+
+My wife and I are very excited to annouce the arrival of our little girl Riya Layla Patel born on 18th Jan 2024, weighing 4lbs 11 ounces.
+
+Mummy, Baby and Daddy are all doing well ☺️.
+
+Riya was so excited she made her dramatic entrance earlier then expected and reached home by Friday evening. 💕
diff --git a/blog/_posts/2024-10-03-back-to-reality.markdown b/blog/_posts/2024-10-03-back-to-reality.markdown
@@ -0,0 +1,45 @@
+---
+layout: post
+title:  "Back to Reality"
+date:   2024-10-03 23:24:00 +0000
+categories: communication, data, design, development, personal, planning, practical, reviews, theories
+author: Diviyesh Patel
+---
+
+Since Riya was born, we’ve been pretty occupied learning new things about ourselves.
+
+Between us, our families, relatives and friends, it has been a joy to share the new feelings.
+
+Some feelings that are overwhelmingly dramatic, for example feeding to be accomplished within time constraints, otherwise she will let you know about it!
+
+Learning this trait exposed how to multitask across multi-sprint related projects.
+
+Being capable of switching up spontaneously the thought and actioning process behind development.
+
+Arguably this could cause a knock on effect, missing out on any vital information due to the sense, or… nature of urgency.
+
+It’s the minor details that usually get left behind as an afterthought, which then becomes an amendment to the list of things to accommodate for.
+
+The drawbacks of having to think at what stage the projects state was left in still rings sirens.
+
+With tools in place to monitor this, it becomes another task in finding out.
+
+But nevertheless that’s business.
+
+A company needs to somewhat level the field with their, the clients, the customers requirements and to fulfill strategies to meet those expectations.
+
+You could throw in the towel and say… we’re humans after all, expect it! – Inevitably it’s true!
+
+We make mistakes, and learn from, to move on.
+
+The oversight to all this is repetitiveness in its implementation and a real time sucker to restructure the development workflow.
+
+We need to think out side the box a little here.
+
+Think of how things would work in terms of data science here.
+
+What data sets do we have and how to access this across multiple web applications without the need to call multiple APIs just to fetch data.
+
+Connecting the requirements together is always a challenge from sprint to sprint, without having the birds eye view of which application it will affect.
+
+An outside perspective in with the knowledge to fulfill those missing gaps is what is required and to validate the idea with the wider development team if it’s possible is all that is needed.
diff --git a/blog/_posts/2024-12-05-if-some.markdown b/blog/_posts/2024-12-05-if-some.markdown
@@ -0,0 +1,27 @@
+---
+layout: post
+title:  "If some…"
+date:   2024-12-05 06:11:00 +0000
+categories: profession, reviews, theories
+author: Diviyesh Patel
+---
+
+…things are restricted with a system, then create a new database or entry fields for more viable solutions.
+
+…things are planned to be restricted, then design and plan for less options.
+
+…or all things fail, revert back to the last working solution to keep things undisrupted.
+
+…people are misusing a feature, then question if it was over-engineered or something missing?
+
+…people regular scope development tasks to lean to one side, then be sceptical about it – think whether it needs to be displayed after a page reload.
+
+…people think they’re always right in their decision making, then allow it to validate or highlight their mistake by results.
+
+…people are doing tasks outside their role, should it be deemed appropriate given there are others professionals available for the task?
+
+…people find the shortcut is the answer, then be sceptical about it – life isn’t always about shortcuts nor is it meant to be easy!
+
+…people have any concerns, raised them with the relevant team to investigate and resolve.
+
+…people are in a disagreement with the agreement, then hold them accountable to rectify the issue.
